From mailman-admin@ietf.org  Sat May  1 10:02:11 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16618
	for <pana-archive@lists.ietf.org>; Sat, 1 May 2004 10:02:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJuCc-0004JQ-LF
	for pana-archive@lists.ietf.org; Sat, 01 May 2004 09:06:46 -0400
Date: Sat, 01 May 2004 09:06:46 -0400
Message-ID: <20040501130646.27207.81423.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: pana-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

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

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

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

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

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

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


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

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

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


From pana-admin@ietf.org  Mon May  3 04:59:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15429
	for <pana-archive@lists.ietf.org>; Mon, 3 May 2004 04:59:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZFC-0006S5-9x; Mon, 03 May 2004 04:56:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZCZ-0004Pg-Gf
	for pana@optimus.ietf.org; Mon, 03 May 2004 04:53:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15138
	for <pana@ietf.org>; Mon, 3 May 2004 04:53:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKZCW-0006gu-EC
	for pana@ietf.org; Mon, 03 May 2004 04:53:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKZ8V-00066D-00
	for pana@ietf.org; Mon, 03 May 2004 04:49:17 -0400
Received: from sparte.int-evry.fr ([157.159.10.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZ3x-0005Be-00
	for pana@ietf.org; Mon, 03 May 2004 04:44:33 -0400
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 61A6231C27; Mon,  3 May 2004 10:41:51 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.1.0.29) with SMTP id M2004050310440308101
 ; Mon, 03 May 2004 10:44:03 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 5126331C27; Mon,  3 May 2004 10:41:51 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BKZ1o-000CT3-A2; Mon, 03 May 2004 10:42:20 +0200
Date: Mon, 3 May 2004 10:42:20 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 3)
Message-ID: <20040503084220.GT31546@ipv6-5.int-evry.fr>
References: <20040427033622.GT21363@steelhead> <003001c42eef$8422c870$6401a8c0@sisa.samsung.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003001c42eef$8422c870$6401a8c0@sisa.samsung.com>
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,

    I have two comments concerning added text:

    please see inline,

On Fri, Apr 30, 2004 at 01:12:50PM -0700, Alper Yegin wrote:
> 4.9 Mobility Handling
> 
>    A mobile PaC's AAA performance can be enhanced by deploying a 
>    context-transfer-based mechanism, where some session attributes are 
>    transferred from a previous PAA to the current one in order to avoid 
>    performing a full EAP authentication (reactive approach). Additional 
>    mechanisms that are based on the proactive AAA state establishment at
> 
>    one or more candidate PAAs may be developed in the future 
>    [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
>    mechanism is provided in this section.
> 
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume 
>    its ongoing PANA session without running EAP MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message. This action
> 
>    signals PaC's desire to perform the mobility optimization. In 
>    the absence of Session-Id AVP in this message, PANA session 
>    takes its usual course (i.e., EAP-based authentication is performed).
> 
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable fast re-authentication, it
>    SHOULD retrieve the PANA session attributes from a previous (anchor)
>    PAA that has an unexpired PANA session with the PaC. Current PAA
>    determines the identity of the anchor PAA by looking at the
>    DiameterIdentity part of the PANA session identifier. The mechanism 
>    required to retrieve the session attributes from the anchor PAA is
>    outside the scope of this protocol. Seamoby Context Transfer Protocol
> 
>    [I-D.ietf-seamoby-ctp] might be useful for this purpose.

As the PaC does not give its previous Device-Identifier, the anchor PAA
won't be able to retrieve the PANA context.

> 
>    When the anchor or current PAA is not configured to enable this 
>    optimization, the current PAA can not retrieve the PANA session 
>    attributes, or the PANA session has already expired (i.e., session 
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with 
>    the new session identifier and let the PANA exchange take its usual 
>    course. This action will engage EAP-based authentication and create a
>    fresh PANA session from scratch.
> 
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the anchor PAA, the PANA session continues with a PANA-Bind
>    exchange. 
> 
>    A new AAA-Key is provided by the anchor PAA to the current PAA. The 
>    anchor PAA and PaC perform the following computation for generating
> the 
>    new AAA-Key: 
> 
>    AAA-Key-new = The first N bits of 
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)

if an attacker is able to get this AAA-Key, (s)he will be able to
compute this new key. 

-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Mon May  3 05:09:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15744
	for <pana-archive@odin.ietf.org>; Mon, 3 May 2004 05:09:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZQb-0002Jw-83
	for pana-archive@odin.ietf.org; Mon, 03 May 2004 05:07:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4397vjM008878
	for pana-archive@odin.ietf.org; Mon, 3 May 2004 05:07:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZOP-00019x-KQ
	for pana-web-archive@optimus.ietf.org; Mon, 03 May 2004 05:05:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15693
	for <pana-web-archive@ietf.org>; Mon, 3 May 2004 05:05:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKZOM-000124-8x
	for pana-web-archive@ietf.org; Mon, 03 May 2004 05:05:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKZLJ-0000U2-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 05:02:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZIG-0007hI-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 04:59:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZFC-0006S5-9x; Mon, 03 May 2004 04:56:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZCZ-0004Pg-Gf
	for pana@optimus.ietf.org; Mon, 03 May 2004 04:53:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15138
	for <pana@ietf.org>; Mon, 3 May 2004 04:53:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKZCW-0006gu-EC
	for pana@ietf.org; Mon, 03 May 2004 04:53:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKZ8V-00066D-00
	for pana@ietf.org; Mon, 03 May 2004 04:49:17 -0400
Received: from sparte.int-evry.fr ([157.159.10.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZ3x-0005Be-00
	for pana@ietf.org; Mon, 03 May 2004 04:44:33 -0400
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 61A6231C27; Mon,  3 May 2004 10:41:51 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.1.0.29) with SMTP id M2004050310440308101
 ; Mon, 03 May 2004 10:44:03 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 5126331C27; Mon,  3 May 2004 10:41:51 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BKZ1o-000CT3-A2; Mon, 03 May 2004 10:42:20 +0200
Date: Mon, 3 May 2004 10:42:20 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 3)
Message-ID: <20040503084220.GT31546@ipv6-5.int-evry.fr>
References: <20040427033622.GT21363@steelhead> <003001c42eef$8422c870$6401a8c0@sisa.samsung.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003001c42eef$8422c870$6401a8c0@sisa.samsung.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>
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,

    I have two comments concerning added text:

    please see inline,

On Fri, Apr 30, 2004 at 01:12:50PM -0700, Alper Yegin wrote:
> 4.9 Mobility Handling
> 
>    A mobile PaC's AAA performance can be enhanced by deploying a 
>    context-transfer-based mechanism, where some session attributes are 
>    transferred from a previous PAA to the current one in order to avoid 
>    performing a full EAP authentication (reactive approach). Additional 
>    mechanisms that are based on the proactive AAA state establishment at
> 
>    one or more candidate PAAs may be developed in the future 
>    [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
>    mechanism is provided in this section.
> 
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume 
>    its ongoing PANA session without running EAP MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message. This action
> 
>    signals PaC's desire to perform the mobility optimization. In 
>    the absence of Session-Id AVP in this message, PANA session 
>    takes its usual course (i.e., EAP-based authentication is performed).
> 
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable fast re-authentication, it
>    SHOULD retrieve the PANA session attributes from a previous (anchor)
>    PAA that has an unexpired PANA session with the PaC. Current PAA
>    determines the identity of the anchor PAA by looking at the
>    DiameterIdentity part of the PANA session identifier. The mechanism 
>    required to retrieve the session attributes from the anchor PAA is
>    outside the scope of this protocol. Seamoby Context Transfer Protocol
> 
>    [I-D.ietf-seamoby-ctp] might be useful for this purpose.

As the PaC does not give its previous Device-Identifier, the anchor PAA
won't be able to retrieve the PANA context.

> 
>    When the anchor or current PAA is not configured to enable this 
>    optimization, the current PAA can not retrieve the PANA session 
>    attributes, or the PANA session has already expired (i.e., session 
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with 
>    the new session identifier and let the PANA exchange take its usual 
>    course. This action will engage EAP-based authentication and create a
>    fresh PANA session from scratch.
> 
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the anchor PAA, the PANA session continues with a PANA-Bind
>    exchange. 
> 
>    A new AAA-Key is provided by the anchor PAA to the current PAA. The 
>    anchor PAA and PaC perform the following computation for generating
> the 
>    new AAA-Key: 
> 
>    AAA-Key-new = The first N bits of 
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)

if an attacker is able to get this AAA-Key, (s)he will be able to
compute this new key. 

-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Mon May  3 15:13:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22388
	for <pana-archive@lists.ietf.org>; Mon, 3 May 2004 15:13:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKijS-0006Rw-3t; Mon, 03 May 2004 15:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKiN1-0004rs-GC
	for pana@optimus.ietf.org; Mon, 03 May 2004 14:40:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19548
	for <pana@ietf.org>; Mon, 3 May 2004 14:40:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKiMy-0004NM-Pr
	for pana@ietf.org; Mon, 03 May 2004 14:40:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKiM7-0004ED-00
	for pana@ietf.org; Mon, 03 May 2004 14:39:56 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKiLJ-0003yo-00
	for pana@ietf.org; Mon, 03 May 2004 14:39:05 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX500901IGAEO@mailout3.samsung.com> for pana@ietf.org; Tue,
 04 May 2004 03:38:34 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX500F34IGAGW@mailout3.samsung.com> for pana@ietf.org; Tue,
 04 May 2004 03:38:34 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX500F30IG70F@mmp1.samsung.com> for pana@ietf.org;
 Tue, 04 May 2004 03:38:34 +0900 (KST)
Date: Mon, 03 May 2004 11:38:31 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
In-reply-to: <20040503084220.GT31546@ipv6-5.int-evry.fr>
To: "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <000601c4313d$d6abdcd0$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Julien,

> >    outside the scope of this protocol. Seamoby Context Transfer
Protocol
> >
> >    [I-D.ietf-seamoby-ctp] might be useful for this purpose.
> 
> As the PaC does not give its previous Device-Identifier, the anchor
PAA
> won't be able to retrieve the PANA context.

The PANA session identifier is sufficient to retrieve all the parameters
associated with the session. The CT protocol should carry the session id
to the anchor PAA. Note that this is the session between the PaC and the
anchor PAA.


> 
> >
> >    When the anchor or current PAA is not configured to enable this
> >    optimization, the current PAA can not retrieve the PANA session
> >    attributes, or the PANA session has already expired (i.e.,
session
> >    lifetime is zero), the PAA MUST send the PANA-Auth-Request
message
> > with
> >    the new session identifier and let the PANA exchange take its
usual
> >    course. This action will engage EAP-based authentication and
create a
> >    fresh PANA session from scratch.
> >
> >    In case the current PAA can retrieve the on-going PANA session
> > attributes
> >    from the anchor PAA, the PANA session continues with a PANA-Bind
> >    exchange.
> >
> >    A new AAA-Key is provided by the anchor PAA to the current PAA.
The
> >    anchor PAA and PaC perform the following computation for
generating
> > the
> >    new AAA-Key:
> >
> >    AAA-Key-new = The first N bits of
> >                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> 
> if an attacker is able to get this AAA-Key, (s)he will be able to
> compute this new key.

That's true. We address this issue in the security considerations
section. 

i) Mobility optimization

The mobility optimization described in Section 4.9 involves an anchor
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the anchor PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised anchor PAA leads to
the 
compromise of AAA-Key-new. Operators should be aware of the potential
risk 
of using this optimization. An operator can reduce the risk exposure by 
forcing the PaC to perform an EAP-based authentication immediately after
the 
optimized PANA execution.


Alper

> 
> --
> julien.bournelle@int-evry.fr


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


From exim@www1.ietf.org  Mon May  3 15:33:48 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24341
	for <pana-archive@odin.ietf.org>; Mon, 3 May 2004 15:33:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKizN-0003ii-02
	for pana-archive@odin.ietf.org; Mon, 03 May 2004 15:20:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43JKS0U014298
	for pana-archive@odin.ietf.org; Mon, 3 May 2004 15:20:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKit0-0000cV-Ep
	for pana-web-archive@optimus.ietf.org; Mon, 03 May 2004 15:13:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22490
	for <pana-web-archive@ietf.org>; Mon, 3 May 2004 15:13:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKisz-0000eM-CU
	for pana-web-archive@ietf.org; Mon, 03 May 2004 15:13:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKis1-0000Yj-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 15:12:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKirp-0000T8-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 15:12:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKijS-0006Rw-3t; Mon, 03 May 2004 15:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKiN1-0004rs-GC
	for pana@optimus.ietf.org; Mon, 03 May 2004 14:40:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19548
	for <pana@ietf.org>; Mon, 3 May 2004 14:40:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKiMy-0004NM-Pr
	for pana@ietf.org; Mon, 03 May 2004 14:40:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKiM7-0004ED-00
	for pana@ietf.org; Mon, 03 May 2004 14:39:56 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKiLJ-0003yo-00
	for pana@ietf.org; Mon, 03 May 2004 14:39:05 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX500901IGAEO@mailout3.samsung.com> for pana@ietf.org; Tue,
 04 May 2004 03:38:34 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX500F34IGAGW@mailout3.samsung.com> for pana@ietf.org; Tue,
 04 May 2004 03:38:34 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX500F30IG70F@mmp1.samsung.com> for pana@ietf.org;
 Tue, 04 May 2004 03:38:34 +0900 (KST)
Date: Mon, 03 May 2004 11:38:31 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
In-reply-to: <20040503084220.GT31546@ipv6-5.int-evry.fr>
To: "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <000601c4313d$d6abdcd0$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Julien,

> >    outside the scope of this protocol. Seamoby Context Transfer
Protocol
> >
> >    [I-D.ietf-seamoby-ctp] might be useful for this purpose.
> 
> As the PaC does not give its previous Device-Identifier, the anchor
PAA
> won't be able to retrieve the PANA context.

The PANA session identifier is sufficient to retrieve all the parameters
associated with the session. The CT protocol should carry the session id
to the anchor PAA. Note that this is the session between the PaC and the
anchor PAA.


> 
> >
> >    When the anchor or current PAA is not configured to enable this
> >    optimization, the current PAA can not retrieve the PANA session
> >    attributes, or the PANA session has already expired (i.e.,
session
> >    lifetime is zero), the PAA MUST send the PANA-Auth-Request
message
> > with
> >    the new session identifier and let the PANA exchange take its
usual
> >    course. This action will engage EAP-based authentication and
create a
> >    fresh PANA session from scratch.
> >
> >    In case the current PAA can retrieve the on-going PANA session
> > attributes
> >    from the anchor PAA, the PANA session continues with a PANA-Bind
> >    exchange.
> >
> >    A new AAA-Key is provided by the anchor PAA to the current PAA.
The
> >    anchor PAA and PaC perform the following computation for
generating
> > the
> >    new AAA-Key:
> >
> >    AAA-Key-new = The first N bits of
> >                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> 
> if an attacker is able to get this AAA-Key, (s)he will be able to
> compute this new key.

That's true. We address this issue in the security considerations
section. 

i) Mobility optimization

The mobility optimization described in Section 4.9 involves an anchor
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the anchor PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised anchor PAA leads to
the 
compromise of AAA-Key-new. Operators should be aware of the potential
risk 
of using this optimization. An operator can reduce the risk exposure by 
forcing the PaC to perform an EAP-based authentication immediately after
the 
optimized PANA execution.


Alper

> 
> --
> julien.bournelle@int-evry.fr


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



From pana-admin@ietf.org  Mon May  3 18:21:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08290
	for <pana-archive@lists.ietf.org>; Mon, 3 May 2004 18:21:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlam-0000Tc-Ty; Mon, 03 May 2004 18:07:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlUi-0003kg-GD
	for pana@optimus.ietf.org; Mon, 03 May 2004 18:01:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06307
	for <pana@ietf.org>; Mon, 3 May 2004 18:00:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKlUf-0002H1-Of
	for pana@ietf.org; Mon, 03 May 2004 18:00:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKlTl-00028f-00
	for pana@ietf.org; Mon, 03 May 2004 18:00:02 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKlSz-0001xv-00
	for pana@ietf.org; Mon, 03 May 2004 17:59:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i43LxCgH002232;
	Tue, 4 May 2004 06:59:12 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i43LxCrO020022;
	Tue, 4 May 2004 06:59:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA20021 ; Tue, 4 May 2004 06:59:12 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA01339; Tue, 4 May 2004 06:59:11 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA11484; Tue, 4 May 2004 06:59:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i43LxADG023008;
	Tue, 4 May 2004 06:59:10 +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 <0HX500BJORQJ4M@tsbpo1.po.toshiba.co.jp>; Tue,
 4 May 2004 06:59:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BKlS9-0005qn-00; Mon, 03 May 2004 14:58:21 -0700
Date: Mon, 03 May 2004 14:58:20 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue28] PaC and PAA state machines
In-reply-to: <008001c42f01$159b5270$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: pana@ietf.org
Message-id: <20040503215820.GP4846@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <008001c42f01$159b5270$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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>

Your proposal works for me.  I will remove it from the manuscript if
there is no objection.

Yoshihiro Ohba


On Fri, Apr 30, 2004 at 03:18:35PM -0700, Alper Yegin wrote:
> 
> I'd like to propose we have a separate I-D for the PaC-PAA state
> machines.
> 
> I think a state machine is very valuable for verifying the protocol
> design, and also for guiding implementers. So, I'm for having one and
> documenting it somewhere. But it doesn't have to be within the base
> protocol specification document. Currently the state machine occupies 20
> pages out of 85 in the pana snapshot 4b:
> 
> http://www.toshiba.com/tari/pana/draft-ietf-pana-pana-04b.txt
> 
> Aside from keeping the base specification concise, a separate I-D
> (eventually an informational RFC) will help the base pana specification
> move faster.
> 
> Thoughts?
> 
> 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 May  3 18:37:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09207
	for <pana-archive@odin.ietf.org>; Mon, 3 May 2004 18:37:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlyb-0000tx-0w
	for pana-archive@odin.ietf.org; Mon, 03 May 2004 18:31:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43MVrZP003465
	for pana-archive@odin.ietf.org; Mon, 3 May 2004 18:31:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlq3-0007FS-Ee
	for pana-web-archive@optimus.ietf.org; Mon, 03 May 2004 18:23:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08429
	for <pana-web-archive@ietf.org>; Mon, 3 May 2004 18:22:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKlq0-00054I-J6
	for pana-web-archive@ietf.org; Mon, 03 May 2004 18:23:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKlp3-0004uq-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 18:22:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKlo2-0004kh-00
	for pana-web-archive@ietf.org; Mon, 03 May 2004 18:20:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlam-0000Tc-Ty; Mon, 03 May 2004 18:07:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKlUi-0003kg-GD
	for pana@optimus.ietf.org; Mon, 03 May 2004 18:01:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06307
	for <pana@ietf.org>; Mon, 3 May 2004 18:00:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKlUf-0002H1-Of
	for pana@ietf.org; Mon, 03 May 2004 18:00:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKlTl-00028f-00
	for pana@ietf.org; Mon, 03 May 2004 18:00:02 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKlSz-0001xv-00
	for pana@ietf.org; Mon, 03 May 2004 17:59:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i43LxCgH002232;
	Tue, 4 May 2004 06:59:12 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i43LxCrO020022;
	Tue, 4 May 2004 06:59:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA20021 ; Tue, 4 May 2004 06:59:12 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA01339; Tue, 4 May 2004 06:59:11 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA11484; Tue, 4 May 2004 06:59:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i43LxADG023008;
	Tue, 4 May 2004 06:59:10 +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 <0HX500BJORQJ4M@tsbpo1.po.toshiba.co.jp>; Tue,
 4 May 2004 06:59:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BKlS9-0005qn-00; Mon, 03 May 2004 14:58:21 -0700
Date: Mon, 03 May 2004 14:58:20 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue28] PaC and PAA state machines
In-reply-to: <008001c42f01$159b5270$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: pana@ietf.org
Message-id: <20040503215820.GP4846@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <008001c42f01$159b5270$6401a8c0@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Your proposal works for me.  I will remove it from the manuscript if
there is no objection.

Yoshihiro Ohba


On Fri, Apr 30, 2004 at 03:18:35PM -0700, Alper Yegin wrote:
> 
> I'd like to propose we have a separate I-D for the PaC-PAA state
> machines.
> 
> I think a state machine is very valuable for verifying the protocol
> design, and also for guiding implementers. So, I'm for having one and
> documenting it somewhere. But it doesn't have to be within the base
> protocol specification document. Currently the state machine occupies 20
> pages out of 85 in the pana snapshot 4b:
> 
> http://www.toshiba.com/tari/pana/draft-ietf-pana-pana-04b.txt
> 
> Aside from keeping the base specification concise, a separate I-D
> (eventually an informational RFC) will help the base pana specification
> move faster.
> 
> Thoughts?
> 
> 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 May  4 03:06:38 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13249
	for <pana-archive@lists.ietf.org>; Tue, 4 May 2004 03:06:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKtuO-00021E-Ip; Tue, 04 May 2004 03:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKtsi-0001ih-S6
	for pana@optimus.ietf.org; Tue, 04 May 2004 02:58:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12885
	for <pana@ietf.org>; Tue, 4 May 2004 02:58:17 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKtsf-0001AT-0G
	for pana@ietf.org; Tue, 04 May 2004 02:58:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKtrf-0000yo-00
	for pana@ietf.org; Tue, 04 May 2004 02:57:16 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKtqd-0000ec-00
	for pana@ietf.org; Tue, 04 May 2004 02:56:12 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i446u8k02808;
	Tue, 4 May 2004 09:56:08 +0300 (EET DST)
X-Scanned: Tue, 4 May 2004 09:55:41 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i446tf0v005107;
	Tue, 4 May 2004 09:55:41 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00lKD5rt; Tue, 04 May 2004 09:55:37 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i446tKH18121;
	Tue, 4 May 2004 09:55:20 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 4 May 2004 09:54:56 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
Date: Tue, 4 May 2004 09:54:55 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 58 and issue 74: proposed text (take 3)
Thread-Index: AcQxQm+uH4YiRX48RlKokcjj/OB8aQAXoUyA
To: <alper.yegin@samsung.com>, <Julien.Bournelle@int-evry.fr>
Cc: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 04 May 2004 06:54:56.0157 (UTC) FILETIME=[B56F14D0:01C431A4]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME 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

Two security related comments below.

> -----Original Message-----
> From: pana-admin@ietf.org [mailto:pana-admin@ietf.org]On Behalf Of ext
> Alper Yegin
> Sent: 03 May, 2004 21:39
> To: 'Julien Bournelle'
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
>=20
>=20
> Hi Julien,
>=20
> > >    outside the scope of this protocol. Seamoby Context Transfer
> Protocol
> > >
> > >    [I-D.ietf-seamoby-ctp] might be useful for this purpose.
> >=20
> > As the PaC does not give its previous Device-Identifier, the anchor
> PAA
> > won't be able to retrieve the PANA context.
>=20
> The PANA session identifier is sufficient to retrieve all the=20
> parameters
> associated with the session. The CT protocol should carry the=20
> session id
> to the anchor PAA. Note that this is the session between the=20
> PaC and the
> anchor PAA.

How about adding the MAC AVP as well. Kind of authenticating the =
session. It makes the system just a bit more resistant to DoS attacks =
and the anchor PAA behavior more clear. The new PAA may add the =
Session-Id and the MAC into the CT protocol and the anchor PAA can then =
verify this request if it is valid or not. If the request is valid, then =
the session is moved/terminated/etc., but if it is not valid the session =
is unchanged AND the legitimitate PaC will keep it's session. Another =
plus is that at this point the DoS attack has been detected and not =
after the PANA-Bind message exchange.
=20
>=20
> >=20
> > >
> > >    When the anchor or current PAA is not configured to enable this
> > >    optimization, the current PAA can not retrieve the PANA session
> > >    attributes, or the PANA session has already expired (i.e.,
> session
> > >    lifetime is zero), the PAA MUST send the PANA-Auth-Request
> message
> > > with
> > >    the new session identifier and let the PANA exchange take its
> usual
> > >    course. This action will engage EAP-based authentication and
> create a
> > >    fresh PANA session from scratch.
> > >
> > >    In case the current PAA can retrieve the on-going PANA session
> > > attributes
> > >    from the anchor PAA, the PANA session continues with a=20
> PANA-Bind
> > >    exchange.
> > >
> > >    A new AAA-Key is provided by the anchor PAA to the current PAA.
> The
> > >    anchor PAA and PaC perform the following computation for
> generating
> > > the
> > >    new AAA-Key:
> > >
> > >    AAA-Key-new =3D The first N bits of
> > >                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> >=20
> > if an attacker is able to get this AAA-Key, (s)he will be able to
> > compute this new key.
>=20
> That's true. We address this issue in the security considerations
> section.=20
>=20
> i) Mobility optimization
>=20
> The mobility optimization described in Section 4.9 involves an anchor
> PAA=20
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks=20
> stemming from potential compromise of PAAs. Compromise of the current
> PAA=20
> does not yield compromise of the anchor PAA, as AAA-Key cannot be
> computed=20
> from a compromised AAA-Key-new. But a compromised anchor PAA leads to
> the=20
> compromise of AAA-Key-new. Operators should be aware of the potential
> risk=20
> of using this optimization. An operator can reduce the risk=20
> exposure by=20
> forcing the PaC to perform an EAP-based authentication=20
> immediately after
> the=20
> optimized PANA execution.

To make the system a bit stronger I would suggest that PaC and the =
new-PAA would exchange nonces and include the nonces into the key =
generation process.=20

First the anchor PAA and PaC compute the AAA-Key-new as it is described =
above (I assume that the anchor PAA then transmits the AAA-Key-new to =
the new PAA). Then with this AAA-Key-new PaC and new-PAA can exchange =
PANA-Bind messages and include fresh nonces (from both of them). Then =
2nd key generation could take place

AAA-Key-Independent-new =3D The first N bits of
                          HMAC-SHA1 ( AAA-Key-new, Session-ID | =
PaC-Nonce | PAA-Nonce )

Then 2nd PANA-Bind message exchange would use this =
AAA-Key-Independent-new in the MAC calculation. The result would then be =
that with the AAA-Key (old) the AAA-Key-Indepenent-new can not be =
calculated.

- Dan

>=20
>=20
> Alper
>=20
> >=20
> > --
> > julien.bournelle@int-evry.fr
>=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 May  4 03:12:18 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13536
	for <pana-archive@odin.ietf.org>; Tue, 4 May 2004 03:12:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKu3o-0004aA-GD
	for pana-archive@odin.ietf.org; Tue, 04 May 2004 03:09:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4479mOT017609
	for pana-archive@odin.ietf.org; Tue, 4 May 2004 03:09:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKu1h-0003vv-9z
	for pana-web-archive@optimus.ietf.org; Tue, 04 May 2004 03:07:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13355
	for <pana-web-archive@ietf.org>; Tue, 4 May 2004 03:07:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKu1d-0002o6-Br
	for pana-web-archive@ietf.org; Tue, 04 May 2004 03:07:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKu0r-0002d0-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 03:06:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKu0F-0002Qz-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 03:06:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKtuO-00021E-Ip; Tue, 04 May 2004 03:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKtsi-0001ih-S6
	for pana@optimus.ietf.org; Tue, 04 May 2004 02:58:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12885
	for <pana@ietf.org>; Tue, 4 May 2004 02:58:17 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKtsf-0001AT-0G
	for pana@ietf.org; Tue, 04 May 2004 02:58:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKtrf-0000yo-00
	for pana@ietf.org; Tue, 04 May 2004 02:57:16 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKtqd-0000ec-00
	for pana@ietf.org; Tue, 04 May 2004 02:56:12 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i446u8k02808;
	Tue, 4 May 2004 09:56:08 +0300 (EET DST)
X-Scanned: Tue, 4 May 2004 09:55:41 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i446tf0v005107;
	Tue, 4 May 2004 09:55:41 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00lKD5rt; Tue, 04 May 2004 09:55:37 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i446tKH18121;
	Tue, 4 May 2004 09:55:20 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 4 May 2004 09:54:56 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
Date: Tue, 4 May 2004 09:54:55 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 58 and issue 74: proposed text (take 3)
Thread-Index: AcQxQm+uH4YiRX48RlKokcjj/OB8aQAXoUyA
To: <alper.yegin@samsung.com>, <Julien.Bournelle@int-evry.fr>
Cc: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 04 May 2004 06:54:56.0157 (UTC) FILETIME=[B56F14D0:01C431A4]
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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Two security related comments below.

> -----Original Message-----
> From: pana-admin@ietf.org [mailto:pana-admin@ietf.org]On Behalf Of ext
> Alper Yegin
> Sent: 03 May, 2004 21:39
> To: 'Julien Bournelle'
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 3)
>=20
>=20
> Hi Julien,
>=20
> > >    outside the scope of this protocol. Seamoby Context Transfer
> Protocol
> > >
> > >    [I-D.ietf-seamoby-ctp] might be useful for this purpose.
> >=20
> > As the PaC does not give its previous Device-Identifier, the anchor
> PAA
> > won't be able to retrieve the PANA context.
>=20
> The PANA session identifier is sufficient to retrieve all the=20
> parameters
> associated with the session. The CT protocol should carry the=20
> session id
> to the anchor PAA. Note that this is the session between the=20
> PaC and the
> anchor PAA.

How about adding the MAC AVP as well. Kind of authenticating the =
session. It makes the system just a bit more resistant to DoS attacks =
and the anchor PAA behavior more clear. The new PAA may add the =
Session-Id and the MAC into the CT protocol and the anchor PAA can then =
verify this request if it is valid or not. If the request is valid, then =
the session is moved/terminated/etc., but if it is not valid the session =
is unchanged AND the legitimitate PaC will keep it's session. Another =
plus is that at this point the DoS attack has been detected and not =
after the PANA-Bind message exchange.
=20
>=20
> >=20
> > >
> > >    When the anchor or current PAA is not configured to enable this
> > >    optimization, the current PAA can not retrieve the PANA session
> > >    attributes, or the PANA session has already expired (i.e.,
> session
> > >    lifetime is zero), the PAA MUST send the PANA-Auth-Request
> message
> > > with
> > >    the new session identifier and let the PANA exchange take its
> usual
> > >    course. This action will engage EAP-based authentication and
> create a
> > >    fresh PANA session from scratch.
> > >
> > >    In case the current PAA can retrieve the on-going PANA session
> > > attributes
> > >    from the anchor PAA, the PANA session continues with a=20
> PANA-Bind
> > >    exchange.
> > >
> > >    A new AAA-Key is provided by the anchor PAA to the current PAA.
> The
> > >    anchor PAA and PaC perform the following computation for
> generating
> > > the
> > >    new AAA-Key:
> > >
> > >    AAA-Key-new =3D The first N bits of
> > >                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> >=20
> > if an attacker is able to get this AAA-Key, (s)he will be able to
> > compute this new key.
>=20
> That's true. We address this issue in the security considerations
> section.=20
>=20
> i) Mobility optimization
>=20
> The mobility optimization described in Section 4.9 involves an anchor
> PAA=20
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks=20
> stemming from potential compromise of PAAs. Compromise of the current
> PAA=20
> does not yield compromise of the anchor PAA, as AAA-Key cannot be
> computed=20
> from a compromised AAA-Key-new. But a compromised anchor PAA leads to
> the=20
> compromise of AAA-Key-new. Operators should be aware of the potential
> risk=20
> of using this optimization. An operator can reduce the risk=20
> exposure by=20
> forcing the PaC to perform an EAP-based authentication=20
> immediately after
> the=20
> optimized PANA execution.

To make the system a bit stronger I would suggest that PaC and the =
new-PAA would exchange nonces and include the nonces into the key =
generation process.=20

First the anchor PAA and PaC compute the AAA-Key-new as it is described =
above (I assume that the anchor PAA then transmits the AAA-Key-new to =
the new PAA). Then with this AAA-Key-new PaC and new-PAA can exchange =
PANA-Bind messages and include fresh nonces (from both of them). Then =
2nd key generation could take place

AAA-Key-Independent-new =3D The first N bits of
                          HMAC-SHA1 ( AAA-Key-new, Session-ID | =
PaC-Nonce | PAA-Nonce )

Then 2nd PANA-Bind message exchange would use this =
AAA-Key-Independent-new in the MAC calculation. The result would then be =
that with the AAA-Key (old) the AAA-Key-Indepenent-new can not be =
calculated.

- Dan

>=20
>=20
> Alper
>=20
> >=20
> > --
> > julien.bournelle@int-evry.fr
>=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 May  4 06:49:37 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21837
	for <pana-archive@lists.ietf.org>; Tue, 4 May 2004 06:49:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKxIb-0000Tm-Cy; Tue, 04 May 2004 06:37:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKvms-0004gZ-Ja
	for pana@optimus.ietf.org; Tue, 04 May 2004 05:00:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17971
	for <pana@ietf.org>; Tue, 4 May 2004 05:00:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKvmo-0000R8-JY
	for pana@ietf.org; Tue, 04 May 2004 05:00:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKvlu-0000H1-00
	for pana@ietf.org; Tue, 04 May 2004 04:59:27 -0400
Received: from sparte.int-evry.fr ([157.159.10.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKvl3-0007jE-00
	for pana@ietf.org; Tue, 04 May 2004 04:58:33 -0400
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 629173143C; Tue,  4 May 2004 10:54:57 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.1.0.29) with SMTP id M2004050410571101066
 ; Tue, 04 May 2004 10:57:11 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 4CE373143C; Tue,  4 May 2004 10:54:57 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BKvAR-000DRh-Cm; Tue, 04 May 2004 10:20:43 +0200
Date: Tue, 4 May 2004 10:20:43 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Dan.Forsberg@nokia.com
Cc: alper.yegin@samsung.com, yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 3)
Message-ID: <20040504082043.GI49504@ipv6-5.int-evry.fr>
References: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
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,

On Tue, May 04, 2004 at 09:54:55AM +0300, Dan.Forsberg@nokia.com wrote:
> > 
> > The PANA session identifier is sufficient to retrieve all the 
> > parameters
> > associated with the session. The CT protocol should carry the 
> > session id
> > to the anchor PAA. Note that this is the session between the 
> > PaC and the
> > anchor PAA.
> 
> How about adding the MAC AVP as well. Kind of authenticating the session. It makes the system just a bit more resistant to DoS attacks and the anchor PAA behavior more clear. The new PAA may add the Session-Id and the MAC into the CT protocol and the anchor PAA can then verify this request if it is valid or not. If the request is valid, then the session is moved/terminated/etc., but if it is not valid the session is unchanged AND the legitimitate PaC will keep it's session. Another plus is that at this point the DoS attack has been detected and not after the PANA-Bind message exchange.


the CT protocol already provides such a feature. In CTP, the MN triggers
the transfer by sending a CTAR message to the new access router. This message contains a keyed
hash which is computed with a key that the MN and the old Access Router
should share.

> To make the system a bit stronger I would suggest that PaC and the new-PAA would exchange nonces and include the nonces into the key generation process. 
> 
> First the anchor PAA and PaC compute the AAA-Key-new as it is described above (I assume that the anchor PAA then transmits the AAA-Key-new to the new PAA). Then with this AAA-Key-new PaC and new-PAA can exchange PANA-Bind messages and include fresh nonces (from both of them). Then 2nd key generation could take place
> 
> AAA-Key-Independent-new = The first N bits of
>                           HMAC-SHA1 ( AAA-Key-new, Session-ID | PaC-Nonce | PAA-Nonce )
> 
> Then 2nd PANA-Bind message exchange would use this AAA-Key-Independent-new in the MAC calculation. The result would then be that with the AAA-Key (old) the AAA-Key-Indepenent-new can not be calculated.

it sounds good


-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Tue May  4 07:13:24 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23913
	for <pana-archive@odin.ietf.org>; Tue, 4 May 2004 07:13:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKxja-0008Hf-R7
	for pana-archive@odin.ietf.org; Tue, 04 May 2004 07:05:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i44B5A0l031843
	for pana-archive@odin.ietf.org; Tue, 4 May 2004 07:05:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKxeh-0006kN-TT
	for pana-web-archive@optimus.ietf.org; Tue, 04 May 2004 07:00:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22677
	for <pana-web-archive@ietf.org>; Tue, 4 May 2004 07:00:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKxed-0000Lm-P9
	for pana-web-archive@ietf.org; Tue, 04 May 2004 07:00:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKxcM-0007WE-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 06:57:43 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKxaS-00072l-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 06:55:44 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BKxU8-0004z6-Bo
	for pana-web-archive@ietf.org; Tue, 04 May 2004 06:49:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKxIb-0000Tm-Cy; Tue, 04 May 2004 06:37:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKvms-0004gZ-Ja
	for pana@optimus.ietf.org; Tue, 04 May 2004 05:00:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17971
	for <pana@ietf.org>; Tue, 4 May 2004 05:00:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKvmo-0000R8-JY
	for pana@ietf.org; Tue, 04 May 2004 05:00:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKvlu-0000H1-00
	for pana@ietf.org; Tue, 04 May 2004 04:59:27 -0400
Received: from sparte.int-evry.fr ([157.159.10.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKvl3-0007jE-00
	for pana@ietf.org; Tue, 04 May 2004 04:58:33 -0400
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 629173143C; Tue,  4 May 2004 10:54:57 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.1.0.29) with SMTP id M2004050410571101066
 ; Tue, 04 May 2004 10:57:11 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 4CE373143C; Tue,  4 May 2004 10:54:57 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BKvAR-000DRh-Cm; Tue, 04 May 2004 10:20:43 +0200
Date: Tue, 4 May 2004 10:20:43 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Dan.Forsberg@nokia.com
Cc: alper.yegin@samsung.com, yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 3)
Message-ID: <20040504082043.GI49504@ipv6-5.int-evry.fr>
References: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
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,

On Tue, May 04, 2004 at 09:54:55AM +0300, Dan.Forsberg@nokia.com wrote:
> > 
> > The PANA session identifier is sufficient to retrieve all the 
> > parameters
> > associated with the session. The CT protocol should carry the 
> > session id
> > to the anchor PAA. Note that this is the session between the 
> > PaC and the
> > anchor PAA.
> 
> How about adding the MAC AVP as well. Kind of authenticating the session. It makes the system just a bit more resistant to DoS attacks and the anchor PAA behavior more clear. The new PAA may add the Session-Id and the MAC into the CT protocol and the anchor PAA can then verify this request if it is valid or not. If the request is valid, then the session is moved/terminated/etc., but if it is not valid the session is unchanged AND the legitimitate PaC will keep it's session. Another plus is that at this point the DoS attack has been detected and not after the PANA-Bind message exchange.


the CT protocol already provides such a feature. In CTP, the MN triggers
the transfer by sending a CTAR message to the new access router. This message contains a keyed
hash which is computed with a key that the MN and the old Access Router
should share.

> To make the system a bit stronger I would suggest that PaC and the new-PAA would exchange nonces and include the nonces into the key generation process. 
> 
> First the anchor PAA and PaC compute the AAA-Key-new as it is described above (I assume that the anchor PAA then transmits the AAA-Key-new to the new PAA). Then with this AAA-Key-new PaC and new-PAA can exchange PANA-Bind messages and include fresh nonces (from both of them). Then 2nd key generation could take place
> 
> AAA-Key-Independent-new = The first N bits of
>                           HMAC-SHA1 ( AAA-Key-new, Session-ID | PaC-Nonce | PAA-Nonce )
> 
> Then 2nd PANA-Bind message exchange would use this AAA-Key-Independent-new in the MAC calculation. The result would then be that with the AAA-Key (old) the AAA-Key-Indepenent-new can not be calculated.

it sounds good


-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Tue May  4 22:01:42 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14716
	for <pana-archive@lists.ietf.org>; Tue, 4 May 2004 22:01:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBee-0001me-Sq; Tue, 04 May 2004 21:57:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBap-00011B-0L
	for pana@optimus.ietf.org; Tue, 04 May 2004 21:53:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14328
	for <pana@ietf.org>; Tue, 4 May 2004 21:52:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLBam-0005Ks-09
	for pana@ietf.org; Tue, 04 May 2004 21:53:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLBZn-0005Bm-00
	for pana@ietf.org; Tue, 04 May 2004 21:52:00 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLBYm-0004xa-00
	for pana@ietf.org; Tue, 04 May 2004 21:50:56 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX700E01X3WU1@mailout2.samsung.com> for pana@ietf.org; Wed,
 05 May 2004 10:50:20 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX700D3TX3VLJ@mailout2.samsung.com> for pana@ietf.org; Wed,
 05 May 2004 10:50:20 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX700GUEX3SIG@mmp1.samsung.com> for pana@ietf.org;
 Wed, 05 May 2004 10:50:19 +0900 (KST)
Date: Tue, 04 May 2004 18:50:13 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <000001c43243$503d0370$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

Updated the text based on the latest comments.....

[1] Add to 4.1.1:

   o Nonce AVP: contains a randomly chosen value.


[2] New text for section 4.9:

4.9 Mobility Handling

   A mobile PaC's AAA performance can be enhanced by deploying a 
   context-transfer-based mechanism, where some session attributes are 
   transferred from a previous PAA to the current one in order to avoid 
   performing a full EAP authentication (reactive approach). Additional 
   mechanisms that are based on the proactive AAA state establishment at

   one or more candidate PAAs may be developed in the future 
   [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
   mechanism is provided in this section.

   Upon changing its point of attachment, a PaC that wants to quickly
resume 
   its ongoing PANA session without running EAP MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. Along with
the
   Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
   Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
   is computed by using the PANA_MAC_Key shared between the PaC and a
   previous (anchor) PAA that has an unexpired PANA session with the
PaC.
   This action signals PaC's desire to perform the mobility
optimization. In 
   the absence of Session-Id AVP in this message, PANA session takes its

   usual course (i.e., EAP-based authentication is performed).

   If PAA receives a session identifier in the PANA-Start-Answer
   message, and it is configured to enable this optimization, it
   SHOULD retrieve the PANA session attributes from the anchor PAA.
   Current PAA determines the identity of the anchor PAA by looking at
the
   DiameterIdentity part of the PANA session identifier. The MAC AVP can
   only be verified by the anchor PAA, therefore a copy of the PANA
messsage
   SHOULD be provided to the anchor PAA. The mechanism required to send
a 
   copy of the PANA-Start-Answer message from current PAA to the anchor
PAA, 
   and retrieve the session attributes is outside the scope of this 
   protocol. Seamoby Context Transfer Protocol [I-D.ietf-seamoby-ctp]
might 
   be useful for this purpose.

   When the anchor or current PAA is not configured to enable this 
   optimization, the current PAA can not retrieve the PANA session 
   attributes, or the PANA session has already expired (i.e., session 
   lifetime is zero), the PAA MUST send the PANA-Auth-Request message
with 
   the new session identifier and let the PANA exchange take its usual 
   course. This action will engage EAP-based authentication and create a
   fresh PANA session from scratch.

   In case the current PAA can retrieve the on-going PANA session
attributes
   from the anchor PAA, the PANA session continues with a PANA-Bind
   exchange. 

   As part of the context transfer, an intermediate AAA-Key material is 
   provided by the anchor PAA to the current PAA.  


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
                           

   In case there are two AAA-Keys generated from a NAP-ISP
authentication,
   the AAA-Key-int computation is:


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
                           Session-ID)

   
   The value of N depends on the integrity protection algorithm in
   use, i.e., N=160 for HMAC-SHA1. AAA-Key is the EAP-based
   key that was made available to anchor PAA and PaC as a result of
   the earlier EAP authentication. Due to the reliance on the AAA-Key,
this 
   optimization only works when PaC has performed an EAP-based 
   authentication on the anchor PAA. DiameterIdentity is the identifier
of
   the current PAA. Session-ID is the identifier of the PaC's PANA
session 
   with the anchor PAA. 

   Finally, current PAA and PaC compute the new AAA-Key by using the
nonce 
   values. PAA_Nonce is the randomly chosen value that MUST be carried
in a 
   Nonce AVP in the PANA-Bind-Request message.


   AAA-Key-new = The first N bits of
                 HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)


   New PANA_MAC_Key is computed based on the algorithm described in
Section 
   4.1.5, by using the new AAA-Key and the new Session-ID assigned by
the 
   current PAA. The MAC AVP contained in the PANA-Bind-Request and 
   PANA-Bind-Answer messages MUST be generated and verified by using the
new
   PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
   assigned by the current PAA. A new PANA session is created upon 
   successful completion of this exchange. 

   Note that correct operation of this optimization relies on many
factors,
   including applicability of authorization state from one network 
   attachment to another. [I-D.ietf-eap-keying] identifies this
operation as 
   "fast handoff" and provides deployment considerations. Operators are 
   recommended to take those guidelines into account when using this 
   optimization in their networks. 

   
[4] Change section 9.3.7 from:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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

to:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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


[5] Change 9.3.4:

Change:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Cookie ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]


To:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Session-Id ] 
                       [ Cookie ]
                       [ Nonce ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]
                   0*1 <MAC>                    


[6] Update the AVP occurrence table from:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |








To:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |



And add a line:

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Nonce               |  0   |  0   |  0  |  0  |  0  |
     



[7] Add 9.4.18:

9.4.18 Nonce AVP

   The Nonce AVP (Code 1041) is of type OctetString. The data contains
   a randomly generated value in opaque format. The data length MUST be 
   between 8 and 256 bytes inclusive.



[8] Add to references:

[I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt


[9] Add to Security Considerations section:

i) Mobility optimization

The mobility optimization described in Section 4.9 involves an anchor
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the anchor PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised anchor PAA along with
the 
intercepted nonce values leads to the compromise of AAA-Key-new.
Operators 
should be aware of the potential risk of using this optimization. An
operator can reduce the risk exposure by forcing the PaC to perform an 
EAP-based authentication immediately after the optimized PANA execution.



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


From exim@www1.ietf.org  Tue May  4 22:09:02 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15073
	for <pana-archive@odin.ietf.org>; Tue, 4 May 2004 22:09:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBp0-0004MU-S2
	for pana-archive@odin.ietf.org; Tue, 04 May 2004 22:07:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4527g53016759
	for pana-archive@odin.ietf.org; Tue, 4 May 2004 22:07:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBkX-00035l-KB
	for pana-web-archive@optimus.ietf.org; Tue, 04 May 2004 22:03:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14773
	for <pana-web-archive@ietf.org>; Tue, 4 May 2004 22:03:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLBkU-0006iM-II
	for pana-web-archive@ietf.org; Tue, 04 May 2004 22:03:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLBjc-0006b3-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 22:02:10 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLBij-0006TL-00
	for pana-web-archive@ietf.org; Tue, 04 May 2004 22:01:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBee-0001me-Sq; Tue, 04 May 2004 21:57:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLBap-00011B-0L
	for pana@optimus.ietf.org; Tue, 04 May 2004 21:53:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14328
	for <pana@ietf.org>; Tue, 4 May 2004 21:52:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLBam-0005Ks-09
	for pana@ietf.org; Tue, 04 May 2004 21:53:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLBZn-0005Bm-00
	for pana@ietf.org; Tue, 04 May 2004 21:52:00 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLBYm-0004xa-00
	for pana@ietf.org; Tue, 04 May 2004 21:50:56 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX700E01X3WU1@mailout2.samsung.com> for pana@ietf.org; Wed,
 05 May 2004 10:50:20 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX700D3TX3VLJ@mailout2.samsung.com> for pana@ietf.org; Wed,
 05 May 2004 10:50:20 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX700GUEX3SIG@mmp1.samsung.com> for pana@ietf.org;
 Wed, 05 May 2004 10:50:19 +0900 (KST)
Date: Tue, 04 May 2004 18:50:13 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C6E2@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <000001c43243$503d0370$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Updated the text based on the latest comments.....

[1] Add to 4.1.1:

   o Nonce AVP: contains a randomly chosen value.


[2] New text for section 4.9:

4.9 Mobility Handling

   A mobile PaC's AAA performance can be enhanced by deploying a 
   context-transfer-based mechanism, where some session attributes are 
   transferred from a previous PAA to the current one in order to avoid 
   performing a full EAP authentication (reactive approach). Additional 
   mechanisms that are based on the proactive AAA state establishment at

   one or more candidate PAAs may be developed in the future 
   [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
   mechanism is provided in this section.

   Upon changing its point of attachment, a PaC that wants to quickly
resume 
   its ongoing PANA session without running EAP MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. Along with
the
   Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
   Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
   is computed by using the PANA_MAC_Key shared between the PaC and a
   previous (anchor) PAA that has an unexpired PANA session with the
PaC.
   This action signals PaC's desire to perform the mobility
optimization. In 
   the absence of Session-Id AVP in this message, PANA session takes its

   usual course (i.e., EAP-based authentication is performed).

   If PAA receives a session identifier in the PANA-Start-Answer
   message, and it is configured to enable this optimization, it
   SHOULD retrieve the PANA session attributes from the anchor PAA.
   Current PAA determines the identity of the anchor PAA by looking at
the
   DiameterIdentity part of the PANA session identifier. The MAC AVP can
   only be verified by the anchor PAA, therefore a copy of the PANA
messsage
   SHOULD be provided to the anchor PAA. The mechanism required to send
a 
   copy of the PANA-Start-Answer message from current PAA to the anchor
PAA, 
   and retrieve the session attributes is outside the scope of this 
   protocol. Seamoby Context Transfer Protocol [I-D.ietf-seamoby-ctp]
might 
   be useful for this purpose.

   When the anchor or current PAA is not configured to enable this 
   optimization, the current PAA can not retrieve the PANA session 
   attributes, or the PANA session has already expired (i.e., session 
   lifetime is zero), the PAA MUST send the PANA-Auth-Request message
with 
   the new session identifier and let the PANA exchange take its usual 
   course. This action will engage EAP-based authentication and create a
   fresh PANA session from scratch.

   In case the current PAA can retrieve the on-going PANA session
attributes
   from the anchor PAA, the PANA session continues with a PANA-Bind
   exchange. 

   As part of the context transfer, an intermediate AAA-Key material is 
   provided by the anchor PAA to the current PAA.  


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
                           

   In case there are two AAA-Keys generated from a NAP-ISP
authentication,
   the AAA-Key-int computation is:


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
                           Session-ID)

   
   The value of N depends on the integrity protection algorithm in
   use, i.e., N=160 for HMAC-SHA1. AAA-Key is the EAP-based
   key that was made available to anchor PAA and PaC as a result of
   the earlier EAP authentication. Due to the reliance on the AAA-Key,
this 
   optimization only works when PaC has performed an EAP-based 
   authentication on the anchor PAA. DiameterIdentity is the identifier
of
   the current PAA. Session-ID is the identifier of the PaC's PANA
session 
   with the anchor PAA. 

   Finally, current PAA and PaC compute the new AAA-Key by using the
nonce 
   values. PAA_Nonce is the randomly chosen value that MUST be carried
in a 
   Nonce AVP in the PANA-Bind-Request message.


   AAA-Key-new = The first N bits of
                 HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)


   New PANA_MAC_Key is computed based on the algorithm described in
Section 
   4.1.5, by using the new AAA-Key and the new Session-ID assigned by
the 
   current PAA. The MAC AVP contained in the PANA-Bind-Request and 
   PANA-Bind-Answer messages MUST be generated and verified by using the
new
   PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
   assigned by the current PAA. A new PANA session is created upon 
   successful completion of this exchange. 

   Note that correct operation of this optimization relies on many
factors,
   including applicability of authorization state from one network 
   attachment to another. [I-D.ietf-eap-keying] identifies this
operation as 
   "fast handoff" and provides deployment considerations. Operators are 
   recommended to take those guidelines into account when using this 
   optimization in their networks. 

   
[4] Change section 9.3.7 from:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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

to:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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


[5] Change 9.3.4:

Change:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Cookie ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]


To:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Session-Id ] 
                       [ Cookie ]
                       [ Nonce ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]
                   0*1 <MAC>                    


[6] Update the AVP occurrence table from:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |








To:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |



And add a line:

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Nonce               |  0   |  0   |  0  |  0  |  0  |
     



[7] Add 9.4.18:

9.4.18 Nonce AVP

   The Nonce AVP (Code 1041) is of type OctetString. The data contains
   a randomly generated value in opaque format. The data length MUST be 
   between 8 and 256 bytes inclusive.



[8] Add to references:

[I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt


[9] Add to Security Considerations section:

i) Mobility optimization

The mobility optimization described in Section 4.9 involves an anchor
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the anchor PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised anchor PAA along with
the 
intercepted nonce values leads to the compromise of AAA-Key-new.
Operators 
should be aware of the potential risk of using this optimization. An
operator can reduce the risk exposure by forcing the PaC to perform an 
EAP-based authentication immediately after the optimized PANA execution.



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



From pana-admin@ietf.org  Wed May  5 02:53:59 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25167
	for <pana-archive@lists.ietf.org>; Wed, 5 May 2004 02:53:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLG6Z-0006d0-7n; Wed, 05 May 2004 02:42:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLFz0-0003nD-GN
	for pana@optimus.ietf.org; Wed, 05 May 2004 02:34:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24186
	for <pana@ietf.org>; Wed, 5 May 2004 02:34:15 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLFyw-0001C8-PW
	for pana@ietf.org; Wed, 05 May 2004 02:34:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLFy4-000133-00
	for pana@ietf.org; Wed, 05 May 2004 02:33:21 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLFxa-0000tc-00
	for pana@ietf.org; Wed, 05 May 2004 02:32:50 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i456WjB21832;
	Wed, 5 May 2004 09:32:45 +0300 (EET DST)
X-Scanned: Wed, 5 May 2004 09:32:27 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i456WRMx019601;
	Wed, 5 May 2004 09:32:27 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00bXEkcr; Wed, 05 May 2004 09:32:26 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i456WPH19015;
	Wed, 5 May 2004 09:32:25 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 5 May 2004 09:32:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
Date: Wed, 5 May 2004 09:32:19 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 58 and issue 74: proposed text (take 4)
Thread-Index: AcQyQ2B/zqbrygmiQrqNi/UufsPgwAAJRJAA
To: <alper.yegin@samsung.com>, <Julien.Bournelle@int-evry.fr>
Cc: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 05 May 2004 06:32:22.0830 (UTC) FILETIME=[B93384E0:01C4326A]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME 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

Ok, great. For this to be repeatable, I think=20
that the AAA-Key-new should become the as the=20
'AAA-Key' for the remaining time of the session.=20
Thus, take this sentence away: "Due to the=20
reliance on the AAA-Key, this optimization=20
only works when PaC has performed an EAP-based=20
authentication on the anchor PAA". The new AAA-Key=20
is not as strong as the original one, but on the=20
other hand PANA session lifetime has not changed=20
either (the key lifetime is not reseted).

   "The value of N depends on the integrity protection algorithm in
   use, i.e., N=3D160 for HMAC-SHA1. AAA-Key is the EAP-based
   key that was made available to anchor PAA and PaC as a result of
   the earlier EAP authentication. DiameterIdentity is the identifier of
   the current PAA. Session-ID is the identifier of the PaC's PANA =
session=20
   with the anchor PAA."



- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper.yegin@samsung.com]
> Sent: 05 May, 2004 04:50
> To: Forsberg Dan (Nokia-NRC/Helsinki); Julien.Bournelle@int-evry.fr
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
>=20
>=20
> Updated the text based on the latest comments.....
>=20
> [1] Add to 4.1.1:
>=20
>    o Nonce AVP: contains a randomly chosen value.
>=20
>=20
> [2] New text for section 4.9:
>=20
> 4.9 Mobility Handling
>=20
>    A mobile PaC's AAA performance can be enhanced by deploying a=20
>    context-transfer-based mechanism, where some session=20
> attributes are=20
>    transferred from a previous PAA to the current one in=20
> order to avoid=20
>    performing a full EAP authentication (reactive approach).=20
> Additional=20
>    mechanisms that are based on the proactive AAA state=20
> establishment at
>=20
>    one or more candidate PAAs may be developed in the future=20
>    [I-D.irtf-aaaarch-handoff]. The details of a=20
> context-transfer-based=20
>    mechanism is provided in this section.
>=20
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume=20
>    its ongoing PANA session without running EAP MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message.=20
> Along with
> the
>    Session-Id AVP, MAC and Nonce AVPs MUST be included in=20
> this message.=20
>    Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
>    is computed by using the PANA_MAC_Key shared between the PaC and a
>    previous (anchor) PAA that has an unexpired PANA session with the
> PaC.
>    This action signals PaC's desire to perform the mobility
> optimization. In=20
>    the absence of Session-Id AVP in this message, PANA=20
> session takes its
>=20
>    usual course (i.e., EAP-based authentication is performed).
>=20
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable this optimization, it
>    SHOULD retrieve the PANA session attributes from the anchor PAA.
>    Current PAA determines the identity of the anchor PAA by looking at
> the
>    DiameterIdentity part of the PANA session identifier. The=20
> MAC AVP can
>    only be verified by the anchor PAA, therefore a copy of the PANA
> messsage
>    SHOULD be provided to the anchor PAA. The mechanism=20
> required to send
> a=20
>    copy of the PANA-Start-Answer message from current PAA to=20
> the anchor
> PAA,=20
>    and retrieve the session attributes is outside the scope of this=20
>    protocol. Seamoby Context Transfer Protocol [I-D.ietf-seamoby-ctp]
> might=20
>    be useful for this purpose.
>=20
>    When the anchor or current PAA is not configured to enable this=20
>    optimization, the current PAA can not retrieve the PANA session=20
>    attributes, or the PANA session has already expired (i.e., session=20
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with=20
>    the new session identifier and let the PANA exchange take=20
> its usual=20
>    course. This action will engage EAP-based authentication=20
> and create a
>    fresh PANA session from scratch.
>=20
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the anchor PAA, the PANA session continues with a PANA-Bind
>    exchange.=20
>=20
>    As part of the context transfer, an intermediate AAA-Key=20
> material is=20
>    provided by the anchor PAA to the current PAA. =20
>=20
>=20
>    AAA-Key-int =3D The first N bits of=20
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
>                           =20
>=20
>    In case there are two AAA-Keys generated from a NAP-ISP
> authentication,
>    the AAA-Key-int computation is:
>=20
>=20
>    AAA-Key-int =3D The first N bits of=20
>                  HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity |=20
>                            Session-ID)
>=20
>   =20
>    The value of N depends on the integrity protection algorithm in
>    use, i.e., N=3D160 for HMAC-SHA1. AAA-Key is the EAP-based
>    key that was made available to anchor PAA and PaC as a result of
>    the earlier EAP authentication. Due to the reliance on the AAA-Key,
> this=20
>    optimization only works when PaC has performed an EAP-based=20
>    authentication on the anchor PAA. DiameterIdentity is the=20
> identifier
> of
>    the current PAA. Session-ID is the identifier of the PaC's PANA
> session=20
>    with the anchor PAA.=20
>=20
>    Finally, current PAA and PaC compute the new AAA-Key by using the
> nonce=20
>    values. PAA_Nonce is the randomly chosen value that MUST be carried
> in a=20
>    Nonce AVP in the PANA-Bind-Request message.
>=20
>=20
>    AAA-Key-new =3D The first N bits of
>                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)
>=20
>=20
>    New PANA_MAC_Key is computed based on the algorithm described in
> Section=20
>    4.1.5, by using the new AAA-Key and the new Session-ID assigned by
> the=20
>    current PAA. The MAC AVP contained in the PANA-Bind-Request and=20
>    PANA-Bind-Answer messages MUST be generated and verified=20
> by using the
> new
>    PANA_MAC_Key. Session-ID AVP MUST include a new session identifier=20
>    assigned by the current PAA. A new PANA session is created upon=20
>    successful completion of this exchange.=20
>=20
>    Note that correct operation of this optimization relies on many
> factors,
>    including applicability of authorization state from one network=20
>    attachment to another. [I-D.ietf-eap-keying] identifies this
> operation as=20
>    "fast handoff" and provides deployment considerations.=20
> Operators are=20
>    recommended to take those guidelines into account when using this=20
>    optimization in their networks.=20
>=20
>   =20
> [4] Change section 9.3.7 from:
>=20
> 9.3.7 PANA-Bind-Request (PBR)
>=20
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
>=20
>          PANA-Bind-Request ::=3D < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        { EAP-Payload }
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
>=20
> to:
>=20
> 9.3.7 PANA-Bind-Request (PBR)
>=20
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
>=20
>          PANA-Bind-Request ::=3D < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        [ EAP-Payload ]                   =20
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                        [ Nonce]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
>=20
>=20
> [5] Change 9.3.4:
>=20
> Change:
>=20
> 9.3.4 PANA-Start-Answer (PSA)
>=20
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in=20
> response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
>=20
>          PANA-Start-Answer ::=3D < PANA-Header: 2 [SEP] >
>                        [ Cookie ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>=20
>=20
> To:
>=20
> 9.3.4 PANA-Start-Answer (PSA)
>=20
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in=20
> response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
>=20
>          PANA-Start-Answer ::=3D < PANA-Header: 2 [SEP] >
>                        [ Session-Id ]=20
>                        [ Cookie ]
>                        [ Nonce ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>                    0*1 <MAC>                   =20
>=20
>=20
> [6] Update the AVP occurrence table from:
>=20
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
>       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> To:
>=20
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
>=20
>=20
>=20
> And add a line:
>=20
>                           +-------------------------------+
>                           |      Message                  |
>                           |       Type                    |
>                           +------+------+-----+-----+-----+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
>       --------------------+------+------+-----+-----+-----+
>       Nonce               |  0   |  0   |  0  |  0  |  0  |
>     =20
>=20
>=20
>=20
> [7] Add 9.4.18:
>=20
> 9.4.18 Nonce AVP
>=20
>    The Nonce AVP (Code 1041) is of type OctetString. The data contains
>    a randomly generated value in opaque format. The data=20
> length MUST be=20
>    between 8 and 256 bytes inclusive.
>=20
>=20
>=20
> [8] Add to references:
>=20
> [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
>=20
>=20
> [9] Add to Security Considerations section:
>=20
> i) Mobility optimization
>=20
> The mobility optimization described in Section 4.9 involves an anchor
> PAA=20
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks=20
> stemming from potential compromise of PAAs. Compromise of the current
> PAA=20
> does not yield compromise of the anchor PAA, as AAA-Key cannot be
> computed=20
> from a compromised AAA-Key-new. But a compromised anchor PAA=20
> along with
> the=20
> intercepted nonce values leads to the compromise of AAA-Key-new.
> Operators=20
> should be aware of the potential risk of using this optimization. An
> operator can reduce the risk exposure by forcing the PaC to=20
> perform an=20
> EAP-based authentication immediately after the optimized PANA=20
> execution.
>=20
>=20
>=20

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


From exim@www1.ietf.org  Wed May  5 03:01:31 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25578
	for <pana-archive@odin.ietf.org>; Wed, 5 May 2004 03:01:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLGKc-0002Ag-66
	for pana-archive@odin.ietf.org; Wed, 05 May 2004 02:56:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i456ubOu008342
	for pana-archive@odin.ietf.org; Wed, 5 May 2004 02:56:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLGJS-0001eH-FK
	for pana-web-archive@optimus.ietf.org; Wed, 05 May 2004 02:55:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25239
	for <pana-web-archive@ietf.org>; Wed, 5 May 2004 02:55:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLGJO-0004rM-Kd
	for pana-web-archive@ietf.org; Wed, 05 May 2004 02:55:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLGIR-0004gr-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 02:54:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLGHY-0004Wz-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 02:53:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLG6Z-0006d0-7n; Wed, 05 May 2004 02:42:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLFz0-0003nD-GN
	for pana@optimus.ietf.org; Wed, 05 May 2004 02:34:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24186
	for <pana@ietf.org>; Wed, 5 May 2004 02:34:15 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLFyw-0001C8-PW
	for pana@ietf.org; Wed, 05 May 2004 02:34:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLFy4-000133-00
	for pana@ietf.org; Wed, 05 May 2004 02:33:21 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLFxa-0000tc-00
	for pana@ietf.org; Wed, 05 May 2004 02:32:50 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i456WjB21832;
	Wed, 5 May 2004 09:32:45 +0300 (EET DST)
X-Scanned: Wed, 5 May 2004 09:32:27 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i456WRMx019601;
	Wed, 5 May 2004 09:32:27 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00bXEkcr; Wed, 05 May 2004 09:32:26 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i456WPH19015;
	Wed, 5 May 2004 09:32:25 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 5 May 2004 09:32:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
Date: Wed, 5 May 2004 09:32:19 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 58 and issue 74: proposed text (take 4)
Thread-Index: AcQyQ2B/zqbrygmiQrqNi/UufsPgwAAJRJAA
To: <alper.yegin@samsung.com>, <Julien.Bournelle@int-evry.fr>
Cc: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 05 May 2004 06:32:22.0830 (UTC) FILETIME=[B93384E0:01C4326A]
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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Ok, great. For this to be repeatable, I think=20
that the AAA-Key-new should become the as the=20
'AAA-Key' for the remaining time of the session.=20
Thus, take this sentence away: "Due to the=20
reliance on the AAA-Key, this optimization=20
only works when PaC has performed an EAP-based=20
authentication on the anchor PAA". The new AAA-Key=20
is not as strong as the original one, but on the=20
other hand PANA session lifetime has not changed=20
either (the key lifetime is not reseted).

   "The value of N depends on the integrity protection algorithm in
   use, i.e., N=3D160 for HMAC-SHA1. AAA-Key is the EAP-based
   key that was made available to anchor PAA and PaC as a result of
   the earlier EAP authentication. DiameterIdentity is the identifier of
   the current PAA. Session-ID is the identifier of the PaC's PANA =
session=20
   with the anchor PAA."



- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper.yegin@samsung.com]
> Sent: 05 May, 2004 04:50
> To: Forsberg Dan (Nokia-NRC/Helsinki); Julien.Bournelle@int-evry.fr
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 4)
>=20
>=20
> Updated the text based on the latest comments.....
>=20
> [1] Add to 4.1.1:
>=20
>    o Nonce AVP: contains a randomly chosen value.
>=20
>=20
> [2] New text for section 4.9:
>=20
> 4.9 Mobility Handling
>=20
>    A mobile PaC's AAA performance can be enhanced by deploying a=20
>    context-transfer-based mechanism, where some session=20
> attributes are=20
>    transferred from a previous PAA to the current one in=20
> order to avoid=20
>    performing a full EAP authentication (reactive approach).=20
> Additional=20
>    mechanisms that are based on the proactive AAA state=20
> establishment at
>=20
>    one or more candidate PAAs may be developed in the future=20
>    [I-D.irtf-aaaarch-handoff]. The details of a=20
> context-transfer-based=20
>    mechanism is provided in this section.
>=20
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume=20
>    its ongoing PANA session without running EAP MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message.=20
> Along with
> the
>    Session-Id AVP, MAC and Nonce AVPs MUST be included in=20
> this message.=20
>    Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
>    is computed by using the PANA_MAC_Key shared between the PaC and a
>    previous (anchor) PAA that has an unexpired PANA session with the
> PaC.
>    This action signals PaC's desire to perform the mobility
> optimization. In=20
>    the absence of Session-Id AVP in this message, PANA=20
> session takes its
>=20
>    usual course (i.e., EAP-based authentication is performed).
>=20
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable this optimization, it
>    SHOULD retrieve the PANA session attributes from the anchor PAA.
>    Current PAA determines the identity of the anchor PAA by looking at
> the
>    DiameterIdentity part of the PANA session identifier. The=20
> MAC AVP can
>    only be verified by the anchor PAA, therefore a copy of the PANA
> messsage
>    SHOULD be provided to the anchor PAA. The mechanism=20
> required to send
> a=20
>    copy of the PANA-Start-Answer message from current PAA to=20
> the anchor
> PAA,=20
>    and retrieve the session attributes is outside the scope of this=20
>    protocol. Seamoby Context Transfer Protocol [I-D.ietf-seamoby-ctp]
> might=20
>    be useful for this purpose.
>=20
>    When the anchor or current PAA is not configured to enable this=20
>    optimization, the current PAA can not retrieve the PANA session=20
>    attributes, or the PANA session has already expired (i.e., session=20
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with=20
>    the new session identifier and let the PANA exchange take=20
> its usual=20
>    course. This action will engage EAP-based authentication=20
> and create a
>    fresh PANA session from scratch.
>=20
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the anchor PAA, the PANA session continues with a PANA-Bind
>    exchange.=20
>=20
>    As part of the context transfer, an intermediate AAA-Key=20
> material is=20
>    provided by the anchor PAA to the current PAA. =20
>=20
>=20
>    AAA-Key-int =3D The first N bits of=20
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
>                           =20
>=20
>    In case there are two AAA-Keys generated from a NAP-ISP
> authentication,
>    the AAA-Key-int computation is:
>=20
>=20
>    AAA-Key-int =3D The first N bits of=20
>                  HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity |=20
>                            Session-ID)
>=20
>   =20
>    The value of N depends on the integrity protection algorithm in
>    use, i.e., N=3D160 for HMAC-SHA1. AAA-Key is the EAP-based
>    key that was made available to anchor PAA and PaC as a result of
>    the earlier EAP authentication. Due to the reliance on the AAA-Key,
> this=20
>    optimization only works when PaC has performed an EAP-based=20
>    authentication on the anchor PAA. DiameterIdentity is the=20
> identifier
> of
>    the current PAA. Session-ID is the identifier of the PaC's PANA
> session=20
>    with the anchor PAA.=20
>=20
>    Finally, current PAA and PaC compute the new AAA-Key by using the
> nonce=20
>    values. PAA_Nonce is the randomly chosen value that MUST be carried
> in a=20
>    Nonce AVP in the PANA-Bind-Request message.
>=20
>=20
>    AAA-Key-new =3D The first N bits of
>                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)
>=20
>=20
>    New PANA_MAC_Key is computed based on the algorithm described in
> Section=20
>    4.1.5, by using the new AAA-Key and the new Session-ID assigned by
> the=20
>    current PAA. The MAC AVP contained in the PANA-Bind-Request and=20
>    PANA-Bind-Answer messages MUST be generated and verified=20
> by using the
> new
>    PANA_MAC_Key. Session-ID AVP MUST include a new session identifier=20
>    assigned by the current PAA. A new PANA session is created upon=20
>    successful completion of this exchange.=20
>=20
>    Note that correct operation of this optimization relies on many
> factors,
>    including applicability of authorization state from one network=20
>    attachment to another. [I-D.ietf-eap-keying] identifies this
> operation as=20
>    "fast handoff" and provides deployment considerations.=20
> Operators are=20
>    recommended to take those guidelines into account when using this=20
>    optimization in their networks.=20
>=20
>   =20
> [4] Change section 9.3.7 from:
>=20
> 9.3.7 PANA-Bind-Request (PBR)
>=20
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
>=20
>          PANA-Bind-Request ::=3D < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        { EAP-Payload }
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
>=20
> to:
>=20
> 9.3.7 PANA-Bind-Request (PBR)
>=20
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
>=20
>          PANA-Bind-Request ::=3D < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        [ EAP-Payload ]                   =20
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                        [ Nonce]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
>=20
>=20
> [5] Change 9.3.4:
>=20
> Change:
>=20
> 9.3.4 PANA-Start-Answer (PSA)
>=20
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in=20
> response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
>=20
>          PANA-Start-Answer ::=3D < PANA-Header: 2 [SEP] >
>                        [ Cookie ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>=20
>=20
> To:
>=20
> 9.3.4 PANA-Start-Answer (PSA)
>=20
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in=20
> response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
>=20
>          PANA-Start-Answer ::=3D < PANA-Header: 2 [SEP] >
>                        [ Session-Id ]=20
>                        [ Cookie ]
>                        [ Nonce ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>                    0*1 <MAC>                   =20
>=20
>=20
> [6] Update the AVP occurrence table from:
>=20
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
>       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> To:
>=20
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
>=20
>=20
>=20
> And add a line:
>=20
>                           +-------------------------------+
>                           |      Message                  |
>                           |       Type                    |
>                           +------+------+-----+-----+-----+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
>       --------------------+------+------+-----+-----+-----+
>       Nonce               |  0   |  0   |  0  |  0  |  0  |
>     =20
>=20
>=20
>=20
> [7] Add 9.4.18:
>=20
> 9.4.18 Nonce AVP
>=20
>    The Nonce AVP (Code 1041) is of type OctetString. The data contains
>    a randomly generated value in opaque format. The data=20
> length MUST be=20
>    between 8 and 256 bytes inclusive.
>=20
>=20
>=20
> [8] Add to references:
>=20
> [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
>=20
>=20
> [9] Add to Security Considerations section:
>=20
> i) Mobility optimization
>=20
> The mobility optimization described in Section 4.9 involves an anchor
> PAA=20
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks=20
> stemming from potential compromise of PAAs. Compromise of the current
> PAA=20
> does not yield compromise of the anchor PAA, as AAA-Key cannot be
> computed=20
> from a compromised AAA-Key-new. But a compromised anchor PAA=20
> along with
> the=20
> intercepted nonce values leads to the compromise of AAA-Key-new.
> Operators=20
> should be aware of the potential risk of using this optimization. An
> operator can reduce the risk exposure by forcing the PaC to=20
> perform an=20
> EAP-based authentication immediately after the optimized PANA=20
> execution.
>=20
>=20
>=20

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



From pana-admin@ietf.org  Wed May  5 15:28:44 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06949
	for <pana-archive@lists.ietf.org>; Wed, 5 May 2004 15:28:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLRqD-0006Hp-Tz; Wed, 05 May 2004 15:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLRgV-0006lb-3h
	for pana@optimus.ietf.org; Wed, 05 May 2004 15:03:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05071
	for <pana@ietf.org>; Wed, 5 May 2004 15:03:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLRgS-000670-58
	for pana@ietf.org; Wed, 05 May 2004 15:03:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLRfY-0005qQ-00
	for pana@ietf.org; Wed, 05 May 2004 15:03:01 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLRf3-0005Yt-00
	for pana@ietf.org; Wed, 05 May 2004 15:02:29 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX900D058VADS@mailout3.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 04:01:58 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX900MJ48V85D@mailout3.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 04:01:57 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX900DBU8V5OO@mmp2.samsung.com> for pana@ietf.org;
 Thu, 06 May 2004 04:01:56 +0900 (KST)
Date: Wed, 05 May 2004 12:01:53 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <000801c432d3$6f4cd110$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

The "anchor" PAA model was a leftover from the time we were using EMSK.
Now that we are not using this key, I think we can convert the scheme to
"chaining" as Dan suggests. 

The text is updated accordingly. Let's make sure we are not missing
something.

Alper



[1] Add to 4.1.1:

   o Nonce AVP: contains a randomly chosen value.


[2] New text for section 4.9:

4.9 Mobility Handling

   A mobile PaC's AAA performance can be enhanced by deploying a 
   context-transfer-based mechanism, where some session attributes are 
   transferred from the previous PAA to the current one in order to
avoid 
   performing a full EAP authentication (reactive approach). Additional 
   mechanisms that are based on the proactive AAA state establishment at

   one or more candidate PAAs may be developed in the future 
   [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
   mechanism is provided in this section.

   Upon changing its point of attachment, a PaC that wants to quickly
resume 
   its ongoing PANA session without running EAP MAY send its unexpired
   PANA session identifier in its PANA-Start-Answer message. Along with
the
   Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
   Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
   is computed by using the PANA_MAC_Key shared between the PaC and its
   previous PAA that has an unexpired PANA session with the PaC.
   This action signals PaC's desire to perform the mobility
optimization. In 
   the absence of Session-Id AVP in this message, PANA session takes its

   usual course (i.e., EAP-based authentication is performed).

   If PAA receives a session identifier in the PANA-Start-Answer
   message, and it is configured to enable this optimization, it
   SHOULD retrieve the PANA session attributes from the previous PAA.
   Current PAA determines the identity of the previous PAA by looking at
the
   DiameterIdentity part of the PANA session identifier. The MAC AVP can
   only be verified by the previous PAA, therefore a copy of the PANA 
   message SHOULD be provided to the previous PAA. The mechanism
required to 
   send a copy of the PANA-Start-Answer message from current PAA to the 
   previous PAA, and retrieve the session attributes is outside the
scope of 
   PANA protocol. Seamoby Context Transfer Protocol
[I-D.ietf-seamoby-ctp] 
   might be useful for this purpose.

   When the previous or current PAA is not configured to enable this 
   optimization, the current PAA can not retrieve the PANA session 
   attributes, or the PANA session has already expired (i.e., session 
   lifetime is zero), the PAA MUST send the PANA-Auth-Request message
with 
   a new session identifier and let the PANA exchange take its usual 
   course. This action will engage EAP-based authentication and create a
   fresh PANA session from scratch.

   In case the current PAA can retrieve the on-going PANA session
attributes
   from the previous PAA, the PANA session continues with a PANA-Bind
   exchange. 

   As part of the context transfer, an intermediate AAA-Key material is 
   provided by the previous PAA to the current PAA.  


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
                           

   In case there are two AAA-Keys generated from a NAP-ISP
authentication,
   the AAA-Key-int computation is:


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
                           Session-ID)

   
   The value of N depends on the integrity protection algorithm in
   use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the identifier of
   the current PAA. Session-ID is the identifier of the PaC's PANA
session 
   with the previous PAA. 

   The current PAA and PaC compute the new AAA-Key by using the nonce 
   values and the AAA-Key-int. PAA_Nonce is the randomly chosen value
that 
   MUST be carried in a Nonce AVP in the PANA-Bind-Request message.


   AAA-Key-new = The first N bits of
                 HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)


   New PANA_MAC_Key is computed based on the algorithm described in
Section 
   4.1.5, by using the new AAA-Key and the new Session-ID assigned by
the 
   current PAA. The MAC AVP contained in the PANA-Bind-Request and 
   PANA-Bind-Answer messages MUST be generated and verified by using the
new
   PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
   assigned by the current PAA. A new PANA session is created upon 
   successful completion of this exchange. 

   Note that correct operation of this optimization relies on many
factors,
   including applicability of authorization state from one network 
   attachment to another. [I-D.ietf-eap-keying] identifies this
operation as 
   "fast handoff" and provides deployment considerations. Operators are 
   recommended to take those guidelines into account when using this 
   optimization in their networks. 

   
[4] Change section 9.3.7 from:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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

to:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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


[5] Change 9.3.4:

Change:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Cookie ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]


To:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Session-Id ] 
                       [ Cookie ]
                       [ Nonce ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]
                   0*1 <MAC>                    


[6] Update the AVP occurrence table from:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |








To:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |



And add a line:

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Nonce               |  0   |  0   |  0  |  0  |  0  |
     



[7] Add 9.4.18:

9.4.18 Nonce AVP

   The Nonce AVP (Code 1041) is of type OctetString. The data contains
   a randomly generated value in opaque format. The data length MUST be 
   between 8 and 256 bytes inclusive.



[8] Add to references:

[I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt


[9] Add to Security Considerations section:

i) Mobility optimization

The mobility optimization described in Section 4.9 involves the previous
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the previous PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised previous PAA along
with 
the intercepted nonce values leads to the compromise of AAA-Key-new. 
Operators should be aware of the potential risk of using this
optimization. 
An operator can reduce the risk exposure by forcing the PaC to perform
an 
EAP-based authentication immediately after the optimized PANA execution.



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


From exim@www1.ietf.org  Wed May  5 15:44:43 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07849
	for <pana-archive@odin.ietf.org>; Wed, 5 May 2004 15:44:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSC0-0008Nu-TJ
	for pana-archive@odin.ietf.org; Wed, 05 May 2004 15:36:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i45JaWTB032231
	for pana-archive@odin.ietf.org; Wed, 5 May 2004 15:36:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLS5Y-0005V8-Kn
	for pana-web-archive@optimus.ietf.org; Wed, 05 May 2004 15:29:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06995
	for <pana-web-archive@ietf.org>; Wed, 5 May 2004 15:29:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLS5X-0005Sh-Bw
	for pana-web-archive@ietf.org; Wed, 05 May 2004 15:29:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLS4b-0005Bj-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 15:28:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLS3y-0004vI-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 15:28:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLRqD-0006Hp-Tz; Wed, 05 May 2004 15:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLRgV-0006lb-3h
	for pana@optimus.ietf.org; Wed, 05 May 2004 15:03:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05071
	for <pana@ietf.org>; Wed, 5 May 2004 15:03:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLRgS-000670-58
	for pana@ietf.org; Wed, 05 May 2004 15:03:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLRfY-0005qQ-00
	for pana@ietf.org; Wed, 05 May 2004 15:03:01 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLRf3-0005Yt-00
	for pana@ietf.org; Wed, 05 May 2004 15:02:29 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX900D058VADS@mailout3.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 04:01:58 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX900MJ48V85D@mailout3.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 04:01:57 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX900DBU8V5OO@mmp2.samsung.com> for pana@ietf.org;
 Thu, 06 May 2004 04:01:56 +0900 (KST)
Date: Wed, 05 May 2004 12:01:53 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <000801c432d3$6f4cd110$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

The "anchor" PAA model was a leftover from the time we were using EMSK.
Now that we are not using this key, I think we can convert the scheme to
"chaining" as Dan suggests. 

The text is updated accordingly. Let's make sure we are not missing
something.

Alper



[1] Add to 4.1.1:

   o Nonce AVP: contains a randomly chosen value.


[2] New text for section 4.9:

4.9 Mobility Handling

   A mobile PaC's AAA performance can be enhanced by deploying a 
   context-transfer-based mechanism, where some session attributes are 
   transferred from the previous PAA to the current one in order to
avoid 
   performing a full EAP authentication (reactive approach). Additional 
   mechanisms that are based on the proactive AAA state establishment at

   one or more candidate PAAs may be developed in the future 
   [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
   mechanism is provided in this section.

   Upon changing its point of attachment, a PaC that wants to quickly
resume 
   its ongoing PANA session without running EAP MAY send its unexpired
   PANA session identifier in its PANA-Start-Answer message. Along with
the
   Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
   Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
   is computed by using the PANA_MAC_Key shared between the PaC and its
   previous PAA that has an unexpired PANA session with the PaC.
   This action signals PaC's desire to perform the mobility
optimization. In 
   the absence of Session-Id AVP in this message, PANA session takes its

   usual course (i.e., EAP-based authentication is performed).

   If PAA receives a session identifier in the PANA-Start-Answer
   message, and it is configured to enable this optimization, it
   SHOULD retrieve the PANA session attributes from the previous PAA.
   Current PAA determines the identity of the previous PAA by looking at
the
   DiameterIdentity part of the PANA session identifier. The MAC AVP can
   only be verified by the previous PAA, therefore a copy of the PANA 
   message SHOULD be provided to the previous PAA. The mechanism
required to 
   send a copy of the PANA-Start-Answer message from current PAA to the 
   previous PAA, and retrieve the session attributes is outside the
scope of 
   PANA protocol. Seamoby Context Transfer Protocol
[I-D.ietf-seamoby-ctp] 
   might be useful for this purpose.

   When the previous or current PAA is not configured to enable this 
   optimization, the current PAA can not retrieve the PANA session 
   attributes, or the PANA session has already expired (i.e., session 
   lifetime is zero), the PAA MUST send the PANA-Auth-Request message
with 
   a new session identifier and let the PANA exchange take its usual 
   course. This action will engage EAP-based authentication and create a
   fresh PANA session from scratch.

   In case the current PAA can retrieve the on-going PANA session
attributes
   from the previous PAA, the PANA session continues with a PANA-Bind
   exchange. 

   As part of the context transfer, an intermediate AAA-Key material is 
   provided by the previous PAA to the current PAA.  


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
                           

   In case there are two AAA-Keys generated from a NAP-ISP
authentication,
   the AAA-Key-int computation is:


   AAA-Key-int = The first N bits of 
                 HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
                           Session-ID)

   
   The value of N depends on the integrity protection algorithm in
   use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the identifier of
   the current PAA. Session-ID is the identifier of the PaC's PANA
session 
   with the previous PAA. 

   The current PAA and PaC compute the new AAA-Key by using the nonce 
   values and the AAA-Key-int. PAA_Nonce is the randomly chosen value
that 
   MUST be carried in a Nonce AVP in the PANA-Bind-Request message.


   AAA-Key-new = The first N bits of
                 HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)


   New PANA_MAC_Key is computed based on the algorithm described in
Section 
   4.1.5, by using the new AAA-Key and the new Session-ID assigned by
the 
   current PAA. The MAC AVP contained in the PANA-Bind-Request and 
   PANA-Bind-Answer messages MUST be generated and verified by using the
new
   PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
   assigned by the current PAA. A new PANA session is created upon 
   successful completion of this exchange. 

   Note that correct operation of this optimization relies on many
factors,
   including applicability of authorization state from one network 
   attachment to another. [I-D.ietf-eap-keying] identifies this
operation as 
   "fast handoff" and provides deployment considerations. Operators are 
   recommended to take those guidelines into account when using this 
   optimization in their networks. 

   
[4] Change section 9.3.7 from:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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

to:

9.3.7 PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

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


[5] Change 9.3.4:

Change:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Cookie ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]


To:

9.3.4 PANA-Start-Answer (PSA)

   PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
   a PANA-Start-Request message.  The PANA_start message transmission
   sequence number field is copied to the received sequence number
   field.  The transmission sequence number is set to initial random
   value.

         PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
                       [ Session-Id ] 
                       [ Cookie ]
                       [ Nonce ]
                       [ EAP-Payload ]
                       [ ISP-Information ]
                    *  [ AVP ]
                   0*1 <MAC>                    


[6] Update the AVP occurrence table from:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |








To:

                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |



And add a line:

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Nonce               |  0   |  0   |  0  |  0  |  0  |
     



[7] Add 9.4.18:

9.4.18 Nonce AVP

   The Nonce AVP (Code 1041) is of type OctetString. The data contains
   a randomly generated value in opaque format. The data length MUST be 
   between 8 and 256 bytes inclusive.



[8] Add to references:

[I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt


[9] Add to Security Considerations section:

i) Mobility optimization

The mobility optimization described in Section 4.9 involves the previous
PAA 
providing a AAA-Key to the current PAA of the PaC. There are security
risks 
stemming from potential compromise of PAAs. Compromise of the current
PAA 
does not yield compromise of the previous PAA, as AAA-Key cannot be
computed 
from a compromised AAA-Key-new. But a compromised previous PAA along
with 
the intercepted nonce values leads to the compromise of AAA-Key-new. 
Operators should be aware of the potential risk of using this
optimization. 
An operator can reduce the risk exposure by forcing the PaC to perform
an 
EAP-based authentication immediately after the optimized PANA execution.



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



From pana-admin@ietf.org  Wed May  5 16:00:02 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08704
	for <pana-archive@lists.ietf.org>; Wed, 5 May 2004 16:00:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSSw-0008QV-5b; Wed, 05 May 2004 15:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSK7-0004LE-NB
	for pana@optimus.ietf.org; Wed, 05 May 2004 15:44:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07882
	for <pana@ietf.org>; Wed, 5 May 2004 15:44:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLSK6-00024n-47
	for pana@ietf.org; Wed, 05 May 2004 15:44:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLSJA-0001mV-00
	for pana@ietf.org; Wed, 05 May 2004 15:43:57 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLSIH-0001UB-00
	for pana@ietf.org; Wed, 05 May 2004 15:43:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i45Jh0gH025339;
	Thu, 6 May 2004 04:43:00 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i45Jh0B3022758;
	Thu, 6 May 2004 04:43:00 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA22756 ; Thu, 6 May 2004 04:43:00 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14882; Thu, 6 May 2004 04:42:59 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA00075; Thu, 6 May 2004 04:42:59 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i45JgwDG023191;
	Thu, 6 May 2004 04:42:58 +0900 (JST)
Received: from steelhead ([172.30.24.116]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HX9000KWARIVH@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 04:42:57 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLSH5-0005G9-00; Wed, 05 May 2004 12:41:47 -0700
Date: Wed, 05 May 2004 12:41:47 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <000801c432d3$6f4cd110$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr,
        yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20040505194146.GC18466@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr, yohba@tari.toshiba.com,
 pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
 <000801c432d3$6f4cd110$991d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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, May 05, 2004 at 12:01:53PM -0700, Alper Yegin wrote:
> The "anchor" PAA model was a leftover from the time we were using EMSK.
> Now that we are not using this key, I think we can convert the scheme to
> "chaining" as Dan suggests. 

OK.  Please see further comments below.

> 
> The text is updated accordingly. Let's make sure we are not missing
> something.
> 
> Alper
> 
> 
> 
> [1] Add to 4.1.1:
> 
>    o Nonce AVP: contains a randomly chosen value.
> 
> 
> [2] New text for section 4.9:
> 
> 4.9 Mobility Handling
> 
>    A mobile PaC's AAA performance can be enhanced by deploying a 
>    context-transfer-based mechanism, where some session attributes are 
>    transferred from the previous PAA to the current one in order to
> avoid 
>    performing a full EAP authentication (reactive approach). Additional 
>    mechanisms that are based on the proactive AAA state establishment at
> 
>    one or more candidate PAAs may be developed in the future 
>    [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
>    mechanism is provided in this section.
> 
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume 
>    its ongoing PANA session without running EAP MAY send its unexpired
>    PANA session identifier in its PANA-Start-Answer message. Along with
> the
>    Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
>    Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
>    is computed by using the PANA_MAC_Key shared between the PaC and its
>    previous PAA that has an unexpired PANA session with the PaC.
>    This action signals PaC's desire to perform the mobility
> optimization. In 
>    the absence of Session-Id AVP in this message, PANA session takes its
> 
>    usual course (i.e., EAP-based authentication is performed).
> 
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable this optimization, it
>    SHOULD retrieve the PANA session attributes from the previous PAA.
>    Current PAA determines the identity of the previous PAA by looking at
> the
>    DiameterIdentity part of the PANA session identifier. The MAC AVP can
>    only be verified by the previous PAA, therefore a copy of the PANA 
>    message SHOULD be provided to the previous PAA. The mechanism
> required to 
>    send a copy of the PANA-Start-Answer message from current PAA to the 
>    previous PAA, and retrieve the session attributes is outside the
> scope of 
>    PANA protocol. Seamoby Context Transfer Protocol
> [I-D.ietf-seamoby-ctp] 
>    might be useful for this purpose.
> 
>    When the previous or current PAA is not configured to enable this 
>    optimization, the current PAA can not retrieve the PANA session 
>    attributes, or the PANA session has already expired (i.e., session 
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with 
>    a new session identifier and let the PANA exchange take its usual 
>    course. This action will engage EAP-based authentication and create a
>    fresh PANA session from scratch.
> 
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the previous PAA, the PANA session continues with a PANA-Bind
>    exchange. 
> 
>    As part of the context transfer, an intermediate AAA-Key material is 
>    provided by the previous PAA to the current PAA.  
> 
> 
>    AAA-Key-int = The first N bits of 
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
>                            
> 
>    In case there are two AAA-Keys generated from a NAP-ISP
> authentication,
>    the AAA-Key-int computation is:
> 
> 
>    AAA-Key-int = The first N bits of 
>                  HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
>                            Session-ID)

I noticed that three parameters are given to the HMAC-SHA1 function.
There should be two parameters instead.  There would be two
ways to fix this.

Algorithm 1:

     AAA-Key-int = The first N bits of 
                   HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity | 
                             Session-ID)

Algorithm 2:

     AAA-Key-int = The first N bits of 
                   HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)

     where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
     (Issue: How to combine the keys?)

Which is good, or any other algorithm?

Note that the same fix should be applied to the current PANA_MAC_Key
computation described in 4.1.5.

> 
>    
>    The value of N depends on the integrity protection algorithm in
>    use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the identifier of
>    the current PAA. Session-ID is the identifier of the PaC's PANA
> session 
>    with the previous PAA. 
> 
>    The current PAA and PaC compute the new AAA-Key by using the nonce 
>    values and the AAA-Key-int. PAA_Nonce is the randomly chosen value
> that 
>    MUST be carried in a Nonce AVP in the PANA-Bind-Request message.
> 
> 
>    AAA-Key-new = The first N bits of
>                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)

Again there are three parameters.  

This should be:

     AAA-Key-new = The first N bits of
                   HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)


Yoshihiro Ohba


> 
> 
>    New PANA_MAC_Key is computed based on the algorithm described in
> Section 
>    4.1.5, by using the new AAA-Key and the new Session-ID assigned by
> the 
>    current PAA. The MAC AVP contained in the PANA-Bind-Request and 
>    PANA-Bind-Answer messages MUST be generated and verified by using the
> new
>    PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
>    assigned by the current PAA. A new PANA session is created upon 
>    successful completion of this exchange. 
> 
>    Note that correct operation of this optimization relies on many
> factors,
>    including applicability of authorization state from one network 
>    attachment to another. [I-D.ietf-eap-keying] identifies this
> operation as 
>    "fast handoff" and provides deployment considerations. Operators are 
>    recommended to take those guidelines into account when using this 
>    optimization in their networks. 
> 
>    
> [4] Change section 9.3.7 from:
> 
> 9.3.7 PANA-Bind-Request (PBR)
> 
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> 
>          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        { EAP-Payload }
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> to:
> 
> 9.3.7 PANA-Bind-Request (PBR)
> 
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> 
>          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        [ EAP-Payload ]                    
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                        [ Nonce]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> [5] Change 9.3.4:
> 
> Change:
> 
> 9.3.4 PANA-Start-Answer (PSA)
> 
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
> 
>          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
>                        [ Cookie ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
> 
> 
> To:
> 
> 9.3.4 PANA-Start-Answer (PSA)
> 
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
> 
>          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
>                        [ Session-Id ] 
>                        [ Cookie ]
>                        [ Nonce ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>                    0*1 <MAC>                    
> 
> 
> [6] Update the AVP occurrence table from:
> 
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
>       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
> 
> 
> 
> 
> 
> 
> 
> 
> To:
> 
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
> 
> 
> 
> And add a line:
> 
>                           +-------------------------------+
>                           |      Message                  |
>                           |       Type                    |
>                           +------+------+-----+-----+-----+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
>       --------------------+------+------+-----+-----+-----+
>       Nonce               |  0   |  0   |  0  |  0  |  0  |
>      
> 
> 
> 
> [7] Add 9.4.18:
> 
> 9.4.18 Nonce AVP
> 
>    The Nonce AVP (Code 1041) is of type OctetString. The data contains
>    a randomly generated value in opaque format. The data length MUST be 
>    between 8 and 256 bytes inclusive.
> 
> 
> 
> [8] Add to references:
> 
> [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
> 
> 
> [9] Add to Security Considerations section:
> 
> i) Mobility optimization
> 
> The mobility optimization described in Section 4.9 involves the previous
> PAA 
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks 
> stemming from potential compromise of PAAs. Compromise of the current
> PAA 
> does not yield compromise of the previous PAA, as AAA-Key cannot be
> computed 
> from a compromised AAA-Key-new. But a compromised previous PAA along
> with 
> the intercepted nonce values leads to the compromise of AAA-Key-new. 
> Operators should be aware of the potential risk of using this
> optimization. 
> An operator can reduce the risk exposure by forcing the PaC to perform
> an 
> EAP-based authentication immediately after the optimized PANA execution.
> 
> 

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


From exim@www1.ietf.org  Wed May  5 16:12:05 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09340
	for <pana-archive@odin.ietf.org>; Wed, 5 May 2004 16:12:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSev-0005MW-HN
	for pana-archive@odin.ietf.org; Wed, 05 May 2004 16:06:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i45K6PU8020613
	for pana-archive@odin.ietf.org; Wed, 5 May 2004 16:06:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSZr-0002DC-ED
	for pana-web-archive@optimus.ietf.org; Wed, 05 May 2004 16:01:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08788
	for <pana-web-archive@ietf.org>; Wed, 5 May 2004 16:01:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLSZp-0006hP-VY
	for pana-web-archive@ietf.org; Wed, 05 May 2004 16:01:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLSYt-0006P0-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 16:00:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLSYH-00066Y-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 15:59:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSSw-0008QV-5b; Wed, 05 May 2004 15:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLSK7-0004LE-NB
	for pana@optimus.ietf.org; Wed, 05 May 2004 15:44:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07882
	for <pana@ietf.org>; Wed, 5 May 2004 15:44:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLSK6-00024n-47
	for pana@ietf.org; Wed, 05 May 2004 15:44:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLSJA-0001mV-00
	for pana@ietf.org; Wed, 05 May 2004 15:43:57 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLSIH-0001UB-00
	for pana@ietf.org; Wed, 05 May 2004 15:43:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i45Jh0gH025339;
	Thu, 6 May 2004 04:43:00 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i45Jh0B3022758;
	Thu, 6 May 2004 04:43:00 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA22756 ; Thu, 6 May 2004 04:43:00 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14882; Thu, 6 May 2004 04:42:59 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA00075; Thu, 6 May 2004 04:42:59 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i45JgwDG023191;
	Thu, 6 May 2004 04:42:58 +0900 (JST)
Received: from steelhead ([172.30.24.116]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HX9000KWARIVH@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 04:42:57 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLSH5-0005G9-00; Wed, 05 May 2004 12:41:47 -0700
Date: Wed, 05 May 2004 12:41:47 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <000801c432d3$6f4cd110$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr,
        yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20040505194146.GC18466@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr, yohba@tari.toshiba.com,
 pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C6E3@esebe008.ntc.nokia.com>
 <000801c432d3$6f4cd110$991d9069@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, May 05, 2004 at 12:01:53PM -0700, Alper Yegin wrote:
> The "anchor" PAA model was a leftover from the time we were using EMSK.
> Now that we are not using this key, I think we can convert the scheme to
> "chaining" as Dan suggests. 

OK.  Please see further comments below.

> 
> The text is updated accordingly. Let's make sure we are not missing
> something.
> 
> Alper
> 
> 
> 
> [1] Add to 4.1.1:
> 
>    o Nonce AVP: contains a randomly chosen value.
> 
> 
> [2] New text for section 4.9:
> 
> 4.9 Mobility Handling
> 
>    A mobile PaC's AAA performance can be enhanced by deploying a 
>    context-transfer-based mechanism, where some session attributes are 
>    transferred from the previous PAA to the current one in order to
> avoid 
>    performing a full EAP authentication (reactive approach). Additional 
>    mechanisms that are based on the proactive AAA state establishment at
> 
>    one or more candidate PAAs may be developed in the future 
>    [I-D.irtf-aaaarch-handoff]. The details of a context-transfer-based 
>    mechanism is provided in this section.
> 
>    Upon changing its point of attachment, a PaC that wants to quickly
> resume 
>    its ongoing PANA session without running EAP MAY send its unexpired
>    PANA session identifier in its PANA-Start-Answer message. Along with
> the
>    Session-Id AVP, MAC and Nonce AVPs MUST be included in this message. 
>    Nonce AVP carries a randomly chosen value (PaC_Nonce), and MAC AVP
>    is computed by using the PANA_MAC_Key shared between the PaC and its
>    previous PAA that has an unexpired PANA session with the PaC.
>    This action signals PaC's desire to perform the mobility
> optimization. In 
>    the absence of Session-Id AVP in this message, PANA session takes its
> 
>    usual course (i.e., EAP-based authentication is performed).
> 
>    If PAA receives a session identifier in the PANA-Start-Answer
>    message, and it is configured to enable this optimization, it
>    SHOULD retrieve the PANA session attributes from the previous PAA.
>    Current PAA determines the identity of the previous PAA by looking at
> the
>    DiameterIdentity part of the PANA session identifier. The MAC AVP can
>    only be verified by the previous PAA, therefore a copy of the PANA 
>    message SHOULD be provided to the previous PAA. The mechanism
> required to 
>    send a copy of the PANA-Start-Answer message from current PAA to the 
>    previous PAA, and retrieve the session attributes is outside the
> scope of 
>    PANA protocol. Seamoby Context Transfer Protocol
> [I-D.ietf-seamoby-ctp] 
>    might be useful for this purpose.
> 
>    When the previous or current PAA is not configured to enable this 
>    optimization, the current PAA can not retrieve the PANA session 
>    attributes, or the PANA session has already expired (i.e., session 
>    lifetime is zero), the PAA MUST send the PANA-Auth-Request message
> with 
>    a new session identifier and let the PANA exchange take its usual 
>    course. This action will engage EAP-based authentication and create a
>    fresh PANA session from scratch.
> 
>    In case the current PAA can retrieve the on-going PANA session
> attributes
>    from the previous PAA, the PANA session continues with a PANA-Bind
>    exchange. 
> 
>    As part of the context transfer, an intermediate AAA-Key material is 
>    provided by the previous PAA to the current PAA.  
> 
> 
>    AAA-Key-int = The first N bits of 
>                  HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
>                            
> 
>    In case there are two AAA-Keys generated from a NAP-ISP
> authentication,
>    the AAA-Key-int computation is:
> 
> 
>    AAA-Key-int = The first N bits of 
>                  HMAC-SHA1(AAA-Key1, AAA-Key2, DiameterIdentity | 
>                            Session-ID)

I noticed that three parameters are given to the HMAC-SHA1 function.
There should be two parameters instead.  There would be two
ways to fix this.

Algorithm 1:

     AAA-Key-int = The first N bits of 
                   HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity | 
                             Session-ID)

Algorithm 2:

     AAA-Key-int = The first N bits of 
                   HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)

     where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
     (Issue: How to combine the keys?)

Which is good, or any other algorithm?

Note that the same fix should be applied to the current PANA_MAC_Key
computation described in 4.1.5.

> 
>    
>    The value of N depends on the integrity protection algorithm in
>    use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the identifier of
>    the current PAA. Session-ID is the identifier of the PaC's PANA
> session 
>    with the previous PAA. 
> 
>    The current PAA and PaC compute the new AAA-Key by using the nonce 
>    values and the AAA-Key-int. PAA_Nonce is the randomly chosen value
> that 
>    MUST be carried in a Nonce AVP in the PANA-Bind-Request message.
> 
> 
>    AAA-Key-new = The first N bits of
>                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)

Again there are three parameters.  

This should be:

     AAA-Key-new = The first N bits of
                   HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)


Yoshihiro Ohba


> 
> 
>    New PANA_MAC_Key is computed based on the algorithm described in
> Section 
>    4.1.5, by using the new AAA-Key and the new Session-ID assigned by
> the 
>    current PAA. The MAC AVP contained in the PANA-Bind-Request and 
>    PANA-Bind-Answer messages MUST be generated and verified by using the
> new
>    PANA_MAC_Key. Session-ID AVP MUST include a new session identifier 
>    assigned by the current PAA. A new PANA session is created upon 
>    successful completion of this exchange. 
> 
>    Note that correct operation of this optimization relies on many
> factors,
>    including applicability of authorization state from one network 
>    attachment to another. [I-D.ietf-eap-keying] identifies this
> operation as 
>    "fast handoff" and provides deployment considerations. Operators are 
>    recommended to take those guidelines into account when using this 
>    optimization in their networks. 
> 
>    
> [4] Change section 9.3.7 from:
> 
> 9.3.7 PANA-Bind-Request (PBR)
> 
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> 
>          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        { EAP-Payload }
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> to:
> 
> 9.3.7 PANA-Bind-Request (PBR)
> 
>    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> 
>          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
>                        < Session-Id >
>                        < Device-Id >
>                        [ EAP-Payload ]                    
>                        { Result-Code }
>                        [ Session-Lifetime ]
>                        [ Protection-Capability ]
>                        [ Key-Id ]
>                        [ Nonce]
>                     *  [ EP-Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> [5] Change 9.3.4:
> 
> Change:
> 
> 9.3.4 PANA-Start-Answer (PSA)
> 
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
> 
>          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
>                        [ Cookie ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
> 
> 
> To:
> 
> 9.3.4 PANA-Start-Answer (PSA)
> 
>    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response to
>    a PANA-Start-Request message.  The PANA_start message transmission
>    sequence number field is copied to the received sequence number
>    field.  The transmission sequence number is set to initial random
>    value.
> 
>          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
>                        [ Session-Id ] 
>                        [ Cookie ]
>                        [ Nonce ]
>                        [ EAP-Payload ]
>                        [ ISP-Information ]
>                     *  [ AVP ]
>                    0*1 <MAC>                    
> 
> 
> [6] Update the AVP occurrence table from:
> 
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0  |
>       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
> 
> 
> 
> 
> 
> 
> 
> 
> To:
> 
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
> 
> 
> 
> And add a line:
> 
>                           +-------------------------------+
>                           |      Message                  |
>                           |       Type                    |
>                           +------+------+-----+-----+-----+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
>       --------------------+------+------+-----+-----+-----+
>       Nonce               |  0   |  0   |  0  |  0  |  0  |
>      
> 
> 
> 
> [7] Add 9.4.18:
> 
> 9.4.18 Nonce AVP
> 
>    The Nonce AVP (Code 1041) is of type OctetString. The data contains
>    a randomly generated value in opaque format. The data length MUST be 
>    between 8 and 256 bytes inclusive.
> 
> 
> 
> [8] Add to references:
> 
> [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
> 
> 
> [9] Add to Security Considerations section:
> 
> i) Mobility optimization
> 
> The mobility optimization described in Section 4.9 involves the previous
> PAA 
> providing a AAA-Key to the current PAA of the PaC. There are security
> risks 
> stemming from potential compromise of PAAs. Compromise of the current
> PAA 
> does not yield compromise of the previous PAA, as AAA-Key cannot be
> computed 
> from a compromised AAA-Key-new. But a compromised previous PAA along
> with 
> the intercepted nonce values leads to the compromise of AAA-Key-new. 
> Operators should be aware of the potential risk of using this
> optimization. 
> An operator can reduce the risk exposure by forcing the PaC to perform
> an 
> EAP-based authentication immediately after the optimized PANA execution.
> 
> 

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



From pana-admin@ietf.org  Wed May  5 21:32:46 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24304
	for <pana-archive@lists.ietf.org>; Wed, 5 May 2004 21:32:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXi6-0006Gk-9K; Wed, 05 May 2004 21:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXfJ-0005Do-4P
	for pana@optimus.ietf.org; Wed, 05 May 2004 21:27:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24126
	for <pana@ietf.org>; Wed, 5 May 2004 21:27:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLXfG-0002UF-De
	for pana@ietf.org; Wed, 05 May 2004 21:27:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLXeM-0002CP-00
	for pana@ietf.org; Wed, 05 May 2004 21:26:11 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLXdR-0001bs-00
	for pana@ietf.org; Wed, 05 May 2004 21:25:13 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX900DODQL6CM@mailout1.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 10:24:42 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX900BW6QK6UJ@mailout1.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 10:24:07 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX900DKPQK3OO@mmp2.samsung.com> for pana@ietf.org;
 Thu, 06 May 2004 10:24:06 +0900 (KST)
Date: Wed, 05 May 2004 18:24:03 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <20040505194146.GC18466@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr, pana@ietf.org
Message-id: <004601c43308$d2aacb60$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

> Algorithm 1:
> 
>      AAA-Key-int = The first N bits of
>                    HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity |
>                              Session-ID)
> 
> Algorithm 2:
> 
>      AAA-Key-int = The first N bits of
>                    HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)
> 
>      where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
>      (Issue: How to combine the keys?)
> 
> Which is good, or any other algorithm?

I think we can do this:

      AAA-Key-int = The first N bits of
                    HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
                              Session-ID)

Alper



> 
> Note that the same fix should be applied to the current PANA_MAC_Key
> computation described in 4.1.5.
> 
> >
> >
> >    The value of N depends on the integrity protection algorithm in
> >    use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the
identifier of
> >    the current PAA. Session-ID is the identifier of the PaC's PANA
> > session
> >    with the previous PAA.
> >
> >    The current PAA and PaC compute the new AAA-Key by using the
nonce
> >    values and the AAA-Key-int. PAA_Nonce is the randomly chosen
value
> > that
> >    MUST be carried in a Nonce AVP in the PANA-Bind-Request message.
> >
> >
> >    AAA-Key-new = The first N bits of
> >                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)
> 
> Again there are three parameters.
> 
> This should be:
> 
>      AAA-Key-new = The first N bits of
>                    HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> 
> 
> Yoshihiro Ohba
> 
> 
> >
> >
> >    New PANA_MAC_Key is computed based on the algorithm described in
> > Section
> >    4.1.5, by using the new AAA-Key and the new Session-ID assigned
by
> > the
> >    current PAA. The MAC AVP contained in the PANA-Bind-Request and
> >    PANA-Bind-Answer messages MUST be generated and verified by using
the
> > new
> >    PANA_MAC_Key. Session-ID AVP MUST include a new session
identifier
> >    assigned by the current PAA. A new PANA session is created upon
> >    successful completion of this exchange.
> >
> >    Note that correct operation of this optimization relies on many
> > factors,
> >    including applicability of authorization state from one network
> >    attachment to another. [I-D.ietf-eap-keying] identifies this
> > operation as
> >    "fast handoff" and provides deployment considerations. Operators
are
> >    recommended to take those guidelines into account when using this
> >    optimization in their networks.
> >
> >
> > [4] Change section 9.3.7 from:
> >
> > 9.3.7 PANA-Bind-Request (PBR)
> >
> >    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> >
> >          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
> >                        < Session-Id >
> >                        < Device-Id >
> >                        { EAP-Payload }
> >                        { Result-Code }
> >                        [ Session-Lifetime ]
> >                        [ Protection-Capability ]
> >                        [ Key-Id ]
> >                     *  [ EP-Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> >
> > to:
> >
> > 9.3.7 PANA-Bind-Request (PBR)
> >
> >    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> >
> >          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
> >                        < Session-Id >
> >                        < Device-Id >
> >                        [ EAP-Payload ]
> >                        { Result-Code }
> >                        [ Session-Lifetime ]
> >                        [ Protection-Capability ]
> >                        [ Key-Id ]
> >                        [ Nonce]
> >                     *  [ EP-Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> >
> >
> > [5] Change 9.3.4:
> >
> > Change:
> >
> > 9.3.4 PANA-Start-Answer (PSA)
> >
> >    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response
to
> >    a PANA-Start-Request message.  The PANA_start message
transmission
> >    sequence number field is copied to the received sequence number
> >    field.  The transmission sequence number is set to initial random
> >    value.
> >
> >          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
> >                        [ Cookie ]
> >                        [ EAP-Payload ]
> >                        [ ISP-Information ]
> >                     *  [ AVP ]
> >
> >
> > To:
> >
> > 9.3.4 PANA-Start-Answer (PSA)
> >
> >    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response
to
> >    a PANA-Start-Request message.  The PANA_start message
transmission
> >    sequence number field is copied to the received sequence number
> >    field.  The transmission sequence number is set to initial random
> >    value.
> >
> >          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
> >                        [ Session-Id ]
> >                        [ Cookie ]
> >                        [ Nonce ]
> >                        [ EAP-Payload ]
> >                        [ ISP-Information ]
> >                     *  [ AVP ]
> >                    0*1 <MAC>
> >
> >
> > [6] Update the AVP occurrence table from:
> >
> >
+-----------------------------------------+
> >                           |        Message
|
> >                           |          Type
|
> >
+-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI
|
> >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0
|
> >       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1
|
> >       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0
|
> >
> >
> >
> >
> >
> >
> >
> >
> > To:
> >
> >
+-----------------------------------------+
> >                           |        Message
|
> >                           |          Type
|
> >
+-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI
|
> >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0
|
> >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1
|
> >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0
|
> >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0
|
> >
> >
> >
> > And add a line:
> >
> >                           +-------------------------------+
> >                           |      Message                  |
> >                           |       Type                    |
> >                           +------+------+-----+-----+-----+
> >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
> >       --------------------+------+------+-----+-----+-----+
> >       Nonce               |  0   |  0   |  0  |  0  |  0  |
> >
> >
> >
> >
> > [7] Add 9.4.18:
> >
> > 9.4.18 Nonce AVP
> >
> >    The Nonce AVP (Code 1041) is of type OctetString. The data
contains
> >    a randomly generated value in opaque format. The data length MUST
be
> >    between 8 and 256 bytes inclusive.
> >
> >
> >
> > [8] Add to references:
> >
> > [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
> >
> >
> > [9] Add to Security Considerations section:
> >
> > i) Mobility optimization
> >
> > The mobility optimization described in Section 4.9 involves the
previous
> > PAA
> > providing a AAA-Key to the current PAA of the PaC. There are
security
> > risks
> > stemming from potential compromise of PAAs. Compromise of the
current
> > PAA
> > does not yield compromise of the previous PAA, as AAA-Key cannot be
> > computed
> > from a compromised AAA-Key-new. But a compromised previous PAA along
> > with
> > the intercepted nonce values leads to the compromise of AAA-Key-new.
> > Operators should be aware of the potential risk of using this
> > optimization.
> > An operator can reduce the risk exposure by forcing the PaC to
perform
> > an
> > EAP-based authentication immediately after the optimized PANA
execution.
> >
> >


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


From exim@www1.ietf.org  Wed May  5 21:40:30 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24677
	for <pana-archive@odin.ietf.org>; Wed, 5 May 2004 21:40:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXmv-00082R-GD
	for pana-archive@odin.ietf.org; Wed, 05 May 2004 21:35:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i461Z1N0030899
	for pana-archive@odin.ietf.org; Wed, 5 May 2004 21:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXmE-0007g4-LB
	for pana-web-archive@optimus.ietf.org; Wed, 05 May 2004 21:34:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24353
	for <pana-web-archive@ietf.org>; Wed, 5 May 2004 21:34:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLXmB-0004fO-Tv
	for pana-web-archive@ietf.org; Wed, 05 May 2004 21:34:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLXlC-0004Ln-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 21:33:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLXkG-00042k-00
	for pana-web-archive@ietf.org; Wed, 05 May 2004 21:32:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXi6-0006Gk-9K; Wed, 05 May 2004 21:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLXfJ-0005Do-4P
	for pana@optimus.ietf.org; Wed, 05 May 2004 21:27:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24126
	for <pana@ietf.org>; Wed, 5 May 2004 21:27:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLXfG-0002UF-De
	for pana@ietf.org; Wed, 05 May 2004 21:27:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLXeM-0002CP-00
	for pana@ietf.org; Wed, 05 May 2004 21:26:11 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLXdR-0001bs-00
	for pana@ietf.org; Wed, 05 May 2004 21:25:13 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HX900DODQL6CM@mailout1.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 10:24:42 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HX900BW6QK6UJ@mailout1.samsung.com> for pana@ietf.org; Thu,
 06 May 2004 10:24:07 +0900 (KST)
Received: from Alperyegin ([105.144.29.153])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HX900DKPQK3OO@mmp2.samsung.com> for pana@ietf.org;
 Thu, 06 May 2004 10:24:06 +0900 (KST)
Date: Wed, 05 May 2004 18:24:03 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <20040505194146.GC18466@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: Dan.Forsberg@nokia.com, Julien.Bournelle@int-evry.fr, pana@ietf.org
Message-id: <004601c43308$d2aacb60$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

> Algorithm 1:
> 
>      AAA-Key-int = The first N bits of
>                    HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity |
>                              Session-ID)
> 
> Algorithm 2:
> 
>      AAA-Key-int = The first N bits of
>                    HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)
> 
>      where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
>      (Issue: How to combine the keys?)
> 
> Which is good, or any other algorithm?

I think we can do this:

      AAA-Key-int = The first N bits of
                    HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
                              Session-ID)

Alper



> 
> Note that the same fix should be applied to the current PANA_MAC_Key
> computation described in 4.1.5.
> 
> >
> >
> >    The value of N depends on the integrity protection algorithm in
> >    use, i.e., N=160 for HMAC-SHA1. DiameterIdentity is the
identifier of
> >    the current PAA. Session-ID is the identifier of the PaC's PANA
> > session
> >    with the previous PAA.
> >
> >    The current PAA and PaC compute the new AAA-Key by using the
nonce
> >    values and the AAA-Key-int. PAA_Nonce is the randomly chosen
value
> > that
> >    MUST be carried in a Nonce AVP in the PANA-Bind-Request message.
> >
> >
> >    AAA-Key-new = The first N bits of
> >                  HMAC-SHA1(AAA-Key-int, PaC_nonce, PAA_nonce)
> 
> Again there are three parameters.
> 
> This should be:
> 
>      AAA-Key-new = The first N bits of
>                    HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> 
> 
> Yoshihiro Ohba
> 
> 
> >
> >
> >    New PANA_MAC_Key is computed based on the algorithm described in
> > Section
> >    4.1.5, by using the new AAA-Key and the new Session-ID assigned
by
> > the
> >    current PAA. The MAC AVP contained in the PANA-Bind-Request and
> >    PANA-Bind-Answer messages MUST be generated and verified by using
the
> > new
> >    PANA_MAC_Key. Session-ID AVP MUST include a new session
identifier
> >    assigned by the current PAA. A new PANA session is created upon
> >    successful completion of this exchange.
> >
> >    Note that correct operation of this optimization relies on many
> > factors,
> >    including applicability of authorization state from one network
> >    attachment to another. [I-D.ietf-eap-keying] identifies this
> > operation as
> >    "fast handoff" and provides deployment considerations. Operators
are
> >    recommended to take those guidelines into account when using this
> >    optimization in their networks.
> >
> >
> > [4] Change section 9.3.7 from:
> >
> > 9.3.7 PANA-Bind-Request (PBR)
> >
> >    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> >
> >          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
> >                        < Session-Id >
> >                        < Device-Id >
> >                        { EAP-Payload }
> >                        { Result-Code }
> >                        [ Session-Lifetime ]
> >                        [ Protection-Capability ]
> >                        [ Key-Id ]
> >                     *  [ EP-Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> >
> > to:
> >
> > 9.3.7 PANA-Bind-Request (PBR)
> >
> >    PANA-Bind-Request (PBR) is sent by the PAA to the PaC.
> >
> >          PANA-Bind-Request ::= < PANA-Header: 4, REQ >
> >                        < Session-Id >
> >                        < Device-Id >
> >                        [ EAP-Payload ]
> >                        { Result-Code }
> >                        [ Session-Lifetime ]
> >                        [ Protection-Capability ]
> >                        [ Key-Id ]
> >                        [ Nonce]
> >                     *  [ EP-Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> >
> >
> > [5] Change 9.3.4:
> >
> > Change:
> >
> > 9.3.4 PANA-Start-Answer (PSA)
> >
> >    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response
to
> >    a PANA-Start-Request message.  The PANA_start message
transmission
> >    sequence number field is copied to the received sequence number
> >    field.  The transmission sequence number is set to initial random
> >    value.
> >
> >          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
> >                        [ Cookie ]
> >                        [ EAP-Payload ]
> >                        [ ISP-Information ]
> >                     *  [ AVP ]
> >
> >
> > To:
> >
> > 9.3.4 PANA-Start-Answer (PSA)
> >
> >    PANA-Start-Answer (PSA) is sent by the PaC to the PAA in response
to
> >    a PANA-Start-Request message.  The PANA_start message
transmission
> >    sequence number field is copied to the received sequence number
> >    field.  The transmission sequence number is set to initial random
> >    value.
> >
> >          PANA-Start-Answer ::= < PANA-Header: 2 [SEP] >
> >                        [ Session-Id ]
> >                        [ Cookie ]
> >                        [ Nonce ]
> >                        [ EAP-Payload ]
> >                        [ ISP-Information ]
> >                     *  [ AVP ]
> >                    0*1 <MAC>
> >
> >
> > [6] Update the AVP occurrence table from:
> >
> >
+-----------------------------------------+
> >                           |        Message
|
> >                           |          Type
|
> >
+-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI
|
> >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  |  1  |  0  |  0
|
> >       Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  | 0-1
|
> >       MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0
|
> >
> >
> >
> >
> >
> >
> >
> >
> > To:
> >
> >
+-----------------------------------------+
> >                           |        Message
|
> >                           |          Type
|
> >
+-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI
|
> >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0
|
> >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1
|
> >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0
|
> >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0
|
> >
> >
> >
> > And add a line:
> >
> >                           +-------------------------------+
> >                           |      Message                  |
> >                           |       Type                    |
> >                           +------+------+-----+-----+-----+
> >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
> >       --------------------+------+------+-----+-----+-----+
> >       Nonce               |  0   |  0   |  0  |  0  |  0  |
> >
> >
> >
> >
> > [7] Add 9.4.18:
> >
> > 9.4.18 Nonce AVP
> >
> >    The Nonce AVP (Code 1041) is of type OctetString. The data
contains
> >    a randomly generated value in opaque format. The data length MUST
be
> >    between 8 and 256 bytes inclusive.
> >
> >
> >
> > [8] Add to references:
> >
> > [I-D.irtf-aaaarch-handoff] draft-irtf-aaaarch-handoff-04.txt
> >
> >
> > [9] Add to Security Considerations section:
> >
> > i) Mobility optimization
> >
> > The mobility optimization described in Section 4.9 involves the
previous
> > PAA
> > providing a AAA-Key to the current PAA of the PaC. There are
security
> > risks
> > stemming from potential compromise of PAAs. Compromise of the
current
> > PAA
> > does not yield compromise of the previous PAA, as AAA-Key cannot be
> > computed
> > from a compromised AAA-Key-new. But a compromised previous PAA along
> > with
> > the intercepted nonce values leads to the compromise of AAA-Key-new.
> > Operators should be aware of the potential risk of using this
> > optimization.
> > An operator can reduce the risk exposure by forcing the PaC to
perform
> > an
> > EAP-based authentication immediately after the optimized PANA
execution.
> >
> >


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



From pana-admin@ietf.org  Thu May  6 04:14:49 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26408
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 04:14:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLdz9-0001Eo-HF; Thu, 06 May 2004 04:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLdqy-00057S-K9
	for pana@optimus.ietf.org; Thu, 06 May 2004 04:03:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25727
	for <pana@ietf.org>; Thu, 6 May 2004 04:03:34 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLdqw-0002Ow-1E
	for pana@ietf.org; Thu, 06 May 2004 04:03:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLdq3-00022i-00
	for pana@ietf.org; Thu, 06 May 2004 04:02:40 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLdpS-0001fv-00
	for pana@ietf.org; Thu, 06 May 2004 04:02:02 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i46822k04104
	for <pana@ietf.org>; Thu, 6 May 2004 11:02:02 +0300 (EET DST)
X-Scanned: Thu, 6 May 2004 11:01:49 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i4681nOE025909
	for <pana@ietf.org>; Thu, 6 May 2004 11:01:49 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00Tm40wc; Thu, 06 May 2004 11:01:47 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i4681kH23137
	for <pana@ietf.org>; Thu, 6 May 2004 11:01:46 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Thu, 6 May 2004 11:01:33 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 May 2004 11:01:33 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
Thread-Topic: Editorial comments on 4.2
Thread-Index: AcQzQFjO1gJ5Ud8+Rgupo24A9nguCA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 06 May 2004 08:01:33.0944 (UTC) FILETIME=[59207780:01C43340]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Editorial comments on 4.2
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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

Some editorial comments for section 4.2. About the last change I'm not =
100% sure, but at least something more explicit is needed into the text.
- Dan

Editorial:
4.2.
Change:
"that sent the that sent the"
to:
"that sent the"

Change:
"Protection-Capability and Post-PANA-Address-Configuration AVP AVPs MAY"
To:
"Protection-Capability and Post-PANA-Address-Configuration AVPs MAY"

Change:
"It is possible that both PAA and PaC initiate the discovery and initial =
handshake procedure at the same time, i.e., the PAA sends a =
PANA-Start-Request message while the PaC sends a PANA-PAA-Discover =
message. To resolve the race condition, the 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."
To:
"It is possible that both PAA and PaC initiate the discovery and initial =
handshake procedure at the same time, i.e., the PAA sends a =
PANA-Start-Request message while the PaC sends a PANA-PAA-Discover =
message. To resolve the race condition, the 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 (i.e. no Cookie AVP =
included) for the PaC. In this case PAA will retransmit =
PANA-Start-Request based on a timer, if PaC doesn't respond in time =
(message was lost for example). If PAA had sent stateless =
PANA-Start-Request message (i.e. Cookie AVP was included), then it =
SHOULD answer to the PANA-PAA-Discover message."

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


From exim@www1.ietf.org  Thu May  6 04:22:17 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26908
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 04:22:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLe7V-0004SL-PL
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 04:20:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i468Kf22017129
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 04:20:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLe3T-0002kZ-SR
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 04:16:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26473
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 04:16:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLe3R-0007RF-9k
	for pana-web-archive@ietf.org; Thu, 06 May 2004 04:16:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLe2M-000724-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 04:15:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLe1K-0006Vl-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 04:14:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLdz9-0001Eo-HF; Thu, 06 May 2004 04:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLdqy-00057S-K9
	for pana@optimus.ietf.org; Thu, 06 May 2004 04:03:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25727
	for <pana@ietf.org>; Thu, 6 May 2004 04:03:34 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLdqw-0002Ow-1E
	for pana@ietf.org; Thu, 06 May 2004 04:03:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLdq3-00022i-00
	for pana@ietf.org; Thu, 06 May 2004 04:02:40 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLdpS-0001fv-00
	for pana@ietf.org; Thu, 06 May 2004 04:02:02 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i46822k04104
	for <pana@ietf.org>; Thu, 6 May 2004 11:02:02 +0300 (EET DST)
X-Scanned: Thu, 6 May 2004 11:01:49 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i4681nOE025909
	for <pana@ietf.org>; Thu, 6 May 2004 11:01:49 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00Tm40wc; Thu, 06 May 2004 11:01:47 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i4681kH23137
	for <pana@ietf.org>; Thu, 6 May 2004 11:01:46 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Thu, 6 May 2004 11:01:33 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 May 2004 11:01:33 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
Thread-Topic: Editorial comments on 4.2
Thread-Index: AcQzQFjO1gJ5Ud8+Rgupo24A9nguCA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 06 May 2004 08:01:33.0944 (UTC) FILETIME=[59207780:01C43340]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Editorial comments on 4.2
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Some editorial comments for section 4.2. About the last change I'm not =
100% sure, but at least something more explicit is needed into the text.
- Dan

Editorial:
4.2.
Change:
"that sent the that sent the"
to:
"that sent the"

Change:
"Protection-Capability and Post-PANA-Address-Configuration AVP AVPs MAY"
To:
"Protection-Capability and Post-PANA-Address-Configuration AVPs MAY"

Change:
"It is possible that both PAA and PaC initiate the discovery and initial =
handshake procedure at the same time, i.e., the PAA sends a =
PANA-Start-Request message while the PaC sends a PANA-PAA-Discover =
message. To resolve the race condition, the 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."
To:
"It is possible that both PAA and PaC initiate the discovery and initial =
handshake procedure at the same time, i.e., the PAA sends a =
PANA-Start-Request message while the PaC sends a PANA-PAA-Discover =
message. To resolve the race condition, the 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 (i.e. no Cookie AVP =
included) for the PaC. In this case PAA will retransmit =
PANA-Start-Request based on a timer, if PaC doesn't respond in time =
(message was lost for example). If PAA had sent stateless =
PANA-Start-Request message (i.e. Cookie AVP was included), then it =
SHOULD answer to the PANA-PAA-Discover message."

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



From pana-admin@ietf.org  Thu May  6 08:20:07 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08578
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 08:20:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhjN-0001qS-Bd; Thu, 06 May 2004 08:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhhA-0000vQ-J7
	for pana@optimus.ietf.org; Thu, 06 May 2004 08:09:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08333
	for <pana@ietf.org>; Thu, 6 May 2004 08:09:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLhh9-0004nX-H8
	for pana@ietf.org; Thu, 06 May 2004 08:09:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLhfF-0004OS-00
	for pana@ietf.org; Thu, 06 May 2004 08:07:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLheJ-0003zy-00
	for pana@ietf.org; Thu, 06 May 2004 08:06:48 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46C6hgH017822;
	Thu, 6 May 2004 21:06:43 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46C6h9r010735;
	Thu, 6 May 2004 21:06:43 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id XAA10733 ; Thu, 6 May 2004 21:06:43 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA28948; Thu, 6 May 2004 21:06:42 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA19758; Thu, 6 May 2004 21:06:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46C6fEU016131;
	Thu, 6 May 2004 21:06:41 +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 <0HXA00K5JKB2JE@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 21:06:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLhdz-0006xl-00; Thu, 06 May 2004 05:06:27 -0700
Date: Thu, 06 May 2004 05:06:26 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <004601c43308$d2aacb60$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        Julien.Bournelle@int-evry.fr, pana@ietf.org
Message-id: <20040506120626.GE23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 Julien.Bournelle@int-evry.fr, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <20040505194146.GC18466@steelhead>
 <004601c43308$d2aacb60$991d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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, May 05, 2004 at 06:24:03PM -0700, Alper Yegin wrote:
> > Algorithm 1:
> > 
> >      AAA-Key-int = The first N bits of
> >                    HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity |
> >                              Session-ID)
> > 
> > Algorithm 2:
> > 
> >      AAA-Key-int = The first N bits of
> >                    HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)
> > 
> >      where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
> >      (Issue: How to combine the keys?)
> > 
> > Which is good, or any other algorithm?
> 
> I think we can do this:
> 
>       AAA-Key-int = The first N bits of
>                     HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
>                               Session-ID)

This should be OK.  I will reflect your take 5 with this key
computation algorithm to the manuscript under editing (and fix
PANA_MAC_Key computation algorithm in the same way).

Yoshihiro ohba


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


From exim@www1.ietf.org  Thu May  6 08:25:41 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08782
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 08:25:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhu6-00052Q-UJ
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 08:23:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46CN669019364
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 08:23:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhsj-0004g8-Ml
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 08:21:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08640
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 08:21:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLhsi-0001eK-Im
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:21:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLhrh-0001G8-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:20:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLhqk-0000se-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:19:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhjN-0001qS-Bd; Thu, 06 May 2004 08:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLhhA-0000vQ-J7
	for pana@optimus.ietf.org; Thu, 06 May 2004 08:09:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08333
	for <pana@ietf.org>; Thu, 6 May 2004 08:09:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLhh9-0004nX-H8
	for pana@ietf.org; Thu, 06 May 2004 08:09:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLhfF-0004OS-00
	for pana@ietf.org; Thu, 06 May 2004 08:07:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLheJ-0003zy-00
	for pana@ietf.org; Thu, 06 May 2004 08:06:48 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46C6hgH017822;
	Thu, 6 May 2004 21:06:43 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46C6h9r010735;
	Thu, 6 May 2004 21:06:43 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id XAA10733 ; Thu, 6 May 2004 21:06:43 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA28948; Thu, 6 May 2004 21:06:42 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA19758; Thu, 6 May 2004 21:06:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46C6fEU016131;
	Thu, 6 May 2004 21:06:41 +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 <0HXA00K5JKB2JE@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 21:06:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLhdz-0006xl-00; Thu, 06 May 2004 05:06:27 -0700
Date: Thu, 06 May 2004 05:06:26 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 58 and issue 74: proposed text (take 5)
In-reply-to: <004601c43308$d2aacb60$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        Julien.Bournelle@int-evry.fr, pana@ietf.org
Message-id: <20040506120626.GE23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 Julien.Bournelle@int-evry.fr, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <20040505194146.GC18466@steelhead>
 <004601c43308$d2aacb60$991d9069@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, May 05, 2004 at 06:24:03PM -0700, Alper Yegin wrote:
> > Algorithm 1:
> > 
> >      AAA-Key-int = The first N bits of
> >                    HMAC-SHA1(AAA-Key1, AAA-Key2 | DiameterIdentity |
> >                              Session-ID)
> > 
> > Algorithm 2:
> > 
> >      AAA-Key-int = The first N bits of
> >                    HMAC-SHA1(AAA-Key', DiameterIdentity | Session-ID)
> > 
> >      where AAA-Key' is a combined key of AAA-Key1 and AAA-Key2.
> >      (Issue: How to combine the keys?)
> > 
> > Which is good, or any other algorithm?
> 
> I think we can do this:
> 
>       AAA-Key-int = The first N bits of
>                     HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
>                               Session-ID)

This should be OK.  I will reflect your take 5 with this key
computation algorithm to the manuscript under editing (and fix
PANA_MAC_Key computation algorithm in the same way).

Yoshihiro ohba


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



From pana-admin@ietf.org  Thu May  6 08:52:42 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10129
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 08:52:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiID-0006cw-SW; Thu, 06 May 2004 08:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiD4-0004Jb-4Q
	for pana@optimus.ietf.org; Thu, 06 May 2004 08:42:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09565
	for <pana@ietf.org>; Thu, 6 May 2004 08:42:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLiD2-0002Oe-QV
	for pana@ietf.org; Thu, 06 May 2004 08:42:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLiC9-00020h-00
	for pana@ietf.org; Thu, 06 May 2004 08:41:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLiBK-0001co-00
	for pana@ietf.org; Thu, 06 May 2004 08:40:54 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46CergH003571;
	Thu, 6 May 2004 21:40:53 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46Cerje005459;
	Thu, 6 May 2004 21:40:53 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id XAA05458 ; Thu, 6 May 2004 21:40:53 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA16388; Thu, 6 May 2004 21:40:52 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA22741; Thu, 6 May 2004 21:40:51 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46CepEU004459;
	Thu, 6 May 2004 21:40:51 +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 <0HXA00M60LW05S@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 21:40:50 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLiA2-00075L-00; Thu, 06 May 2004 05:39:34 -0700
Date: Thu, 06 May 2004 05:39:34 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Editorial comments on 4.2
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20040506123933.GF23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Dan,

On Thu, May 06, 2004 at 11:01:33AM +0300, Dan.Forsberg@nokia.com wrote:
> Some editorial comments for section 4.2. About the last change I'm not 100% sure, but at least something more explicit is needed into the text.
> - Dan
> 
> Editorial:
> 4.2.
> Change:
> "that sent the that sent the"
> to:
> "that sent the"

OK.

> 
> Change:
> "Protection-Capability and Post-PANA-Address-Configuration AVP AVPs MAY"
> To:
> "Protection-Capability and Post-PANA-Address-Configuration AVPs MAY"

OK.

> 
> Change:
> "It is possible that both PAA and PaC initiate the discovery and initial handshake procedure at the same time, i.e., the PAA sends a PANA-Start-Request message while the PaC sends a PANA-PAA-Discover message. To resolve the race condition, the 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."
> To:
> "It is possible that both PAA and PaC initiate the discovery and initial handshake procedure at the same time, i.e., the PAA sends a PANA-Start-Request message while the PaC sends a PANA-PAA-Discover message. To resolve the race condition, the 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 (i.e. no Cookie AVP included) for the PaC. In this case PAA will retransmit PANA-Start-Request based on a timer, if PaC doesn't respond in time (message was lost for example). If PAA had sent stateless PANA-Start-Request message (i.e. Cookie AVP was included), then it SHOULD answer to the PANA-PAA-Discover message."

Yes, your text is better.

I reflected all of them to the manuscript.  I will produce -04c snapshot
shortly.

Thank you.

Yoshihiro Ohba


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


From exim@www1.ietf.org  Thu May  6 09:02:00 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10566
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 09:02:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiS1-0001cZ-Jo
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 08:58:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46Cw9fX006226
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 08:58:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiNs-0007yw-B1
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 08:53:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10201
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 08:53:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLiNr-0006zx-3q
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:53:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLiMu-0006aV-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:52:52 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLiMH-0006Be-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 08:52:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiID-0006cw-SW; Thu, 06 May 2004 08:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLiD4-0004Jb-4Q
	for pana@optimus.ietf.org; Thu, 06 May 2004 08:42:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09565
	for <pana@ietf.org>; Thu, 6 May 2004 08:42:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLiD2-0002Oe-QV
	for pana@ietf.org; Thu, 06 May 2004 08:42:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLiC9-00020h-00
	for pana@ietf.org; Thu, 06 May 2004 08:41:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLiBK-0001co-00
	for pana@ietf.org; Thu, 06 May 2004 08:40:54 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46CergH003571;
	Thu, 6 May 2004 21:40:53 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46Cerje005459;
	Thu, 6 May 2004 21:40:53 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id XAA05458 ; Thu, 6 May 2004 21:40:53 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA16388; Thu, 6 May 2004 21:40:52 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA22741; Thu, 6 May 2004 21:40:51 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46CepEU004459;
	Thu, 6 May 2004 21:40:51 +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 <0HXA00M60LW05S@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 21:40:50 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLiA2-00075L-00; Thu, 06 May 2004 05:39:34 -0700
Date: Thu, 06 May 2004 05:39:34 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Editorial comments on 4.2
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20040506123933.GF23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <FC5FF66A769AB044AED651C705EAA8EA02236169@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Hi Dan,

On Thu, May 06, 2004 at 11:01:33AM +0300, Dan.Forsberg@nokia.com wrote:
> Some editorial comments for section 4.2. About the last change I'm not 100% sure, but at least something more explicit is needed into the text.
> - Dan
> 
> Editorial:
> 4.2.
> Change:
> "that sent the that sent the"
> to:
> "that sent the"

OK.

> 
> Change:
> "Protection-Capability and Post-PANA-Address-Configuration AVP AVPs MAY"
> To:
> "Protection-Capability and Post-PANA-Address-Configuration AVPs MAY"

OK.

> 
> Change:
> "It is possible that both PAA and PaC initiate the discovery and initial handshake procedure at the same time, i.e., the PAA sends a PANA-Start-Request message while the PaC sends a PANA-PAA-Discover message. To resolve the race condition, the 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."
> To:
> "It is possible that both PAA and PaC initiate the discovery and initial handshake procedure at the same time, i.e., the PAA sends a PANA-Start-Request message while the PaC sends a PANA-PAA-Discover message. To resolve the race condition, the 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 (i.e. no Cookie AVP included) for the PaC. In this case PAA will retransmit PANA-Start-Request based on a timer, if PaC doesn't respond in time (message was lost for example). If PAA had sent stateless PANA-Start-Request message (i.e. Cookie AVP was included), then it SHOULD answer to the PANA-PAA-Discover message."

Yes, your text is better.

I reflected all of them to the manuscript.  I will produce -04c snapshot
shortly.

Thank you.

Yoshihiro Ohba


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



From pana-admin@ietf.org  Thu May  6 09:48:31 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13034
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 09:48:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjAO-0000m9-SC; Thu, 06 May 2004 09:44:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLj1m-0005pc-MH
	for pana@optimus.ietf.org; Thu, 06 May 2004 09:35:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12250
	for <pana@ietf.org>; Thu, 6 May 2004 09:35:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLj1k-00006p-Rb
	for pana@ietf.org; Thu, 06 May 2004 09:35:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLj0o-0007Un-00
	for pana@ietf.org; Thu, 06 May 2004 09:34:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLj0A-00074b-00
	for pana@ietf.org; Thu, 06 May 2004 09:33:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46DXOgH029888;
	Thu, 6 May 2004 22:33:24 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46DXO60017053;
	Thu, 6 May 2004 22:33:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA17052 ; Thu, 6 May 2004 22:33:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16958; Thu, 6 May 2004 22:33:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA17411; Thu, 6 May 2004 22:33:23 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46DXMEU029169;
	Thu, 6 May 2004 22:33:22 +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 <0HXA000NVOBKZ3@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 22:33:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLj01-0007OP-00; Thu, 06 May 2004 06:33:17 -0700
Date: Thu, 06 May 2004 06:33:17 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040506133317.GG23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] PANA specification snapshot (04c)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

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

Changes (from -04b snapshot):

- Resolutions for issues 28, 58, 74, 78 and 79.

- Dan's editorial comments.

- Added IANA Considerations section (detailed contents: TBD)

- Other minor editorial fixes.

Yoshihiro Ohba

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


From exim@www1.ietf.org  Thu May  6 10:06:45 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14544
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 10:06:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjQI-0007Os-DB
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 10:00:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46E0Qno028446
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 10:00:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjGY-0003Rf-Vy
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 09:50:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13290
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 09:50:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLjGX-0006lb-53
	for pana-web-archive@ietf.org; Thu, 06 May 2004 09:50:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLjFT-0006Gj-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 09:49:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLjEI-0005kf-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 09:48:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjAO-0000m9-SC; Thu, 06 May 2004 09:44:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLj1m-0005pc-MH
	for pana@optimus.ietf.org; Thu, 06 May 2004 09:35:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12250
	for <pana@ietf.org>; Thu, 6 May 2004 09:35:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLj1k-00006p-Rb
	for pana@ietf.org; Thu, 06 May 2004 09:35:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLj0o-0007Un-00
	for pana@ietf.org; Thu, 06 May 2004 09:34:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLj0A-00074b-00
	for pana@ietf.org; Thu, 06 May 2004 09:33:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46DXOgH029888;
	Thu, 6 May 2004 22:33:24 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46DXO60017053;
	Thu, 6 May 2004 22:33:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA17052 ; Thu, 6 May 2004 22:33:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16958; Thu, 6 May 2004 22:33:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA17411; Thu, 6 May 2004 22:33:23 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46DXMEU029169;
	Thu, 6 May 2004 22:33:22 +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 <0HXA000NVOBKZ3@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 22:33:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLj01-0007OP-00; Thu, 06 May 2004 06:33:17 -0700
Date: Thu, 06 May 2004 06:33:17 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040506133317.GG23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
Subject: [Pana] PANA specification snapshot (04c)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60

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

Changes (from -04b snapshot):

- Resolutions for issues 28, 58, 74, 78 and 79.

- Dan's editorial comments.

- Added IANA Considerations section (detailed contents: TBD)

- Other minor editorial fixes.

Yoshihiro Ohba

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



From pana-admin@ietf.org  Thu May  6 10:17:07 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15869
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 10:17:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjYa-0005ou-JV; Thu, 06 May 2004 10:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjRn-0000ha-LD
	for pana@optimus.ietf.org; Thu, 06 May 2004 10:01:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14005
	for <pana@ietf.org>; Thu, 6 May 2004 10:01:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLjRl-0004A9-Gv
	for pana@ietf.org; Thu, 06 May 2004 10:01:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLjQp-0003j5-00
	for pana@ietf.org; Thu, 06 May 2004 10:01:00 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLjPn-0003GE-00
	for pana@ietf.org; Thu, 06 May 2004 09:59:56 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46DxsgH011040;
	Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46DxsJc000187;
	Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA00184 ; Thu, 6 May 2004 22:59:54 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA26597; Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA23179; Thu, 6 May 2004 22:59:53 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46DxrEU010274;
	Thu, 6 May 2004 22:59:53 +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 <0HXA002C2PJPWZ@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 22:59:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLjPN-0007U5-00; Thu, 06 May 2004 06:59:29 -0700
Date: Thu, 06 May 2004 06:59:29 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040506135929.GH23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] host route
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 came up with an issue after submitting
draft-ietf-pana-framework-00.txt.

In section 5 of draft-ietf-pana-framework-00.txt:

      "PRPA and the IP address of PAA are assumed to be on the same IP
      subnet, hence the PaC and PAA can perform on-link communication as
      required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
      this assumption may not hold true. In order to maintain the same
      on-link communication, the PaC and PAA SHOULD create host routes
      to each other upon PaC's IP address change.  The PaC SHOULD create
      a host route to the PAA, and the PAA SHOULD create a host route to
      the PaC (POPA)."

In order to create a host route to the PaC, the PAA needs to know the
POPA.  However, when MAC address is used as the device-id, no
device-id update occurs in PANA, and I am wondering how the PAA can
know the POPA.  There would be several ways to deal with this:

- PAA listens to DHCP or data traffic on the link to know the POPA.

- PAA communicates with DHCP server (by using some other protocol such
as SNMP) to know the POPA.

- After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
  new AVP that carries the POPA.

Which is better or any other ways?

Yoshihiro Ohba

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


From exim@www1.ietf.org  Thu May  6 10:33:12 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16989
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 10:33:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjqx-00089n-2k
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 10:27:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46ERxQx031353
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 10:27:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLji7-0003MF-Bz
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 10:18:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16153
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 10:18:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLji5-0003gn-38
	for pana-web-archive@ietf.org; Thu, 06 May 2004 10:18:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLjh4-0003EQ-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 10:17:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLjfy-0002cX-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 10:16:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjYa-0005ou-JV; Thu, 06 May 2004 10:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLjRn-0000ha-LD
	for pana@optimus.ietf.org; Thu, 06 May 2004 10:01:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14005
	for <pana@ietf.org>; Thu, 6 May 2004 10:01:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLjRl-0004A9-Gv
	for pana@ietf.org; Thu, 06 May 2004 10:01:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLjQp-0003j5-00
	for pana@ietf.org; Thu, 06 May 2004 10:01:00 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLjPn-0003GE-00
	for pana@ietf.org; Thu, 06 May 2004 09:59:56 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46DxsgH011040;
	Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46DxsJc000187;
	Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA00184 ; Thu, 6 May 2004 22:59:54 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA26597; Thu, 6 May 2004 22:59:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA23179; Thu, 6 May 2004 22:59:53 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46DxrEU010274;
	Thu, 6 May 2004 22:59:53 +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 <0HXA002C2PJPWZ@tsbpo1.po.toshiba.co.jp>; Thu,
 6 May 2004 22:59:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLjPN-0007U5-00; Thu, 06 May 2004 06:59:29 -0700
Date: Thu, 06 May 2004 06:59:29 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040506135929.GH23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
Subject: [Pana] host route
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60

I came up with an issue after submitting
draft-ietf-pana-framework-00.txt.

In section 5 of draft-ietf-pana-framework-00.txt:

      "PRPA and the IP address of PAA are assumed to be on the same IP
      subnet, hence the PaC and PAA can perform on-link communication as
      required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
      this assumption may not hold true. In order to maintain the same
      on-link communication, the PaC and PAA SHOULD create host routes
      to each other upon PaC's IP address change.  The PaC SHOULD create
      a host route to the PAA, and the PAA SHOULD create a host route to
      the PaC (POPA)."

In order to create a host route to the PaC, the PAA needs to know the
POPA.  However, when MAC address is used as the device-id, no
device-id update occurs in PANA, and I am wondering how the PAA can
know the POPA.  There would be several ways to deal with this:

- PAA listens to DHCP or data traffic on the link to know the POPA.

- PAA communicates with DHCP server (by using some other protocol such
as SNMP) to know the POPA.

- After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
  new AVP that carries the POPA.

Which is better or any other ways?

Yoshihiro Ohba

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



From pana-admin@ietf.org  Thu May  6 13:03:03 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01108
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 13:03:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLlN9-00072x-C0; Thu, 06 May 2004 12:05:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLktQ-0006mk-PT
	for pana@optimus.ietf.org; Thu, 06 May 2004 11:34:36 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20493;
	Thu, 6 May 2004 11:34:34 -0400 (EDT)
Message-Id: <200405061534.LAA20493@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 06 May 2004 11:34:33 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-framework-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: PANA Framework
	Author(s)	: P. Jayaraman, et al.
	Filename	: draft-ietf-pana-framework-00.txt
	Pages		: 47
	Date		: 2004-5-4
	
PANA design provides support for various types of deployments. Access
   networks can differ based on the availability of lower-layer
   security, placement of PANA entities, choice of client IP
   configuration and authentication methods, etc.  This I-D defines a
   general framework for describing how these various deployment choices
   are handled by PANA and the access network architectures.
   Additionally, two possible deployments are described in detail: using
   PANA over DSL networks and WLAN networks.

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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


From pana-admin@ietf.org  Thu May  6 13:42:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06456
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 13:42:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmcI-0006PJ-QU; Thu, 06 May 2004 13:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmNi-0002nB-9w
	for pana@optimus.ietf.org; Thu, 06 May 2004 13:10:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01746
	for <pana@ietf.org>; Thu, 6 May 2004 13:09:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmNg-00076f-Aq
	for pana@ietf.org; Thu, 06 May 2004 13:09:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmL9-0006Bu-00
	for pana@ietf.org; Thu, 06 May 2004 13:07:20 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLmK7-0005fr-00
	for pana@ietf.org; Thu, 06 May 2004 13:06:15 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.58.94 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 6 May 2004 17:06:13 -0000
Message-ID: <005a01c4338c$7016ffd0$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040506135929.GH23909@steelhead>
Subject: Re: [Pana] host route
Date: Thu, 6 May 2004 10:05:11 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 came up with an issue after submitting
> draft-ietf-pana-framework-00.txt.
> 
> In section 5 of draft-ietf-pana-framework-00.txt:
> 
>       "PRPA and the IP address of PAA are assumed to be on the same IP
>       subnet, hence the PaC and PAA can perform on-link communication as
>       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
>       this assumption may not hold true. In order to maintain the same
>       on-link communication, the PaC and PAA SHOULD create host routes
>       to each other upon PaC's IP address change.  The PaC SHOULD create
>       a host route to the PAA, and the PAA SHOULD create a host route to
>       the PaC (POPA)."
> 
> In order to create a host route to the PaC, the PAA needs to know the
> POPA.  However, when MAC address is used as the device-id, no
> device-id update occurs in PANA, and I am wondering how the PAA can
> know the POPA.  There would be several ways to deal with this:  
> 
> - PAA listens to DHCP or data traffic on the link to know the POPA.
> 
> - PAA communicates with DHCP server (by using some other protocol such
> as SNMP) to know the POPA.
> 
> - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
>   new AVP that carries the POPA.
> 
This sounds like a better option so that we can keep the device-Id update and POPA
update separate. I never understood the reason for using Reauth request for updates.
Why isn't this a generic update mechanism protected by PANA SA ?


> Which is better or any other ways?
> 
 > Yoshihiro Ohba
> 

-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 May  6 13:48:21 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06772
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 13:48:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmeO-0007xX-TD
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 13:27:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46HRCTw030584
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 13:27:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmOc-0003UE-FQ
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 13:10:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01931
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 13:10:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmOa-0007VO-NC
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:10:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmLu-0006S3-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:08:06 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLmKO-0005hL-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:06:32 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BLmGb-00025s-Oq
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:02:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLlN9-00072x-C0; Thu, 06 May 2004 12:05:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLktQ-0006mk-PT
	for pana@optimus.ietf.org; Thu, 06 May 2004 11:34:36 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20493;
	Thu, 6 May 2004 11:34:34 -0400 (EDT)
Message-Id: <200405061534.LAA20493@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 06 May 2004 11:34:33 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-framework-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

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

	Title		: PANA Framework
	Author(s)	: P. Jayaraman, et al.
	Filename	: draft-ietf-pana-framework-00.txt
	Pages		: 47
	Date		: 2004-5-4
	
PANA design provides support for various types of deployments. Access
   networks can differ based on the availability of lower-layer
   security, placement of PANA entities, choice of client IP
   configuration and authentication methods, etc.  This I-D defines a
   general framework for describing how these various deployment choices
   are handled by PANA and the access network architectures.
   Additionally, two possible deployments are described in detail: using
   PANA over DSL networks and WLAN networks.

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Thu May  6 14:05:49 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08206
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 14:05:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLn41-0004e1-51
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 13:53:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46HrfbL017854
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 13:53:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmuu-0008Io-MT
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 13:44:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06493
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 13:44:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmus-0006UV-Ga
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:44:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmtW-000624-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:42:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLmsS-0005Q0-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 13:41:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmcI-0006PJ-QU; Thu, 06 May 2004 13:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmNi-0002nB-9w
	for pana@optimus.ietf.org; Thu, 06 May 2004 13:10:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01746
	for <pana@ietf.org>; Thu, 6 May 2004 13:09:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmNg-00076f-Aq
	for pana@ietf.org; Thu, 06 May 2004 13:09:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmL9-0006Bu-00
	for pana@ietf.org; Thu, 06 May 2004 13:07:20 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLmK7-0005fr-00
	for pana@ietf.org; Thu, 06 May 2004 13:06:15 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.58.94 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 6 May 2004 17:06:13 -0000
Message-ID: <005a01c4338c$7016ffd0$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040506135929.GH23909@steelhead>
Subject: Re: [Pana] host route
Date: Thu, 6 May 2004 10:05:11 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 came up with an issue after submitting
> draft-ietf-pana-framework-00.txt.
> 
> In section 5 of draft-ietf-pana-framework-00.txt:
> 
>       "PRPA and the IP address of PAA are assumed to be on the same IP
>       subnet, hence the PaC and PAA can perform on-link communication as
>       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
>       this assumption may not hold true. In order to maintain the same
>       on-link communication, the PaC and PAA SHOULD create host routes
>       to each other upon PaC's IP address change.  The PaC SHOULD create
>       a host route to the PAA, and the PAA SHOULD create a host route to
>       the PaC (POPA)."
> 
> In order to create a host route to the PaC, the PAA needs to know the
> POPA.  However, when MAC address is used as the device-id, no
> device-id update occurs in PANA, and I am wondering how the PAA can
> know the POPA.  There would be several ways to deal with this:  
> 
> - PAA listens to DHCP or data traffic on the link to know the POPA.
> 
> - PAA communicates with DHCP server (by using some other protocol such
> as SNMP) to know the POPA.
> 
> - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
>   new AVP that carries the POPA.
> 
This sounds like a better option so that we can keep the device-Id update and POPA
update separate. I never understood the reason for using Reauth request for updates.
Why isn't this a generic update mechanism protected by PANA SA ?


> Which is better or any other ways?
> 
 > Yoshihiro Ohba
> 

-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 May  6 14:07:38 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08347
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 14:07:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLn4U-0004zf-66; Thu, 06 May 2004 13:54:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmvV-0008VQ-Qn
	for pana@optimus.ietf.org; Thu, 06 May 2004 13:44:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06513
	for <pana@ietf.org>; Thu, 6 May 2004 13:44:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmvT-0006sq-IR
	for pana@ietf.org; Thu, 06 May 2004 13:44:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmuU-0006QW-00
	for pana@ietf.org; Thu, 06 May 2004 13:43:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLmtP-0005kk-00
	for pana@ietf.org; Thu, 06 May 2004 13:42:43 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46HgfgH027415;
	Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46HgfFR017906;
	Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA17905 ; Fri, 7 May 2004 02:42:41 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA25359; Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA17809; Fri, 7 May 2004 02:42:40 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46HgeEU006993;
	Fri, 7 May 2004 02:42:40 +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 <0HXA00D8SZV1VV@tsbpo1.po.toshiba.co.jp>; Fri,
 7 May 2004 02:42:39 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLmsK-0000HY-00; Thu, 06 May 2004 10:41:36 -0700
Date: Thu, 06 May 2004 10:41:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <005a01c4338c$7016ffd0$6401a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040506174136.GN23909@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@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.1 required=5.0 tests=AWL 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 Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
>  
> 
> > I came up with an issue after submitting
> > draft-ietf-pana-framework-00.txt.
> > 
> > In section 5 of draft-ietf-pana-framework-00.txt:
> > 
> >       "PRPA and the IP address of PAA are assumed to be on the same IP
> >       subnet, hence the PaC and PAA can perform on-link communication as
> >       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
> >       this assumption may not hold true. In order to maintain the same
> >       on-link communication, the PaC and PAA SHOULD create host routes
> >       to each other upon PaC's IP address change.  The PaC SHOULD create
> >       a host route to the PAA, and the PAA SHOULD create a host route to
> >       the PaC (POPA)."
> > 
> > In order to create a host route to the PaC, the PAA needs to know the
> > POPA.  However, when MAC address is used as the device-id, no
> > device-id update occurs in PANA, and I am wondering how the PAA can
> > know the POPA.  There would be several ways to deal with this:  
> > 
> > - PAA listens to DHCP or data traffic on the link to know the POPA.
> > 
> > - PAA communicates with DHCP server (by using some other protocol such
> > as SNMP) to know the POPA.
> > 
> > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
> >   new AVP that carries the POPA.
> > 
> This sounds like a better option so that we can keep the device-Id update and POPA
> update separate. I never understood the reason for using Reauth request for updates.
> Why isn't this a generic update mechanism protected by PANA SA ?


As far as I remember, one usage of PANA-Reauth exchange has been to
allow PaC to its its Device-Id in a secure way.  It seems that sending
the POPA is not much different from updating Device-Id, and that is
why I mentioned PANA-Reauth exchange.  But we could define a separate
mechanism/message for updating an address if we want.  In my
experiance, having a separate mechanism/message might be good for
reducing the chance of mis-implementation coming from using the same
message for many purposes.


Yoshihiro Ohba



> 
> 
> > Which is better or any other ways?
> > 
>  > Yoshihiro Ohba
> > 
> 
> -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 May  6 14:27:50 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09306
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 14:27:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnRY-0007HV-Vj; Thu, 06 May 2004 14:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnFx-0002NR-Ll
	for pana@optimus.ietf.org; Thu, 06 May 2004 14:06:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08247
	for <pana@ietf.org>; Thu, 6 May 2004 14:05:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnFv-0000hB-5L
	for pana@ietf.org; Thu, 06 May 2004 14:05:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnEw-0000Gh-00
	for pana@ietf.org; Thu, 06 May 2004 14:04:58 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnE0-0007Ek-00
	for pana@ietf.org; Thu, 06 May 2004 14:04:00 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 59441AFC2; Thu,  6 May 2004 20:03:29 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 403DF576A; Thu,  6 May 2004 20:03:29 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 8F82214426; Thu,  6 May 2004 20:02:52 +0200 (MET DST)
Message-ID: <409A7D46.8070403@dif.um.es>
Date: Thu, 06 May 2004 20:00:38 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Subject: Re: [Pana] host route
References: <20040506135929.GH23909@steelhead>
In-Reply-To: <20040506135929.GH23909@steelhead>
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=AWL 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 Yoshihiro

Yoshihiro Ohba wrote:

>I came up with an issue after submitting
>draft-ietf-pana-framework-00.txt.
>
>In section 5 of draft-ietf-pana-framework-00.txt:
>
>      "PRPA and the IP address of PAA are assumed to be on the same IP
>      subnet, hence the PaC and PAA can perform on-link communication as
>      required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
>      this assumption may not hold true. In order to maintain the same
>      on-link communication, the PaC and PAA SHOULD create host routes
>      to each other upon PaC's IP address change.  The PaC SHOULD create
>      a host route to the PAA, and the PAA SHOULD create a host route to
>      the PaC (POPA)."
>
>In order to create a host route to the PaC, the PAA needs to know the
>POPA.  However, when MAC address is used as the device-id, no
>device-id update occurs in PANA, and I am wondering how the PAA can
>know the POPA.  There would be several ways to deal with this:
>
>- PAA listens to DHCP or data traffic on the link to know the POPA.
>
>- PAA communicates with DHCP server (by using some other protocol such
>as SNMP) to know the POPA.
>
>- After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
>  new AVP that carries the POPA.
>  
>
I think third option could be more suitable because PaC and PAA talks
PANA , so they should use it to communicate these issues. However, this
new AVP would be really used only to solve this particular case.

>Which is better or any other ways?
>
>Yoshihiro Ohba
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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


From exim@www1.ietf.org  Thu May  6 14:31:06 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09491
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 14:31:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnXg-0001YG-IJ
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 14:24:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46IOKpN005959
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 14:24:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnIv-0003zc-9v
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 14:09:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08439
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 14:09:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnIs-0001zb-TT
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:09:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnHr-0001ZE-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:08:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnH3-00019h-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:07:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLn4U-0004zf-66; Thu, 06 May 2004 13:54:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmvV-0008VQ-Qn
	for pana@optimus.ietf.org; Thu, 06 May 2004 13:44:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06513
	for <pana@ietf.org>; Thu, 6 May 2004 13:44:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLmvT-0006sq-IR
	for pana@ietf.org; Thu, 06 May 2004 13:44:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLmuU-0006QW-00
	for pana@ietf.org; Thu, 06 May 2004 13:43:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLmtP-0005kk-00
	for pana@ietf.org; Thu, 06 May 2004 13:42:43 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i46HgfgH027415;
	Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i46HgfFR017906;
	Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA17905 ; Fri, 7 May 2004 02:42:41 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA25359; Fri, 7 May 2004 02:42:41 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA17809; Fri, 7 May 2004 02:42:40 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i46HgeEU006993;
	Fri, 7 May 2004 02:42:40 +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 <0HXA00D8SZV1VV@tsbpo1.po.toshiba.co.jp>; Fri,
 7 May 2004 02:42:39 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLmsK-0000HY-00; Thu, 06 May 2004 10:41:36 -0700
Date: Thu, 06 May 2004 10:41:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <005a01c4338c$7016ffd0$6401a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040506174136.GN23909@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
>  
> 
> > I came up with an issue after submitting
> > draft-ietf-pana-framework-00.txt.
> > 
> > In section 5 of draft-ietf-pana-framework-00.txt:
> > 
> >       "PRPA and the IP address of PAA are assumed to be on the same IP
> >       subnet, hence the PaC and PAA can perform on-link communication as
> >       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
> >       this assumption may not hold true. In order to maintain the same
> >       on-link communication, the PaC and PAA SHOULD create host routes
> >       to each other upon PaC's IP address change.  The PaC SHOULD create
> >       a host route to the PAA, and the PAA SHOULD create a host route to
> >       the PaC (POPA)."
> > 
> > In order to create a host route to the PaC, the PAA needs to know the
> > POPA.  However, when MAC address is used as the device-id, no
> > device-id update occurs in PANA, and I am wondering how the PAA can
> > know the POPA.  There would be several ways to deal with this:  
> > 
> > - PAA listens to DHCP or data traffic on the link to know the POPA.
> > 
> > - PAA communicates with DHCP server (by using some other protocol such
> > as SNMP) to know the POPA.
> > 
> > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
> >   new AVP that carries the POPA.
> > 
> This sounds like a better option so that we can keep the device-Id update and POPA
> update separate. I never understood the reason for using Reauth request for updates.
> Why isn't this a generic update mechanism protected by PANA SA ?


As far as I remember, one usage of PANA-Reauth exchange has been to
allow PaC to its its Device-Id in a secure way.  It seems that sending
the POPA is not much different from updating Device-Id, and that is
why I mentioned PANA-Reauth exchange.  But we could define a separate
mechanism/message for updating an address if we want.  In my
experiance, having a separate mechanism/message might be good for
reducing the chance of mis-implementation coming from using the same
message for many purposes.


Yoshihiro Ohba



> 
> 
> > Which is better or any other ways?
> > 
>  > Yoshihiro Ohba
> > 
> 
> -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 May  6 14:35:40 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09883
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 14:35:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnZL-0002IE-8K; Thu, 06 May 2004 14:26:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnOb-0005ve-G1
	for pana@optimus.ietf.org; Thu, 06 May 2004 14:14:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08643
	for <pana@ietf.org>; Thu, 6 May 2004 14:14:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnOZ-0004TZ-1u
	for pana@ietf.org; Thu, 06 May 2004 14:14:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnNc-000451-00
	for pana@ietf.org; Thu, 06 May 2004 14:13:57 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLnMh-0003gq-00
	for pana@ietf.org; Thu, 06 May 2004 14:13:00 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.58.94 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 6 May 2004 18:12:59 -0000
Message-ID: <001101c43395$c41d8870$6801a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
Subject: Re: [Pana] host route
Date: Thu, 6 May 2004 11:12:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> >  
> > 
> > > I came up with an issue after submitting
> > > draft-ietf-pana-framework-00.txt.
> > > 
> > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > 
> > >       "PRPA and the IP address of PAA are assumed to be on the same IP
> > >       subnet, hence the PaC and PAA can perform on-link communication as
> > >       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
> > >       this assumption may not hold true. In order to maintain the same
> > >       on-link communication, the PaC and PAA SHOULD create host routes
> > >       to each other upon PaC's IP address change.  The PaC SHOULD create
> > >       a host route to the PAA, and the PAA SHOULD create a host route to
> > >       the PaC (POPA)."
> > > 
> > > In order to create a host route to the PaC, the PAA needs to know the
> > > POPA.  However, when MAC address is used as the device-id, no
> > > device-id update occurs in PANA, and I am wondering how the PAA can
> > > know the POPA.  There would be several ways to deal with this:  
> > > 
> > > - PAA listens to DHCP or data traffic on the link to know the POPA.
> > > 
> > > - PAA communicates with DHCP server (by using some other protocol such
> > > as SNMP) to know the POPA.
> > > 
> > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
> > >   new AVP that carries the POPA.
> > > 
> > This sounds like a better option so that we can keep the device-Id update and POPA
> > update separate. I never understood the reason for using Reauth request for updates.
> > Why isn't this a generic update mechanism protected by PANA SA ?
> 
> 
> As far as I remember, one usage of PANA-Reauth exchange has been to
> allow PaC to its its Device-Id in a secure way.  It seems that sending
> the POPA is not much different from updating Device-Id, and that is
> why I mentioned PANA-Reauth exchange.  But we could define a separate
> mechanism/message for updating an address if we want.  In my
> experiance, having a separate mechanism/message might be good for
> reducing the chance of mis-implementation coming from using the same
> message for many purposes.
> 
As we have more than one update now, it might make sense to provide a separate
mechanism instead of over-loading the reauth.

There is a difference between device-ID update and POPA update. There is not
much incentive for the PaC to update with a device-ID that belongs to someone else.
But PaC can always update the PAA with invalid POPAs consuming host routes.
There is really no redirection attack as the route is not used until the packets are
sent that would use the route. So, the only possibility is to generate invalid host
routes. How can PAA check to make sure that this is not happening ? Can the same
happen with device-ID update consuming some other resource ? The framework
document is still not clear on what happens during a device-Id update.

-mohan


-mohan


> 
> Yoshihiro Ohba
> 
> 
> 
> > 
> > 
> > > Which is better or any other ways?
> > > 
> >  > Yoshihiro Ohba
> > > 
> > 
> > -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 May  6 14:43:34 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10440
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 14:43:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnjw-0006dO-MI
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 14:37:00 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46Ib0jc025492
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 14:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLncE-0003Ki-Mp
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 14:29:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09375
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 14:28:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLncC-0002WB-2Q
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:29:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnbI-00027U-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:28:05 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnaa-0001iS-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:27:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnRY-0007HV-Vj; Thu, 06 May 2004 14:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnFx-0002NR-Ll
	for pana@optimus.ietf.org; Thu, 06 May 2004 14:06:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08247
	for <pana@ietf.org>; Thu, 6 May 2004 14:05:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnFv-0000hB-5L
	for pana@ietf.org; Thu, 06 May 2004 14:05:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnEw-0000Gh-00
	for pana@ietf.org; Thu, 06 May 2004 14:04:58 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnE0-0007Ek-00
	for pana@ietf.org; Thu, 06 May 2004 14:04:00 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 59441AFC2; Thu,  6 May 2004 20:03:29 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 403DF576A; Thu,  6 May 2004 20:03:29 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 8F82214426; Thu,  6 May 2004 20:02:52 +0200 (MET DST)
Message-ID: <409A7D46.8070403@dif.um.es>
Date: Thu, 06 May 2004 20:00:38 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Subject: Re: [Pana] host route
References: <20040506135929.GH23909@steelhead>
In-Reply-To: <20040506135929.GH23909@steelhead>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshihiro

Yoshihiro Ohba wrote:

>I came up with an issue after submitting
>draft-ietf-pana-framework-00.txt.
>
>In section 5 of draft-ietf-pana-framework-00.txt:
>
>      "PRPA and the IP address of PAA are assumed to be on the same IP
>      subnet, hence the PaC and PAA can perform on-link communication as
>      required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
>      this assumption may not hold true. In order to maintain the same
>      on-link communication, the PaC and PAA SHOULD create host routes
>      to each other upon PaC's IP address change.  The PaC SHOULD create
>      a host route to the PAA, and the PAA SHOULD create a host route to
>      the PaC (POPA)."
>
>In order to create a host route to the PaC, the PAA needs to know the
>POPA.  However, when MAC address is used as the device-id, no
>device-id update occurs in PANA, and I am wondering how the PAA can
>know the POPA.  There would be several ways to deal with this:
>
>- PAA listens to DHCP or data traffic on the link to know the POPA.
>
>- PAA communicates with DHCP server (by using some other protocol such
>as SNMP) to know the POPA.
>
>- After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
>  new AVP that carries the POPA.
>  
>
I think third option could be more suitable because PaC and PAA talks
PANA , so they should use it to communicate these issues. However, this
new AVP would be really used only to solve this particular case.

>Which is better or any other ways?
>
>Yoshihiro Ohba
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From exim@www1.ietf.org  Thu May  6 14:51:43 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10734
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 14:51:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnqL-0000ER-En
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 14:43:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46Ihb1l000887
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 14:43:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnkA-0006hV-CH
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 14:37:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10044
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 14:37:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnk7-0005ri-MR
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:37:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnjC-0005RQ-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:36:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLniA-000512-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 14:35:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnZL-0002IE-8K; Thu, 06 May 2004 14:26:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnOb-0005ve-G1
	for pana@optimus.ietf.org; Thu, 06 May 2004 14:14:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08643
	for <pana@ietf.org>; Thu, 6 May 2004 14:14:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnOZ-0004TZ-1u
	for pana@ietf.org; Thu, 06 May 2004 14:14:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnNc-000451-00
	for pana@ietf.org; Thu, 06 May 2004 14:13:57 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLnMh-0003gq-00
	for pana@ietf.org; Thu, 06 May 2004 14:13:00 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.58.94 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 6 May 2004 18:12:59 -0000
Message-ID: <001101c43395$c41d8870$6801a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
Subject: Re: [Pana] host route
Date: Thu, 6 May 2004 11:12:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> >  
> > 
> > > I came up with an issue after submitting
> > > draft-ietf-pana-framework-00.txt.
> > > 
> > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > 
> > >       "PRPA and the IP address of PAA are assumed to be on the same IP
> > >       subnet, hence the PaC and PAA can perform on-link communication as
> > >       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
> > >       this assumption may not hold true. In order to maintain the same
> > >       on-link communication, the PaC and PAA SHOULD create host routes
> > >       to each other upon PaC's IP address change.  The PaC SHOULD create
> > >       a host route to the PAA, and the PAA SHOULD create a host route to
> > >       the PaC (POPA)."
> > > 
> > > In order to create a host route to the PaC, the PAA needs to know the
> > > POPA.  However, when MAC address is used as the device-id, no
> > > device-id update occurs in PANA, and I am wondering how the PAA can
> > > know the POPA.  There would be several ways to deal with this:  
> > > 
> > > - PAA listens to DHCP or data traffic on the link to know the POPA.
> > > 
> > > - PAA communicates with DHCP server (by using some other protocol such
> > > as SNMP) to know the POPA.
> > > 
> > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with a
> > >   new AVP that carries the POPA.
> > > 
> > This sounds like a better option so that we can keep the device-Id update and POPA
> > update separate. I never understood the reason for using Reauth request for updates.
> > Why isn't this a generic update mechanism protected by PANA SA ?
> 
> 
> As far as I remember, one usage of PANA-Reauth exchange has been to
> allow PaC to its its Device-Id in a secure way.  It seems that sending
> the POPA is not much different from updating Device-Id, and that is
> why I mentioned PANA-Reauth exchange.  But we could define a separate
> mechanism/message for updating an address if we want.  In my
> experiance, having a separate mechanism/message might be good for
> reducing the chance of mis-implementation coming from using the same
> message for many purposes.
> 
As we have more than one update now, it might make sense to provide a separate
mechanism instead of over-loading the reauth.

There is a difference between device-ID update and POPA update. There is not
much incentive for the PaC to update with a device-ID that belongs to someone else.
But PaC can always update the PAA with invalid POPAs consuming host routes.
There is really no redirection attack as the route is not used until the packets are
sent that would use the route. So, the only possibility is to generate invalid host
routes. How can PAA check to make sure that this is not happening ? Can the same
happen with device-ID update consuming some other resource ? The framework
document is still not clear on what happens during a device-Id update.

-mohan


-mohan


> 
> Yoshihiro Ohba
> 
> 
> 
> > 
> > 
> > > Which is better or any other ways?
> > > 
> >  > Yoshihiro Ohba
> > > 
> > 
> > -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 May  6 15:42:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14881
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 15:42:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLog0-0005S1-9H; Thu, 06 May 2004 15:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLoZA-0002m2-Q5
	for pana@optimus.ietf.org; Thu, 06 May 2004 15:29:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14329
	for <pana@ietf.org>; Thu, 6 May 2004 15:29:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLoZ9-0004lc-EV
	for pana@ietf.org; Thu, 06 May 2004 15:29:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLoYC-0004Mj-00
	for pana@ietf.org; Thu, 06 May 2004 15:28:57 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLoXK-0003Zd-00
	for pana@ietf.org; Thu, 06 May 2004 15:28:02 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXB00G014PUUE@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 04:27:31 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXB003BW4PUXA@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 04:27:30 +0900 (KST)
Received: from Alperyegin ([105.253.155.8])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXB000034PROB@mmp1.samsung.com> for pana@ietf.org;
 Fri, 07 May 2004 04:27:30 +0900 (KST)
Date: Thu, 06 May 2004 12:27:27 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <015201c433a0$2c22d240$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] RE: issue59: TTL and other IP layer details (update)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 earlier transmissions of this message failed..... let me try again.)



One proposed revision on the UDP port specification... This came up
during some IPsec discussions. In order to be able to enforce UDP port
based SPDs, we need to make sure at least one of the ports in a PANA
packet is assigned the official PANA port number. So:

In the newly proposed section 9.1, we had said:

   When the PANA packet is sent in response to a request, the UDP
   destination port MUST be copied from the source port of the
   corresponding packet.  An unsolicited PANA packet MUST set its
   destination port to a well-known value (TBD).  In either case, the
   source port can be set to a value chosen by the sender.

Instead let's say:

   When the PANA packet is sent in response to a request, the UDP
   source and destination ports of the response packet MUST be copied 
   from the destination and source ports of the request packet, 
   respectively. The destination port of an unsolicited PANA packet 
   MUST be set to an assigned value (TBD), and the source port MUST be
   set to a value chosen by the sender.

Comments welcome.

Alper



> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@samsung.com]
> Sent: Tuesday, April 13, 2004 2:59 PM
> To: 'pana@ietf.org'
> Subject: issue59: TTL and other IP layer details
> 
> 
> Here is an attempt to fix this issue.
> 
> Change:
> 
> 4.1.7 Message Validity Check
> 
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
> 
>    o  Each field in the message header contains a valid value
including
>       sequence number, message length, message type, version number,
>       flags, etc.
> 
> To:
> 
> 4.1.7 Message Validity Check
> 
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
> 
>    o  The IP Hop Limit (or TTL) field has a value of 255, i.e., the
packet
>       could not possibly have been forwarded by a router.
> 
>    o  Each field in the message header contains a valid value
including
>       sequence number, message length, message type, version number,
>       flags, etc.
> 
> 
> Insert a new section 9.1:
> 
> 9.1 IP and UDP Headers
> 
> The Hop Limit (or TTL) field of the IP header MUST be set to 255. IP 
> destination address of a PANA-PAA-Discover message is set to a 
> well-known link-local multicast address (TBD). Any other PANA packet 
> is unicasted between the PaC and the PAA. The source and destination 
> addresses SHOULD be set to the addresses on the interfaces from which 
> the message will be sent and received, respectively.
> 
> When the PANA packet is sent in response to a request, the UDP 
> destination port MUST be copied from the source port of the 
> corresponding packet. An unsolicited PANA packet MUST set its 
> destination port to a well-known value (TBD). In either case, the 
> source port can be set to a value chosen by the sender.
> 
> 
> Also:
> 
> 4.1.2 Transport Layer Protocol
> 
>    PANA uses UDP as its transport layer protocol.  The UDP port number
>    is TBD.  All messages except for PANA-PAA-Discover are always
>    unicast.  PaC MUST NOT use unspecified IP address for communicating
>    with PAA.
> 
> Let's remove the last statement, we don't have to state that 
> unspecified addressed cannot be used (it's obvious).
> 
> Alper
> 



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


From exim@www1.ietf.org  Thu May  6 15:51:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15772
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 15:51:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLoqh-0001Fh-Hd
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 15:48:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46Jm3Kc004813
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 15:48:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLom6-0007rS-1n
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 15:43:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14984
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 15:43:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLom4-0002Pr-LD
	for pana-web-archive@ietf.org; Thu, 06 May 2004 15:43:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLol7-0001ym-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 15:42:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLokS-0001Y4-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 15:41:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLog0-0005S1-9H; Thu, 06 May 2004 15:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLoZA-0002m2-Q5
	for pana@optimus.ietf.org; Thu, 06 May 2004 15:29:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14329
	for <pana@ietf.org>; Thu, 6 May 2004 15:29:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLoZ9-0004lc-EV
	for pana@ietf.org; Thu, 06 May 2004 15:29:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLoYC-0004Mj-00
	for pana@ietf.org; Thu, 06 May 2004 15:28:57 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLoXK-0003Zd-00
	for pana@ietf.org; Thu, 06 May 2004 15:28:02 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXB00G014PUUE@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 04:27:31 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXB003BW4PUXA@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 04:27:30 +0900 (KST)
Received: from Alperyegin ([105.253.155.8])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXB000034PROB@mmp1.samsung.com> for pana@ietf.org;
 Fri, 07 May 2004 04:27:30 +0900 (KST)
Date: Thu, 06 May 2004 12:27:27 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <015201c433a0$2c22d240$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Pana] RE: issue59: TTL and other IP layer details (update)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

(My earlier transmissions of this message failed..... let me try again.)



One proposed revision on the UDP port specification... This came up
during some IPsec discussions. In order to be able to enforce UDP port
based SPDs, we need to make sure at least one of the ports in a PANA
packet is assigned the official PANA port number. So:

In the newly proposed section 9.1, we had said:

   When the PANA packet is sent in response to a request, the UDP
   destination port MUST be copied from the source port of the
   corresponding packet.  An unsolicited PANA packet MUST set its
   destination port to a well-known value (TBD).  In either case, the
   source port can be set to a value chosen by the sender.

Instead let's say:

   When the PANA packet is sent in response to a request, the UDP
   source and destination ports of the response packet MUST be copied 
   from the destination and source ports of the request packet, 
   respectively. The destination port of an unsolicited PANA packet 
   MUST be set to an assigned value (TBD), and the source port MUST be
   set to a value chosen by the sender.

Comments welcome.

Alper



> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@samsung.com]
> Sent: Tuesday, April 13, 2004 2:59 PM
> To: 'pana@ietf.org'
> Subject: issue59: TTL and other IP layer details
> 
> 
> Here is an attempt to fix this issue.
> 
> Change:
> 
> 4.1.7 Message Validity Check
> 
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
> 
>    o  Each field in the message header contains a valid value
including
>       sequence number, message length, message type, version number,
>       flags, etc.
> 
> To:
> 
> 4.1.7 Message Validity Check
> 
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
> 
>    o  The IP Hop Limit (or TTL) field has a value of 255, i.e., the
packet
>       could not possibly have been forwarded by a router.
> 
>    o  Each field in the message header contains a valid value
including
>       sequence number, message length, message type, version number,
>       flags, etc.
> 
> 
> Insert a new section 9.1:
> 
> 9.1 IP and UDP Headers
> 
> The Hop Limit (or TTL) field of the IP header MUST be set to 255. IP 
> destination address of a PANA-PAA-Discover message is set to a 
> well-known link-local multicast address (TBD). Any other PANA packet 
> is unicasted between the PaC and the PAA. The source and destination 
> addresses SHOULD be set to the addresses on the interfaces from which 
> the message will be sent and received, respectively.
> 
> When the PANA packet is sent in response to a request, the UDP 
> destination port MUST be copied from the source port of the 
> corresponding packet. An unsolicited PANA packet MUST set its 
> destination port to a well-known value (TBD). In either case, the 
> source port can be set to a value chosen by the sender.
> 
> 
> Also:
> 
> 4.1.2 Transport Layer Protocol
> 
>    PANA uses UDP as its transport layer protocol.  The UDP port number
>    is TBD.  All messages except for PANA-PAA-Discover are always
>    unicast.  PaC MUST NOT use unspecified IP address for communicating
>    with PAA.
> 
> Let's remove the last statement, we don't have to state that 
> unspecified addressed cannot be used (it's obvious).
> 
> Alper
> 



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



From pana-admin@ietf.org  Thu May  6 20:42:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00705
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 20:42:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtLO-000592-N0; Thu, 06 May 2004 20:36:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtGm-0003TC-Cx
	for pana@optimus.ietf.org; Thu, 06 May 2004 20:31:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00087
	for <pana@ietf.org>; Thu, 6 May 2004 20:31:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLtGk-0006dU-0y
	for pana@ietf.org; Thu, 06 May 2004 20:31:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLtFm-0006Eu-00
	for pana@ietf.org; Thu, 06 May 2004 20:30:15 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLtFO-0005qA-00
	for pana@ietf.org; Thu, 06 May 2004 20:29:50 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXB00801IOWJF@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 09:29:20 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXB006JFIOVY3@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 09:29:20 +0900 (KST)
Received: from Alperyegin ([105.253.155.8])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXB005Q4IOSFI@mmp2.samsung.com> for pana@ietf.org;
 Fri, 07 May 2004 09:29:19 +0900 (KST)
Date: Thu, 06 May 2004 17:29:15 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] host route
In-reply-to: <001101c43395$c41d8870$6801a8c0@adithya>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Message-id: <017c01c433ca$5586e250$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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


Do we still have device ID update via PANA reauth in the spec? We don't
have device ID update anymore.

Alper




> -----Original Message-----
> From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
Mohan
> Parthasarathy
> Sent: Thursday, May 06, 2004 11:13 AM
> To: Yoshihiro Ohba
> Cc: pana@ietf.org
> Subject: Re: [Pana] host route
> 
> 
> > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > >
> > >
> > > > I came up with an issue after submitting
> > > > draft-ietf-pana-framework-00.txt.
> > > >
> > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > >
> > > >       "PRPA and the IP address of PAA are assumed to be on the
same
> IP
> > > >       subnet, hence the PaC and PAA can perform on-link
> communication as
> > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
with
> POPA,
> > > >       this assumption may not hold true. In order to maintain
the
> same
> > > >       on-link communication, the PaC and PAA SHOULD create host
> routes
> > > >       to each other upon PaC's IP address change.  The PaC
SHOULD
> create
> > > >       a host route to the PAA, and the PAA SHOULD create a host
> route to
> > > >       the PaC (POPA)."
> > > >
> > > > In order to create a host route to the PaC, the PAA needs to
know
> the
> > > > POPA.  However, when MAC address is used as the device-id, no
> > > > device-id update occurs in PANA, and I am wondering how the PAA
can
> > > > know the POPA.  There would be several ways to deal with this:
> > > >
> > > > - PAA listens to DHCP or data traffic on the link to know the
POPA.
> > > >
> > > > - PAA communicates with DHCP server (by using some other
protocol
> such
> > > > as SNMP) to know the POPA.
> > > >
> > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
a
> > > >   new AVP that carries the POPA.
> > > >
> > > This sounds like a better option so that we can keep the device-Id
> update and POPA
> > > update separate. I never understood the reason for using Reauth
> request for updates.
> > > Why isn't this a generic update mechanism protected by PANA SA ?
> >
> >
> > As far as I remember, one usage of PANA-Reauth exchange has been to
> > allow PaC to its its Device-Id in a secure way.  It seems that
sending
> > the POPA is not much different from updating Device-Id, and that is
> > why I mentioned PANA-Reauth exchange.  But we could define a
separate
> > mechanism/message for updating an address if we want.  In my
> > experiance, having a separate mechanism/message might be good for
> > reducing the chance of mis-implementation coming from using the same
> > message for many purposes.
> >
> As we have more than one update now, it might make sense to provide a
> separate
> mechanism instead of over-loading the reauth.
> 
> There is a difference between device-ID update and POPA update. There
is
> not
> much incentive for the PaC to update with a device-ID that belongs to
> someone else.
> But PaC can always update the PAA with invalid POPAs consuming host
routes.
> There is really no redirection attack as the route is not used until
the
> packets are
> sent that would use the route. So, the only possibility is to generate
> invalid host
> routes. How can PAA check to make sure that this is not happening ?
Can
> the same
> happen with device-ID update consuming some other resource ? The
framework
> document is still not clear on what happens during a device-Id update.
> 
> -mohan
> 
> 
> -mohan
> 
> 
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > >
> > > > Which is better or any other ways?
> > > >
> > >  > Yoshihiro Ohba
> > > >
> > >
> > > -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 May  6 20:51:13 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01158
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 20:51:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtXm-0000Nt-9d
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 20:48:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i470mo2q001473
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 20:48:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtSV-0007NU-O5
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 20:43:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00794
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 20:43:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLtST-0003p4-Cz
	for pana-web-archive@ietf.org; Thu, 06 May 2004 20:43:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLtRU-0003Oo-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 20:42:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLtQu-0002zB-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 20:41:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtLO-000592-N0; Thu, 06 May 2004 20:36:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLtGm-0003TC-Cx
	for pana@optimus.ietf.org; Thu, 06 May 2004 20:31:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00087
	for <pana@ietf.org>; Thu, 6 May 2004 20:31:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLtGk-0006dU-0y
	for pana@ietf.org; Thu, 06 May 2004 20:31:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLtFm-0006Eu-00
	for pana@ietf.org; Thu, 06 May 2004 20:30:15 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLtFO-0005qA-00
	for pana@ietf.org; Thu, 06 May 2004 20:29:50 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXB00801IOWJF@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 09:29:20 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXB006JFIOVY3@mailout3.samsung.com> for pana@ietf.org; Fri,
 07 May 2004 09:29:20 +0900 (KST)
Received: from Alperyegin ([105.253.155.8])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXB005Q4IOSFI@mmp2.samsung.com> for pana@ietf.org;
 Fri, 07 May 2004 09:29:19 +0900 (KST)
Date: Thu, 06 May 2004 17:29:15 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] host route
In-reply-to: <001101c43395$c41d8870$6801a8c0@adithya>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Message-id: <017c01c433ca$5586e250$991d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT


Do we still have device ID update via PANA reauth in the spec? We don't
have device ID update anymore.

Alper




> -----Original Message-----
> From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
Mohan
> Parthasarathy
> Sent: Thursday, May 06, 2004 11:13 AM
> To: Yoshihiro Ohba
> Cc: pana@ietf.org
> Subject: Re: [Pana] host route
> 
> 
> > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > >
> > >
> > > > I came up with an issue after submitting
> > > > draft-ietf-pana-framework-00.txt.
> > > >
> > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > >
> > > >       "PRPA and the IP address of PAA are assumed to be on the
same
> IP
> > > >       subnet, hence the PaC and PAA can perform on-link
> communication as
> > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
with
> POPA,
> > > >       this assumption may not hold true. In order to maintain
the
> same
> > > >       on-link communication, the PaC and PAA SHOULD create host
> routes
> > > >       to each other upon PaC's IP address change.  The PaC
SHOULD
> create
> > > >       a host route to the PAA, and the PAA SHOULD create a host
> route to
> > > >       the PaC (POPA)."
> > > >
> > > > In order to create a host route to the PaC, the PAA needs to
know
> the
> > > > POPA.  However, when MAC address is used as the device-id, no
> > > > device-id update occurs in PANA, and I am wondering how the PAA
can
> > > > know the POPA.  There would be several ways to deal with this:
> > > >
> > > > - PAA listens to DHCP or data traffic on the link to know the
POPA.
> > > >
> > > > - PAA communicates with DHCP server (by using some other
protocol
> such
> > > > as SNMP) to know the POPA.
> > > >
> > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
a
> > > >   new AVP that carries the POPA.
> > > >
> > > This sounds like a better option so that we can keep the device-Id
> update and POPA
> > > update separate. I never understood the reason for using Reauth
> request for updates.
> > > Why isn't this a generic update mechanism protected by PANA SA ?
> >
> >
> > As far as I remember, one usage of PANA-Reauth exchange has been to
> > allow PaC to its its Device-Id in a secure way.  It seems that
sending
> > the POPA is not much different from updating Device-Id, and that is
> > why I mentioned PANA-Reauth exchange.  But we could define a
separate
> > mechanism/message for updating an address if we want.  In my
> > experiance, having a separate mechanism/message might be good for
> > reducing the chance of mis-implementation coming from using the same
> > message for many purposes.
> >
> As we have more than one update now, it might make sense to provide a
> separate
> mechanism instead of over-loading the reauth.
> 
> There is a difference between device-ID update and POPA update. There
is
> not
> much incentive for the PaC to update with a device-ID that belongs to
> someone else.
> But PaC can always update the PAA with invalid POPAs consuming host
routes.
> There is really no redirection attack as the route is not used until
the
> packets are
> sent that would use the route. So, the only possibility is to generate
> invalid host
> routes. How can PAA check to make sure that this is not happening ?
Can
> the same
> happen with device-ID update consuming some other resource ? The
framework
> document is still not clear on what happens during a device-Id update.
> 
> -mohan
> 
> 
> -mohan
> 
> 
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > >
> > > > Which is better or any other ways?
> > > >
> > >  > Yoshihiro Ohba
> > > >
> > >
> > > -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 May  6 23:28:12 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07764
	for <pana-archive@lists.ietf.org>; Thu, 6 May 2004 23:28:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLvxy-0000xy-4O; Thu, 06 May 2004 23:24:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLvxH-0000gu-R2
	for pana@optimus.ietf.org; Thu, 06 May 2004 23:23:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07595
	for <pana@ietf.org>; Thu, 6 May 2004 23:23:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLvxF-0006Yf-Eo
	for pana@ietf.org; Thu, 06 May 2004 23:23:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLvwK-00068K-00
	for pana@ietf.org; Thu, 06 May 2004 23:22:21 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLvvO-0005hN-00
	for pana@ietf.org; Thu, 06 May 2004 23:21:22 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i473LKgH012481;
	Fri, 7 May 2004 12:21:20 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i473LFTZ005298;
	Fri, 7 May 2004 12:21:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA05290 ; Fri, 7 May 2004 12:21:15 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA21966; Fri, 7 May 2004 12:21:15 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA20939; Fri, 7 May 2004 12:21:14 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i473LEEU012351;
	Fri, 7 May 2004 12:21:14 +0900 (JST)
Received: from steelhead (iVPN01-135.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 <0HXB008E9QNBXS@tsbpo1.po.toshiba.co.jp>; Fri,
 7 May 2004 12:21:13 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLvue-0002IZ-00; Thu, 06 May 2004 20:20:36 -0700
Date: Thu, 06 May 2004 20:20:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <017c01c433ca$5586e250$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040507032036.GR23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Mohan Parthasarathy' <mohanp@sbcglobal.net>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <001101c43395$c41d8870$6801a8c0@adithya>
 <017c01c433ca$5586e250$991d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Thu, May 06, 2004 at 05:29:15PM -0700, Alper Yegin wrote:
> 
> Do we still have device ID update via PANA reauth in the spec? We don't
> have device ID update anymore.

In draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1
and Case C of IPv6 in Appendix A.2 use the device id update mechanism.

Yoshihiro Ohba



> 
> Alper
> 
> 
> 
> 
> > -----Original Message-----
> > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> Mohan
> > Parthasarathy
> > Sent: Thursday, May 06, 2004 11:13 AM
> > To: Yoshihiro Ohba
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] host route
> > 
> > 
> > > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > > >
> > > >
> > > > > I came up with an issue after submitting
> > > > > draft-ietf-pana-framework-00.txt.
> > > > >
> > > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > > >
> > > > >       "PRPA and the IP address of PAA are assumed to be on the
> same
> > IP
> > > > >       subnet, hence the PaC and PAA can perform on-link
> > communication as
> > > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
> with
> > POPA,
> > > > >       this assumption may not hold true. In order to maintain
> the
> > same
> > > > >       on-link communication, the PaC and PAA SHOULD create host
> > routes
> > > > >       to each other upon PaC's IP address change.  The PaC
> SHOULD
> > create
> > > > >       a host route to the PAA, and the PAA SHOULD create a host
> > route to
> > > > >       the PaC (POPA)."
> > > > >
> > > > > In order to create a host route to the PaC, the PAA needs to
> know
> > the
> > > > > POPA.  However, when MAC address is used as the device-id, no
> > > > > device-id update occurs in PANA, and I am wondering how the PAA
> can
> > > > > know the POPA.  There would be several ways to deal with this:
> > > > >
> > > > > - PAA listens to DHCP or data traffic on the link to know the
> POPA.
> > > > >
> > > > > - PAA communicates with DHCP server (by using some other
> protocol
> > such
> > > > > as SNMP) to know the POPA.
> > > > >
> > > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
> a
> > > > >   new AVP that carries the POPA.
> > > > >
> > > > This sounds like a better option so that we can keep the device-Id
> > update and POPA
> > > > update separate. I never understood the reason for using Reauth
> > request for updates.
> > > > Why isn't this a generic update mechanism protected by PANA SA ?
> > >
> > >
> > > As far as I remember, one usage of PANA-Reauth exchange has been to
> > > allow PaC to its its Device-Id in a secure way.  It seems that
> sending
> > > the POPA is not much different from updating Device-Id, and that is
> > > why I mentioned PANA-Reauth exchange.  But we could define a
> separate
> > > mechanism/message for updating an address if we want.  In my
> > > experiance, having a separate mechanism/message might be good for
> > > reducing the chance of mis-implementation coming from using the same
> > > message for many purposes.
> > >
> > As we have more than one update now, it might make sense to provide a
> > separate
> > mechanism instead of over-loading the reauth.
> > 
> > There is a difference between device-ID update and POPA update. There
> is
> > not
> > much incentive for the PaC to update with a device-ID that belongs to
> > someone else.
> > But PaC can always update the PAA with invalid POPAs consuming host
> routes.
> > There is really no redirection attack as the route is not used until
> the
> > packets are
> > sent that would use the route. So, the only possibility is to generate
> > invalid host
> > routes. How can PAA check to make sure that this is not happening ?
> Can
> > the same
> > happen with device-ID update consuming some other resource ? The
> framework
> > document is still not clear on what happens during a device-Id update.
> > 
> > -mohan
> > 
> > 
> > -mohan
> > 
> > 
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > >
> > > > > Which is better or any other ways?
> > > > >
> > > >  > Yoshihiro Ohba
> > > > >
> > > >
> > > > -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  Thu May  6 23:35:19 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08144
	for <pana-archive@odin.ietf.org>; Thu, 6 May 2004 23:35:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLw4S-0002fk-Pc
	for pana-archive@odin.ietf.org; Thu, 06 May 2004 23:30:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i473Ui3K010272
	for pana-archive@odin.ietf.org; Thu, 6 May 2004 23:30:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLw37-0001yS-ML
	for pana-web-archive@optimus.ietf.org; Thu, 06 May 2004 23:29:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07823
	for <pana-web-archive@ietf.org>; Thu, 6 May 2004 23:29:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLw35-0001F7-Mj
	for pana-web-archive@ietf.org; Thu, 06 May 2004 23:29:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLw2E-0000px-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 23:28:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLw1X-0000Qn-00
	for pana-web-archive@ietf.org; Thu, 06 May 2004 23:27:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLvxy-0000xy-4O; Thu, 06 May 2004 23:24:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLvxH-0000gu-R2
	for pana@optimus.ietf.org; Thu, 06 May 2004 23:23:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07595
	for <pana@ietf.org>; Thu, 6 May 2004 23:23:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLvxF-0006Yf-Eo
	for pana@ietf.org; Thu, 06 May 2004 23:23:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLvwK-00068K-00
	for pana@ietf.org; Thu, 06 May 2004 23:22:21 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLvvO-0005hN-00
	for pana@ietf.org; Thu, 06 May 2004 23:21:22 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i473LKgH012481;
	Fri, 7 May 2004 12:21:20 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i473LFTZ005298;
	Fri, 7 May 2004 12:21:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA05290 ; Fri, 7 May 2004 12:21:15 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA21966; Fri, 7 May 2004 12:21:15 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA20939; Fri, 7 May 2004 12:21:14 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i473LEEU012351;
	Fri, 7 May 2004 12:21:14 +0900 (JST)
Received: from steelhead (iVPN01-135.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 <0HXB008E9QNBXS@tsbpo1.po.toshiba.co.jp>; Fri,
 7 May 2004 12:21:13 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BLvue-0002IZ-00; Thu, 06 May 2004 20:20:36 -0700
Date: Thu, 06 May 2004 20:20:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <017c01c433ca$5586e250$991d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040507032036.GR23909@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Mohan Parthasarathy' <mohanp@sbcglobal.net>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <001101c43395$c41d8870$6801a8c0@adithya>
 <017c01c433ca$5586e250$991d9069@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, May 06, 2004 at 05:29:15PM -0700, Alper Yegin wrote:
> 
> Do we still have device ID update via PANA reauth in the spec? We don't
> have device ID update anymore.

In draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1
and Case C of IPv6 in Appendix A.2 use the device id update mechanism.

Yoshihiro Ohba



> 
> Alper
> 
> 
> 
> 
> > -----Original Message-----
> > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> Mohan
> > Parthasarathy
> > Sent: Thursday, May 06, 2004 11:13 AM
> > To: Yoshihiro Ohba
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] host route
> > 
> > 
> > > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > > >
> > > >
> > > > > I came up with an issue after submitting
> > > > > draft-ietf-pana-framework-00.txt.
> > > > >
> > > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > > >
> > > > >       "PRPA and the IP address of PAA are assumed to be on the
> same
> > IP
> > > > >       subnet, hence the PaC and PAA can perform on-link
> > communication as
> > > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
> with
> > POPA,
> > > > >       this assumption may not hold true. In order to maintain
> the
> > same
> > > > >       on-link communication, the PaC and PAA SHOULD create host
> > routes
> > > > >       to each other upon PaC's IP address change.  The PaC
> SHOULD
> > create
> > > > >       a host route to the PAA, and the PAA SHOULD create a host
> > route to
> > > > >       the PaC (POPA)."
> > > > >
> > > > > In order to create a host route to the PaC, the PAA needs to
> know
> > the
> > > > > POPA.  However, when MAC address is used as the device-id, no
> > > > > device-id update occurs in PANA, and I am wondering how the PAA
> can
> > > > > know the POPA.  There would be several ways to deal with this:
> > > > >
> > > > > - PAA listens to DHCP or data traffic on the link to know the
> POPA.
> > > > >
> > > > > - PAA communicates with DHCP server (by using some other
> protocol
> > such
> > > > > as SNMP) to know the POPA.
> > > > >
> > > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
> a
> > > > >   new AVP that carries the POPA.
> > > > >
> > > > This sounds like a better option so that we can keep the device-Id
> > update and POPA
> > > > update separate. I never understood the reason for using Reauth
> > request for updates.
> > > > Why isn't this a generic update mechanism protected by PANA SA ?
> > >
> > >
> > > As far as I remember, one usage of PANA-Reauth exchange has been to
> > > allow PaC to its its Device-Id in a secure way.  It seems that
> sending
> > > the POPA is not much different from updating Device-Id, and that is
> > > why I mentioned PANA-Reauth exchange.  But we could define a
> separate
> > > mechanism/message for updating an address if we want.  In my
> > > experiance, having a separate mechanism/message might be good for
> > > reducing the chance of mis-implementation coming from using the same
> > > message for many purposes.
> > >
> > As we have more than one update now, it might make sense to provide a
> > separate
> > mechanism instead of over-loading the reauth.
> > 
> > There is a difference between device-ID update and POPA update. There
> is
> > not
> > much incentive for the PaC to update with a device-ID that belongs to
> > someone else.
> > But PaC can always update the PAA with invalid POPAs consuming host
> routes.
> > There is really no redirection attack as the route is not used until
> the
> > packets are
> > sent that would use the route. So, the only possibility is to generate
> > invalid host
> > routes. How can PAA check to make sure that this is not happening ?
> Can
> > the same
> > happen with device-ID update consuming some other resource ? The
> framework
> > document is still not clear on what happens during a device-Id update.
> > 
> > -mohan
> > 
> > 
> > -mohan
> > 
> > 
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > >
> > > > > Which is better or any other ways?
> > > > >
> > > >  > Yoshihiro Ohba
> > > > >
> > > >
> > > > -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  Fri May  7 13:32:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07601
	for <pana-archive@lists.ietf.org>; Fri, 7 May 2004 13:32:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM97n-0002cZ-3z; Fri, 07 May 2004 13:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM94n-0001hW-J1
	for pana@optimus.ietf.org; Fri, 07 May 2004 13:23:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07265
	for <pana@ietf.org>; Fri, 7 May 2004 13:23:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM94l-0006cj-JI
	for pana@ietf.org; Fri, 07 May 2004 13:23:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM93r-0006C6-00
	for pana@ietf.org; Fri, 07 May 2004 13:23:00 -0400
Received: from smtp805.mail.sc5.yahoo.com ([66.163.168.184])
	by ietf-mx with smtp (Exim 4.12)
	id 1BM92w-0005lD-00
	for pana@ietf.org; Fri, 07 May 2004 13:22:02 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.59.221 with login)
  by smtp805.mail.sc5.yahoo.com with SMTP; 7 May 2004 17:22:01 -0000
Message-ID: <002601c43457$d0a219e0$6501a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>,
        "Alper Yegin" <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <001101c43395$c41d8870$6801a8c0@adithya> <017c01c433ca$5586e250$991d9069@sisa.samsung.com> <20040507032036.GR23909@steelhead>
Subject: Re: [Pana] host route
Date: Fri, 7 May 2004 10:22:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 Thu, May 06, 2004 at 05:29:15PM -0700, Alper Yegin wrote:
> > 
> > Do we still have device ID update via PANA reauth in the spec? We don't
> > have device ID update anymore.
> 
> In draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1
> and Case C of IPv6 in Appendix A.2 use the device id update mechanism.
> 
I think the base spec should mention the update mechanism somewhere.

-mohan

> Yoshihiro Ohba
> 
> 
> 
> > 
> > Alper
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> > Mohan
> > > Parthasarathy
> > > Sent: Thursday, May 06, 2004 11:13 AM
> > > To: Yoshihiro Ohba
> > > Cc: pana@ietf.org
> > > Subject: Re: [Pana] host route
> > > 
> > > 
> > > > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > > > >
> > > > >
> > > > > > I came up with an issue after submitting
> > > > > > draft-ietf-pana-framework-00.txt.
> > > > > >
> > > > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > > > >
> > > > > >       "PRPA and the IP address of PAA are assumed to be on the
> > same
> > > IP
> > > > > >       subnet, hence the PaC and PAA can perform on-link
> > > communication as
> > > > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
> > with
> > > POPA,
> > > > > >       this assumption may not hold true. In order to maintain
> > the
> > > same
> > > > > >       on-link communication, the PaC and PAA SHOULD create host
> > > routes
> > > > > >       to each other upon PaC's IP address change.  The PaC
> > SHOULD
> > > create
> > > > > >       a host route to the PAA, and the PAA SHOULD create a host
> > > route to
> > > > > >       the PaC (POPA)."
> > > > > >
> > > > > > In order to create a host route to the PaC, the PAA needs to
> > know
> > > the
> > > > > > POPA.  However, when MAC address is used as the device-id, no
> > > > > > device-id update occurs in PANA, and I am wondering how the PAA
> > can
> > > > > > know the POPA.  There would be several ways to deal with this:
> > > > > >
> > > > > > - PAA listens to DHCP or data traffic on the link to know the
> > POPA.
> > > > > >
> > > > > > - PAA communicates with DHCP server (by using some other
> > protocol
> > > such
> > > > > > as SNMP) to know the POPA.
> > > > > >
> > > > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
> > a
> > > > > >   new AVP that carries the POPA.
> > > > > >
> > > > > This sounds like a better option so that we can keep the device-Id
> > > update and POPA
> > > > > update separate. I never understood the reason for using Reauth
> > > request for updates.
> > > > > Why isn't this a generic update mechanism protected by PANA SA ?
> > > >
> > > >
> > > > As far as I remember, one usage of PANA-Reauth exchange has been to
> > > > allow PaC to its its Device-Id in a secure way.  It seems that
> > sending
> > > > the POPA is not much different from updating Device-Id, and that is
> > > > why I mentioned PANA-Reauth exchange.  But we could define a
> > separate
> > > > mechanism/message for updating an address if we want.  In my
> > > > experiance, having a separate mechanism/message might be good for
> > > > reducing the chance of mis-implementation coming from using the same
> > > > message for many purposes.
> > > >
> > > As we have more than one update now, it might make sense to provide a
> > > separate
> > > mechanism instead of over-loading the reauth.
> > > 
> > > There is a difference between device-ID update and POPA update. There
> > is
> > > not
> > > much incentive for the PaC to update with a device-ID that belongs to
> > > someone else.
> > > But PaC can always update the PAA with invalid POPAs consuming host
> > routes.
> > > There is really no redirection attack as the route is not used until
> > the
> > > packets are
> > > sent that would use the route. So, the only possibility is to generate
> > > invalid host
> > > routes. How can PAA check to make sure that this is not happening ?
> > Can
> > > the same
> > > happen with device-ID update consuming some other resource ? The
> > framework
> > > document is still not clear on what happens during a device-Id update.
> > > 
> > > -mohan
> > > 
> > > 
> > > -mohan
> > > 
> > > 
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > > Which is better or any other ways?
> > > > > >
> > > > >  > Yoshihiro Ohba
> > > > > >
> > > > >
> > > > > -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  Fri May  7 13:42:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08187
	for <pana-archive@odin.ietf.org>; Fri, 7 May 2004 13:42:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM9Lo-00070x-Ks
	for pana-archive@odin.ietf.org; Fri, 07 May 2004 13:41:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47HfW7j026962
	for pana-archive@odin.ietf.org; Fri, 7 May 2004 13:41:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM9Dc-0004Na-Q5
	for pana-web-archive@optimus.ietf.org; Fri, 07 May 2004 13:33:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07669
	for <pana-web-archive@ietf.org>; Fri, 7 May 2004 13:33:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM9Da-0002oi-Oa
	for pana-web-archive@ietf.org; Fri, 07 May 2004 13:33:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM9CZ-0002NI-00
	for pana-web-archive@ietf.org; Fri, 07 May 2004 13:32:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM9C7-0001x2-00
	for pana-web-archive@ietf.org; Fri, 07 May 2004 13:31:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM97n-0002cZ-3z; Fri, 07 May 2004 13:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM94n-0001hW-J1
	for pana@optimus.ietf.org; Fri, 07 May 2004 13:23:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07265
	for <pana@ietf.org>; Fri, 7 May 2004 13:23:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM94l-0006cj-JI
	for pana@ietf.org; Fri, 07 May 2004 13:23:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM93r-0006C6-00
	for pana@ietf.org; Fri, 07 May 2004 13:23:00 -0400
Received: from smtp805.mail.sc5.yahoo.com ([66.163.168.184])
	by ietf-mx with smtp (Exim 4.12)
	id 1BM92w-0005lD-00
	for pana@ietf.org; Fri, 07 May 2004 13:22:02 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.59.221 with login)
  by smtp805.mail.sc5.yahoo.com with SMTP; 7 May 2004 17:22:01 -0000
Message-ID: <002601c43457$d0a219e0$6501a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>,
        "Alper Yegin" <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <001101c43395$c41d8870$6801a8c0@adithya> <017c01c433ca$5586e250$991d9069@sisa.samsung.com> <20040507032036.GR23909@steelhead>
Subject: Re: [Pana] host route
Date: Fri, 7 May 2004 10:22:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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 Thu, May 06, 2004 at 05:29:15PM -0700, Alper Yegin wrote:
> > 
> > Do we still have device ID update via PANA reauth in the spec? We don't
> > have device ID update anymore.
> 
> In draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1
> and Case C of IPv6 in Appendix A.2 use the device id update mechanism.
> 
I think the base spec should mention the update mechanism somewhere.

-mohan

> Yoshihiro Ohba
> 
> 
> 
> > 
> > Alper
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> > Mohan
> > > Parthasarathy
> > > Sent: Thursday, May 06, 2004 11:13 AM
> > > To: Yoshihiro Ohba
> > > Cc: pana@ietf.org
> > > Subject: Re: [Pana] host route
> > > 
> > > 
> > > > On Thu, May 06, 2004 at 10:05:11AM -0700, Mohan Parthasarathy wrote:
> > > > >
> > > > >
> > > > > > I came up with an issue after submitting
> > > > > > draft-ietf-pana-framework-00.txt.
> > > > > >
> > > > > > In section 5 of draft-ietf-pana-framework-00.txt:
> > > > > >
> > > > > >       "PRPA and the IP address of PAA are assumed to be on the
> > same
> > > IP
> > > > > >       subnet, hence the PaC and PAA can perform on-link
> > > communication as
> > > > > >       required by PANA.  When the PaC replaces its IPv4 PRPA
> > with
> > > POPA,
> > > > > >       this assumption may not hold true. In order to maintain
> > the
> > > same
> > > > > >       on-link communication, the PaC and PAA SHOULD create host
> > > routes
> > > > > >       to each other upon PaC's IP address change.  The PaC
> > SHOULD
> > > create
> > > > > >       a host route to the PAA, and the PAA SHOULD create a host
> > > route to
> > > > > >       the PaC (POPA)."
> > > > > >
> > > > > > In order to create a host route to the PaC, the PAA needs to
> > know
> > > the
> > > > > > POPA.  However, when MAC address is used as the device-id, no
> > > > > > device-id update occurs in PANA, and I am wondering how the PAA
> > can
> > > > > > know the POPA.  There would be several ways to deal with this:
> > > > > >
> > > > > > - PAA listens to DHCP or data traffic on the link to know the
> > POPA.
> > > > > >
> > > > > > - PAA communicates with DHCP server (by using some other
> > protocol
> > > such
> > > > > > as SNMP) to know the POPA.
> > > > > >
> > > > > > - After obtaining POPA, the PaC sends a PANA-Reauth-Request with
> > a
> > > > > >   new AVP that carries the POPA.
> > > > > >
> > > > > This sounds like a better option so that we can keep the device-Id
> > > update and POPA
> > > > > update separate. I never understood the reason for using Reauth
> > > request for updates.
> > > > > Why isn't this a generic update mechanism protected by PANA SA ?
> > > >
> > > >
> > > > As far as I remember, one usage of PANA-Reauth exchange has been to
> > > > allow PaC to its its Device-Id in a secure way.  It seems that
> > sending
> > > > the POPA is not much different from updating Device-Id, and that is
> > > > why I mentioned PANA-Reauth exchange.  But we could define a
> > separate
> > > > mechanism/message for updating an address if we want.  In my
> > > > experiance, having a separate mechanism/message might be good for
> > > > reducing the chance of mis-implementation coming from using the same
> > > > message for many purposes.
> > > >
> > > As we have more than one update now, it might make sense to provide a
> > > separate
> > > mechanism instead of over-loading the reauth.
> > > 
> > > There is a difference between device-ID update and POPA update. There
> > is
> > > not
> > > much incentive for the PaC to update with a device-ID that belongs to
> > > someone else.
> > > But PaC can always update the PAA with invalid POPAs consuming host
> > routes.
> > > There is really no redirection attack as the route is not used until
> > the
> > > packets are
> > > sent that would use the route. So, the only possibility is to generate
> > > invalid host
> > > routes. How can PAA check to make sure that this is not happening ?
> > Can
> > > the same
> > > happen with device-ID update consuming some other resource ? The
> > framework
> > > document is still not clear on what happens during a device-Id update.
> > > 
> > > -mohan
> > > 
> > > 
> > > -mohan
> > > 
> > > 
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > > Which is better or any other ways?
> > > > > >
> > > > >  > Yoshihiro Ohba
> > > > > >
> > > > >
> > > > > -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  Mon May 10 10:40:28 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08644
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 10:40:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBm9-000262-6Y; Mon, 10 May 2004 10:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBh5-0000wG-Jo
	for pana@optimus.ietf.org; Mon, 10 May 2004 10:23:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07506
	for <pana@ietf.org>; Mon, 10 May 2004 10:23:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNBh3-0005Em-Au
	for pana@ietf.org; Mon, 10 May 2004 10:23:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBg4-0004tR-00
	for pana@ietf.org; Mon, 10 May 2004 10:22:45 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBf3-0004FX-00
	for pana@ietf.org; Mon, 10 May 2004 10:21:41 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AELXgH022107;
	Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AELXrs021577;
	Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id ZAA21574 ; Mon, 10 May 2004 23:21:33 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA03491; Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA18149; Mon, 10 May 2004 23:21:32 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AELVEU019510;
	Mon, 10 May 2004 23:21:32 +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 <0HXI00FZA57S08@tsbpo1.po.toshiba.co.jp>; Mon,
 10 May 2004 23:21:31 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNBf9-0000mc-00; Mon, 10 May 2004 07:21:47 -0700
Date: Mon, 10 May 2004 07:21:47 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <001101c43395$c41d8870$6801a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040510142147.GC1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@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.1 required=5.0 tests=AWL 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 Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > 
> As we have more than one update now, it might make sense to provide a separate
> mechanism instead of over-loading the reauth.
> 
> There is a difference between device-ID update and POPA update. There is not
> much incentive for the PaC to update with a device-ID that belongs to someone else.
> But PaC can always update the PAA with invalid POPAs consuming host routes.
> There is really no redirection attack as the route is not used until the packets are
> sent that would use the route. So, the only possibility is to generate invalid host
> routes. How can PAA check to make sure that this is not happening ? 

I think the only way for PAA to check this is, as PANA is doing for
Device-Id checking, to compare the POPA aganst the source IP address
of the IP packet that carries the POPA in a PANA payload.  This
checking does not work if the PaC uses someone else's address for both
the POPA and the source IP address of the IP packet.  However, this
would not harm IF (i) the PAA does not allow the POPA update when the
POPA is already associated with someone else and (ii) the PAA does not
allow multiple host route entries per PaC.

> Can the same
> happen with device-ID update consuming some other resource ? 

I think so.  However, this would not harm as described above.

> The framework
> document is still not clear on what happens during a device-Id update.

I think describing something on a device-id and POPA update in PANA
specification should be sufficient.

Yoshihiro Ohba


> 
> -mohan
> 
> 
> -mohan
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > > 
> > > 
> > > > Which is better or any other ways?
> > > > 
> > >  > Yoshihiro Ohba
> > > > 
> > > 
> > > -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  Mon May 10 10:57:42 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09288
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 10:57:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNC6S-0004qx-9s
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 10:50:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AEo0Dl018655
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 10:50:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNByX-0004AB-JL
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 10:41:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08715
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 10:41:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNByV-0003e5-9I
	for pana-web-archive@ietf.org; Mon, 10 May 2004 10:41:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBxZ-0003Jj-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 10:40:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBwm-0002zv-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 10:40:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBm9-000262-6Y; Mon, 10 May 2004 10:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBh5-0000wG-Jo
	for pana@optimus.ietf.org; Mon, 10 May 2004 10:23:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07506
	for <pana@ietf.org>; Mon, 10 May 2004 10:23:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNBh3-0005Em-Au
	for pana@ietf.org; Mon, 10 May 2004 10:23:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBg4-0004tR-00
	for pana@ietf.org; Mon, 10 May 2004 10:22:45 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBf3-0004FX-00
	for pana@ietf.org; Mon, 10 May 2004 10:21:41 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AELXgH022107;
	Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AELXrs021577;
	Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id ZAA21574 ; Mon, 10 May 2004 23:21:33 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA03491; Mon, 10 May 2004 23:21:33 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA18149; Mon, 10 May 2004 23:21:32 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AELVEU019510;
	Mon, 10 May 2004 23:21:32 +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 <0HXI00FZA57S08@tsbpo1.po.toshiba.co.jp>; Mon,
 10 May 2004 23:21:31 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNBf9-0000mc-00; Mon, 10 May 2004 07:21:47 -0700
Date: Mon, 10 May 2004 07:21:47 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <001101c43395$c41d8870$6801a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040510142147.GC1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > 
> As we have more than one update now, it might make sense to provide a separate
> mechanism instead of over-loading the reauth.
> 
> There is a difference between device-ID update and POPA update. There is not
> much incentive for the PaC to update with a device-ID that belongs to someone else.
> But PaC can always update the PAA with invalid POPAs consuming host routes.
> There is really no redirection attack as the route is not used until the packets are
> sent that would use the route. So, the only possibility is to generate invalid host
> routes. How can PAA check to make sure that this is not happening ? 

I think the only way for PAA to check this is, as PANA is doing for
Device-Id checking, to compare the POPA aganst the source IP address
of the IP packet that carries the POPA in a PANA payload.  This
checking does not work if the PaC uses someone else's address for both
the POPA and the source IP address of the IP packet.  However, this
would not harm IF (i) the PAA does not allow the POPA update when the
POPA is already associated with someone else and (ii) the PAA does not
allow multiple host route entries per PaC.

> Can the same
> happen with device-ID update consuming some other resource ? 

I think so.  However, this would not harm as described above.

> The framework
> document is still not clear on what happens during a device-Id update.

I think describing something on a device-id and POPA update in PANA
specification should be sufficient.

Yoshihiro Ohba


> 
> -mohan
> 
> 
> -mohan
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > > 
> > > 
> > > > Which is better or any other ways?
> > > > 
> > >  > Yoshihiro Ohba
> > > > 
> > > 
> > > -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  Mon May 10 11:25:38 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11045
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 11:25:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCTk-0001NV-VS; Mon, 10 May 2004 11:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCLw-0007ni-1Z
	for pana@optimus.ietf.org; Mon, 10 May 2004 11:06:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09922
	for <pana@ietf.org>; Mon, 10 May 2004 11:05:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNCLt-000462-CE
	for pana@ietf.org; Mon, 10 May 2004 11:05:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCL2-0003li-00
	for pana@ietf.org; Mon, 10 May 2004 11:05:04 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCKE-0003J8-00
	for pana@ietf.org; Mon, 10 May 2004 11:04:15 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 7EA14285F5; Mon, 10 May 2004 17:03:43 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 64759285D8; Mon, 10 May 2004 17:03:43 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 189A214426; Mon, 10 May 2004 17:03:03 +0200 (MET DST)
Message-ID: <409F9923.7060702@dif.um.es>
Date: Mon, 10 May 2004 17:00:51 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Subject: Re: [Pana] host route
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
In-Reply-To: <20040510142147.GC1742@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
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=AWL 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 Yoshihiro...
Yoshihiro Ohba wrote:

>On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
>  
>
>>As we have more than one update now, it might make sense to provide a separate
>>mechanism instead of over-loading the reauth.
>>
>>There is a difference between device-ID update and POPA update. There is not
>>much incentive for the PaC to update with a device-ID that belongs to someone else.
>>But PaC can always update the PAA with invalid POPAs consuming host routes.
>>There is really no redirection attack as the route is not used until the packets are
>>sent that would use the route. So, the only possibility is to generate invalid host
>>routes. How can PAA check to make sure that this is not happening ? 
>>    
>>
>
>I think the only way for PAA to check this is, as PANA is doing for
>Device-Id checking, to compare the POPA aganst the source IP address
>of the IP packet that carries the POPA in a PANA payload.  This
>checking does not work if the PaC uses someone else's address for both
>the POPA and the source IP address of the IP packet.  However, this
>would not harm
>

> IF (i) the PAA does not allow the POPA update when the
>POPA is already associated with someone else and (ii) the PAA does not
>allow multiple host route entries per PaC.
>  
>
Must both conditions be honored? Because I think Mohan exposes invalid
POPAs and those could not belong to someone else...

>  
>
>>Can the same
>>happen with device-ID update consuming some other resource ? 
>>    
>>
>
>I think so.  However, this would not harm as described above.
>
>  
>
>>The framework
>>document is still not clear on what happens during a device-Id update.
>>    
>>
>
>I think describing something on a device-id and POPA update in PANA
>specification should be sufficient.
>
>Yoshihiro Ohba
>
>
>  
>
>>-mohan
>>
>>
>>-mohan
>>
>>
>>    
>>
>>>Yoshihiro Ohba
>>>
>>>
>>>
>>>      
>>>
>>>>        
>>>>
>>>>>Which is better or any other ways?
>>>>>
>>>>>          
>>>>>
>>>> > Yoshihiro Ohba
>>>>        
>>>>
>>>>-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
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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


From exim@www1.ietf.org  Mon May 10 11:46:16 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12132
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 11:46:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNChu-0004UX-Sj
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 11:28:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFSg3L017266
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 11:28:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCgC-0003w2-4m
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 11:26:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11088
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 11:26:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNCgB-0003a3-6a
	for pana-web-archive@ietf.org; Mon, 10 May 2004 11:26:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCf9-0003F6-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 11:25:52 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCeU-0002va-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 11:25:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCTk-0001NV-VS; Mon, 10 May 2004 11:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCLw-0007ni-1Z
	for pana@optimus.ietf.org; Mon, 10 May 2004 11:06:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09922
	for <pana@ietf.org>; Mon, 10 May 2004 11:05:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNCLt-000462-CE
	for pana@ietf.org; Mon, 10 May 2004 11:05:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCL2-0003li-00
	for pana@ietf.org; Mon, 10 May 2004 11:05:04 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCKE-0003J8-00
	for pana@ietf.org; Mon, 10 May 2004 11:04:15 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 7EA14285F5; Mon, 10 May 2004 17:03:43 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 64759285D8; Mon, 10 May 2004 17:03:43 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 189A214426; Mon, 10 May 2004 17:03:03 +0200 (MET DST)
Message-ID: <409F9923.7060702@dif.um.es>
Date: Mon, 10 May 2004 17:00:51 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Subject: Re: [Pana] host route
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
In-Reply-To: <20040510142147.GC1742@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshihiro...
Yoshihiro Ohba wrote:

>On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
>  
>
>>As we have more than one update now, it might make sense to provide a separate
>>mechanism instead of over-loading the reauth.
>>
>>There is a difference between device-ID update and POPA update. There is not
>>much incentive for the PaC to update with a device-ID that belongs to someone else.
>>But PaC can always update the PAA with invalid POPAs consuming host routes.
>>There is really no redirection attack as the route is not used until the packets are
>>sent that would use the route. So, the only possibility is to generate invalid host
>>routes. How can PAA check to make sure that this is not happening ? 
>>    
>>
>
>I think the only way for PAA to check this is, as PANA is doing for
>Device-Id checking, to compare the POPA aganst the source IP address
>of the IP packet that carries the POPA in a PANA payload.  This
>checking does not work if the PaC uses someone else's address for both
>the POPA and the source IP address of the IP packet.  However, this
>would not harm
>

> IF (i) the PAA does not allow the POPA update when the
>POPA is already associated with someone else and (ii) the PAA does not
>allow multiple host route entries per PaC.
>  
>
Must both conditions be honored? Because I think Mohan exposes invalid
POPAs and those could not belong to someone else...

>  
>
>>Can the same
>>happen with device-ID update consuming some other resource ? 
>>    
>>
>
>I think so.  However, this would not harm as described above.
>
>  
>
>>The framework
>>document is still not clear on what happens during a device-Id update.
>>    
>>
>
>I think describing something on a device-id and POPA update in PANA
>specification should be sufficient.
>
>Yoshihiro Ohba
>
>
>  
>
>>-mohan
>>
>>
>>-mohan
>>
>>
>>    
>>
>>>Yoshihiro Ohba
>>>
>>>
>>>
>>>      
>>>
>>>>        
>>>>
>>>>>Which is better or any other ways?
>>>>>
>>>>>          
>>>>>
>>>> > Yoshihiro Ohba
>>>>        
>>>>
>>>>-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
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From pana-admin@ietf.org  Mon May 10 12:32:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15298
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 12:32:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDXm-00086M-2n; Mon, 10 May 2004 12:22:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDJ8-0003nu-7R
	for pana@optimus.ietf.org; Mon, 10 May 2004 12:07:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13718
	for <pana@ietf.org>; Mon, 10 May 2004 12:07:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNDJ6-0001bd-QN
	for pana@ietf.org; Mon, 10 May 2004 12:07:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDHz-0001BQ-00
	for pana@ietf.org; Mon, 10 May 2004 12:06:00 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNDGX-0000Qg-00
	for pana@ietf.org; Mon, 10 May 2004 12:04:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNDGS-0006sD-Re
	for pana@ietf.org; Mon, 10 May 2004 12:04:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AG3wgH025354;
	Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AG3wOq011384;
	Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA11383 ; Tue, 11 May 2004 01:03:58 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA12663; Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA22626; Tue, 11 May 2004 01:03:57 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AG3uEU007951;
	Tue, 11 May 2004 01:03:56 +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 <0HXI003UA9YHBN@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 01:03:56 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNDGu-0001A9-00; Mon, 10 May 2004 09:04:52 -0700
Date: Mon, 10 May 2004 09:04:51 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <409F9923.7060702@dif.um.es>
To: Rafael Marin Lopez <rafa@dif.um.es>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>,
        Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Message-id: <20040510160451.GF1742@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Rafael Marin Lopez <rafa@dif.um.es>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>,
 Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <409F9923.7060702@dif.um.es>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Rafa,

On Mon, May 10, 2004 at 05:00:51PM +0200, Rafael Marin Lopez wrote:
> Hi Yoshihiro...
> Yoshihiro Ohba wrote:
> 
> >On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> >  
> >
> >>As we have more than one update now, it might make sense to provide a separate
> >>mechanism instead of over-loading the reauth.
> >>
> >>There is a difference between device-ID update and POPA update. There is not
> >>much incentive for the PaC to update with a device-ID that belongs to someone else.
> >>But PaC can always update the PAA with invalid POPAs consuming host routes.
> >>There is really no redirection attack as the route is not used until the packets are
> >>sent that would use the route. So, the only possibility is to generate invalid host
> >>routes. How can PAA check to make sure that this is not happening ? 
> >>    
> >>
> >
> >I think the only way for PAA to check this is, as PANA is doing for
> >Device-Id checking, to compare the POPA aganst the source IP address
> >of the IP packet that carries the POPA in a PANA payload.  This
> >checking does not work if the PaC uses someone else's address for both
> >the POPA and the source IP address of the IP packet.  However, this
> >would not harm
> >
> 
> > IF (i) the PAA does not allow the POPA update when the
> >POPA is already associated with someone else and (ii) the PAA does not
> >allow multiple host route entries per PaC.
> >  
> >
> Must both conditions be honored? Because I think Mohan exposes invalid
> POPAs and those could not belong to someone else...

Condition (ii) is needed to avoid consuming host routes.

Condition (i) is needed to avoid redirection attack for PANA messages.
As Mohan mentioned, this redirection would not occur until a (PANA)
message is sent from the PAA, but it might be better to avoid such a
redirection attack in the PANA protocol.

Yoshihiro Ohba



> 
> >  
> >
> >>Can the same
> >>happen with device-ID update consuming some other resource ? 
> >>    
> >>
> >
> >I think so.  However, this would not harm as described above.
> >
> >  
> >
> >>The framework
> >>document is still not clear on what happens during a device-Id update.
> >>    
> >>
> >
> >I think describing something on a device-id and POPA update in PANA
> >specification should be sufficient.
> >
> >Yoshihiro Ohba
> >
> >
> >  
> >
> >>-mohan
> >>
> >>
> >>-mohan
> >>
> >>
> >>    
> >>
> >>>Yoshihiro Ohba
> >>>
> >>>
> >>>
> >>>      
> >>>
> >>>>        
> >>>>
> >>>>>Which is better or any other ways?
> >>>>>
> >>>>>          
> >>>>>
> >>>> > Yoshihiro Ohba
> >>>>        
> >>>>
> >>>>-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
> >
> >
> >  
> >
> 
> 
> -- 
> ------------------------------------------------------
> Rafael Marin Lopez
> Faculty of Computer Science-University of Murcia
> 30071 Murcia - Spain
> Telf: +34968367645    e-mail: rafa@dif.um.es
> ------------------------------------------------------
> 

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


From exim@www1.ietf.org  Mon May 10 12:50:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16601
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 12:50:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDmO-0001zp-KY
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 12:37:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AGbOZj007668
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 12:37:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDjR-0001Ky-5y
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 12:34:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15431
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 12:34:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNDjP-0003Wy-L4
	for pana-web-archive@ietf.org; Mon, 10 May 2004 12:34:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDiI-00038e-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 12:33:10 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNDhS-0002lJ-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 12:32:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDXm-00086M-2n; Mon, 10 May 2004 12:22:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDJ8-0003nu-7R
	for pana@optimus.ietf.org; Mon, 10 May 2004 12:07:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13718
	for <pana@ietf.org>; Mon, 10 May 2004 12:07:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNDJ6-0001bd-QN
	for pana@ietf.org; Mon, 10 May 2004 12:07:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDHz-0001BQ-00
	for pana@ietf.org; Mon, 10 May 2004 12:06:00 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNDGX-0000Qg-00
	for pana@ietf.org; Mon, 10 May 2004 12:04:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNDGS-0006sD-Re
	for pana@ietf.org; Mon, 10 May 2004 12:04:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AG3wgH025354;
	Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AG3wOq011384;
	Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA11383 ; Tue, 11 May 2004 01:03:58 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA12663; Tue, 11 May 2004 01:03:58 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA22626; Tue, 11 May 2004 01:03:57 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AG3uEU007951;
	Tue, 11 May 2004 01:03:56 +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 <0HXI003UA9YHBN@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 01:03:56 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNDGu-0001A9-00; Mon, 10 May 2004 09:04:52 -0700
Date: Mon, 10 May 2004 09:04:51 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <409F9923.7060702@dif.um.es>
To: Rafael Marin Lopez <rafa@dif.um.es>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>,
        Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Message-id: <20040510160451.GF1742@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Rafael Marin Lopez <rafa@dif.um.es>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>,
 Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <409F9923.7060702@dif.um.es>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60

Hi Rafa,

On Mon, May 10, 2004 at 05:00:51PM +0200, Rafael Marin Lopez wrote:
> Hi Yoshihiro...
> Yoshihiro Ohba wrote:
> 
> >On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> >  
> >
> >>As we have more than one update now, it might make sense to provide a separate
> >>mechanism instead of over-loading the reauth.
> >>
> >>There is a difference between device-ID update and POPA update. There is not
> >>much incentive for the PaC to update with a device-ID that belongs to someone else.
> >>But PaC can always update the PAA with invalid POPAs consuming host routes.
> >>There is really no redirection attack as the route is not used until the packets are
> >>sent that would use the route. So, the only possibility is to generate invalid host
> >>routes. How can PAA check to make sure that this is not happening ? 
> >>    
> >>
> >
> >I think the only way for PAA to check this is, as PANA is doing for
> >Device-Id checking, to compare the POPA aganst the source IP address
> >of the IP packet that carries the POPA in a PANA payload.  This
> >checking does not work if the PaC uses someone else's address for both
> >the POPA and the source IP address of the IP packet.  However, this
> >would not harm
> >
> 
> > IF (i) the PAA does not allow the POPA update when the
> >POPA is already associated with someone else and (ii) the PAA does not
> >allow multiple host route entries per PaC.
> >  
> >
> Must both conditions be honored? Because I think Mohan exposes invalid
> POPAs and those could not belong to someone else...

Condition (ii) is needed to avoid consuming host routes.

Condition (i) is needed to avoid redirection attack for PANA messages.
As Mohan mentioned, this redirection would not occur until a (PANA)
message is sent from the PAA, but it might be better to avoid such a
redirection attack in the PANA protocol.

Yoshihiro Ohba



> 
> >  
> >
> >>Can the same
> >>happen with device-ID update consuming some other resource ? 
> >>    
> >>
> >
> >I think so.  However, this would not harm as described above.
> >
> >  
> >
> >>The framework
> >>document is still not clear on what happens during a device-Id update.
> >>    
> >>
> >
> >I think describing something on a device-id and POPA update in PANA
> >specification should be sufficient.
> >
> >Yoshihiro Ohba
> >
> >
> >  
> >
> >>-mohan
> >>
> >>
> >>-mohan
> >>
> >>
> >>    
> >>
> >>>Yoshihiro Ohba
> >>>
> >>>
> >>>
> >>>      
> >>>
> >>>>        
> >>>>
> >>>>>Which is better or any other ways?
> >>>>>
> >>>>>          
> >>>>>
> >>>> > Yoshihiro Ohba
> >>>>        
> >>>>
> >>>>-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
> >
> >
> >  
> >
> 
> 
> -- 
> ------------------------------------------------------
> Rafael Marin Lopez
> Faculty of Computer Science-University of Murcia
> 30071 Murcia - Spain
> Telf: +34968367645    e-mail: rafa@dif.um.es
> ------------------------------------------------------
> 

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



From pana-admin@ietf.org  Mon May 10 18:00:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09331
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 18:00:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIc2-0004F9-OU; Mon, 10 May 2004 17:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIUY-000216-M7
	for pana@optimus.ietf.org; Mon, 10 May 2004 17:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08298
	for <pana@ietf.org>; Mon, 10 May 2004 17:39:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNIUW-00020L-7G
	for pana@ietf.org; Mon, 10 May 2004 17:39:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNITX-0001fN-00
	for pana@ietf.org; Mon, 10 May 2004 17:38:15 -0400
Received: from smtp802.mail.sc5.yahoo.com ([66.163.168.181])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNITC-0001Kk-00
	for pana@ietf.org; Mon, 10 May 2004 17:37:54 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp802.mail.sc5.yahoo.com with SMTP; 10 May 2004 21:37:54 -0000
Message-ID: <00c201c436d7$0e778940$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
Subject: Re: [Pana] host route
Date: Mon, 10 May 2004 14:37:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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 Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > 
> > As we have more than one update now, it might make sense to provide a separate
> > mechanism instead of over-loading the reauth.
> > 
> > There is a difference between device-ID update and POPA update. There is not
> > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > There is really no redirection attack as the route is not used until the packets are
> > sent that would use the route. So, the only possibility is to generate invalid host
> > routes. How can PAA check to make sure that this is not happening ? 
> 
> I think the only way for PAA to check this is, as PANA is doing for
> Device-Id checking, to compare the POPA aganst the source IP address
> of the IP packet that carries the POPA in a PANA payload.  This
> checking does not work if the PaC uses someone else's address for both
> the POPA and the source IP address of the IP packet.  However, this
> would not harm IF (i) the PAA does not allow the POPA update when the
> POPA is already associated with someone else and (ii) the PAA does not
> allow multiple host route entries per PaC.
> 
I think so. Are you ssuming that POPA never changes during the lifetime ? Otherwise,
there has to be state about when PaC can update its POPA/POPA has already
been updated by PaC etc. Also, how is the PaC identified (to check whether
a given PaC can update only once or not) ?

My usage of redirection attack in my previous mail is not right.  PAA needs
to have a "host" route for sending packets to PaC. Even if a wrong entry
is setup, it does not redirect traffic from one address to another address.
The only harm is the consumption of memory. Even if a malicious PaC1
sets up an entry for a different PaC2 before that PaC is seen on the network,
it does not cause any problems. When PaC2 authenticates, the route will
already be there.


> > Can the same
> > happen with device-ID update consuming some other resource ? 
> 
> I think so.  However, this would not harm as described above.
>
> 
> > The framework
> > document is still not clear on what happens during a device-Id update.
> 
> I think describing something on a device-id and POPA update in PANA
> specification should be sufficient.
> 
Ok.

-mohan

> Yoshihiro Ohba
> 
> 
> > 
> > -mohan
> > 
> > 
> > -mohan
> > 
> > 
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > 
> > > > 
> > > > 
> > > > > Which is better or any other ways?
> > > > > 
> > > >  > Yoshihiro Ohba
> > > > > 
> > > > 
> > > > -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  Mon May 10 18:22:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12022
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 18:22:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIye-0004ks-TP
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 18:10:25 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AMAOY9018275
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 18:10:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIqi-00008n-QC
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 18:02:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09473
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 18:02:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNIqg-0002BD-5v
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:02:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNIpk-0001qq-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:01:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNIoy-0001W2-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:00:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIc2-0004F9-OU; Mon, 10 May 2004 17:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIUY-000216-M7
	for pana@optimus.ietf.org; Mon, 10 May 2004 17:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08298
	for <pana@ietf.org>; Mon, 10 May 2004 17:39:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNIUW-00020L-7G
	for pana@ietf.org; Mon, 10 May 2004 17:39:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNITX-0001fN-00
	for pana@ietf.org; Mon, 10 May 2004 17:38:15 -0400
Received: from smtp802.mail.sc5.yahoo.com ([66.163.168.181])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNITC-0001Kk-00
	for pana@ietf.org; Mon, 10 May 2004 17:37:54 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp802.mail.sc5.yahoo.com with SMTP; 10 May 2004 21:37:54 -0000
Message-ID: <00c201c436d7$0e778940$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
Subject: Re: [Pana] host route
Date: Mon, 10 May 2004 14:37:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 

> On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > 
> > As we have more than one update now, it might make sense to provide a separate
> > mechanism instead of over-loading the reauth.
> > 
> > There is a difference between device-ID update and POPA update. There is not
> > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > There is really no redirection attack as the route is not used until the packets are
> > sent that would use the route. So, the only possibility is to generate invalid host
> > routes. How can PAA check to make sure that this is not happening ? 
> 
> I think the only way for PAA to check this is, as PANA is doing for
> Device-Id checking, to compare the POPA aganst the source IP address
> of the IP packet that carries the POPA in a PANA payload.  This
> checking does not work if the PaC uses someone else's address for both
> the POPA and the source IP address of the IP packet.  However, this
> would not harm IF (i) the PAA does not allow the POPA update when the
> POPA is already associated with someone else and (ii) the PAA does not
> allow multiple host route entries per PaC.
> 
I think so. Are you ssuming that POPA never changes during the lifetime ? Otherwise,
there has to be state about when PaC can update its POPA/POPA has already
been updated by PaC etc. Also, how is the PaC identified (to check whether
a given PaC can update only once or not) ?

My usage of redirection attack in my previous mail is not right.  PAA needs
to have a "host" route for sending packets to PaC. Even if a wrong entry
is setup, it does not redirect traffic from one address to another address.
The only harm is the consumption of memory. Even if a malicious PaC1
sets up an entry for a different PaC2 before that PaC is seen on the network,
it does not cause any problems. When PaC2 authenticates, the route will
already be there.


> > Can the same
> > happen with device-ID update consuming some other resource ? 
> 
> I think so.  However, this would not harm as described above.
>
> 
> > The framework
> > document is still not clear on what happens during a device-Id update.
> 
> I think describing something on a device-id and POPA update in PANA
> specification should be sufficient.
> 
Ok.

-mohan

> Yoshihiro Ohba
> 
> 
> > 
> > -mohan
> > 
> > 
> > -mohan
> > 
> > 
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > 
> > > > 
> > > > 
> > > > > Which is better or any other ways?
> > > > > 
> > > >  > Yoshihiro Ohba
> > > > > 
> > > > 
> > > > -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  Mon May 10 18:31:13 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12504
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 18:31:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJAr-0002nM-JB; Mon, 10 May 2004 18:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIwi-0003dp-G9
	for pana@optimus.ietf.org; Mon, 10 May 2004 18:08:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10553
	for <pana@ietf.org>; Mon, 10 May 2004 18:08:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNIwf-0004VU-K8
	for pana@ietf.org; Mon, 10 May 2004 18:08:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNIve-00047a-00
	for pana@ietf.org; Mon, 10 May 2004 18:07:19 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNIuy-0003kU-00
	for pana@ietf.org; Mon, 10 May 2004 18:06:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AM6YgH008706;
	Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AM6YuO024543;
	Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA24540 ; Tue, 11 May 2004 07:06:34 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA06237; Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA15449; Tue, 11 May 2004 07:06:33 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AM6XEU012982;
	Tue, 11 May 2004 07:06:33 +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 <0HXI00C5SQQTWW@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 07:06:32 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNIvE-0002Pv-00; Mon, 10 May 2004 15:06:52 -0700
Date: Mon, 10 May 2004 15:06:52 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <00c201c436d7$0e778940$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040510220652.GN1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <00c201c436d7$0e778940$861167c0@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.1 required=5.0 tests=AWL 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 Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > 
> > > As we have more than one update now, it might make sense to provide a separate
> > > mechanism instead of over-loading the reauth.
> > > 
> > > There is a difference between device-ID update and POPA update. There is not
> > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > There is really no redirection attack as the route is not used until the packets are
> > > sent that would use the route. So, the only possibility is to generate invalid host
> > > routes. How can PAA check to make sure that this is not happening ? 
> > 
> > I think the only way for PAA to check this is, as PANA is doing for
> > Device-Id checking, to compare the POPA aganst the source IP address
> > of the IP packet that carries the POPA in a PANA payload.  This
> > checking does not work if the PaC uses someone else's address for both
> > the POPA and the source IP address of the IP packet.  However, this
> > would not harm IF (i) the PAA does not allow the POPA update when the
> > POPA is already associated with someone else and (ii) the PAA does not
> > allow multiple host route entries per PaC.
> > 
> I think so. Are you ssuming that POPA never changes during the lifetime ? 

POPA may change if DHCP assigns a new address when the lease period 
of the current address expires.  So I don't think we should assume 
that POPA never changes during the lifetime.

> Otherwise,
> there has to be state about when PaC can update its POPA/POPA has already
> been updated by PaC etc. Also, how is the PaC identified (to check whether
> a given PaC can update only once or not) ?

I think the state could be maintained outside the PANA protocol, e.g.,
by consulting the DHCP server about the state through SNMP, if needed.

Yoshihiro Ohba

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


From exim@www1.ietf.org  Mon May 10 18:55:06 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14478
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 18:55:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJST-0007Bh-QB
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 18:41:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AMfD1p027629
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 18:41:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJK9-0004ec-Kz
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 18:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12607
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 18:32:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNJK6-00058n-MZ
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:32:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNJIz-0004mC-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:31:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNJIL-0004QM-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 18:30:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJAr-0002nM-JB; Mon, 10 May 2004 18:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNIwi-0003dp-G9
	for pana@optimus.ietf.org; Mon, 10 May 2004 18:08:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10553
	for <pana@ietf.org>; Mon, 10 May 2004 18:08:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNIwf-0004VU-K8
	for pana@ietf.org; Mon, 10 May 2004 18:08:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNIve-00047a-00
	for pana@ietf.org; Mon, 10 May 2004 18:07:19 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNIuy-0003kU-00
	for pana@ietf.org; Mon, 10 May 2004 18:06:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4AM6YgH008706;
	Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4AM6YuO024543;
	Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA24540 ; Tue, 11 May 2004 07:06:34 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA06237; Tue, 11 May 2004 07:06:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA15449; Tue, 11 May 2004 07:06:33 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4AM6XEU012982;
	Tue, 11 May 2004 07:06:33 +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 <0HXI00C5SQQTWW@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 07:06:32 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNIvE-0002Pv-00; Mon, 10 May 2004 15:06:52 -0700
Date: Mon, 10 May 2004 15:06:52 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <00c201c436d7$0e778940$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040510220652.GN1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <00c201c436d7$0e778940$861167c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > 
> > > As we have more than one update now, it might make sense to provide a separate
> > > mechanism instead of over-loading the reauth.
> > > 
> > > There is a difference between device-ID update and POPA update. There is not
> > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > There is really no redirection attack as the route is not used until the packets are
> > > sent that would use the route. So, the only possibility is to generate invalid host
> > > routes. How can PAA check to make sure that this is not happening ? 
> > 
> > I think the only way for PAA to check this is, as PANA is doing for
> > Device-Id checking, to compare the POPA aganst the source IP address
> > of the IP packet that carries the POPA in a PANA payload.  This
> > checking does not work if the PaC uses someone else's address for both
> > the POPA and the source IP address of the IP packet.  However, this
> > would not harm IF (i) the PAA does not allow the POPA update when the
> > POPA is already associated with someone else and (ii) the PAA does not
> > allow multiple host route entries per PaC.
> > 
> I think so. Are you ssuming that POPA never changes during the lifetime ? 

POPA may change if DHCP assigns a new address when the lease period 
of the current address expires.  So I don't think we should assume 
that POPA never changes during the lifetime.

> Otherwise,
> there has to be state about when PaC can update its POPA/POPA has already
> been updated by PaC etc. Also, how is the PaC identified (to check whether
> a given PaC can update only once or not) ?

I think the state could be maintained outside the PANA protocol, e.g.,
by consulting the DHCP server about the state through SNMP, if needed.

Yoshihiro Ohba

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



From pana-admin@ietf.org  Mon May 10 19:24:29 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16063
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 19:24:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJvJ-0005GD-KG; Mon, 10 May 2004 19:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJsn-0004d6-El
	for pana@optimus.ietf.org; Mon, 10 May 2004 19:08:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15349
	for <pana@ietf.org>; Mon, 10 May 2004 19:08:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNJsk-0002fm-5B
	for pana@ietf.org; Mon, 10 May 2004 19:08:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNJrb-0002Is-00
	for pana@ietf.org; Mon, 10 May 2004 19:07:11 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNJqZ-0001tI-00
	for pana@ietf.org; Mon, 10 May 2004 19:06:07 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 10 May 2004 23:03:07 -0000
Message-ID: <013401c436e2$f5c2ce30$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead> <00c201c436d7$0e778940$861167c0@adithya> <20040510220652.GN1742@steelhead>
Subject: Re: [Pana] host route
Date: Mon, 10 May 2004 16:03:08 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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 Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
> >  
> > 
> > > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > > 
> > > > As we have more than one update now, it might make sense to provide a separate
> > > > mechanism instead of over-loading the reauth.
> > > > 
> > > > There is a difference between device-ID update and POPA update. There is not
> > > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > > There is really no redirection attack as the route is not used until the packets are
> > > > sent that would use the route. So, the only possibility is to generate invalid host
> > > > routes. How can PAA check to make sure that this is not happening ? 
> > > 
> > > I think the only way for PAA to check this is, as PANA is doing for
> > > Device-Id checking, to compare the POPA aganst the source IP address
> > > of the IP packet that carries the POPA in a PANA payload.  This
> > > checking does not work if the PaC uses someone else's address for both
> > > the POPA and the source IP address of the IP packet.  However, this
> > > would not harm IF (i) the PAA does not allow the POPA update when the
> > > POPA is already associated with someone else and (ii) the PAA does not
> > > allow multiple host route entries per PaC.
> > > 
> > I think so. Are you ssuming that POPA never changes during the lifetime ? 
> 
> POPA may change if DHCP assigns a new address when the lease period 
> of the current address expires.  So I don't think we should assume 
> that POPA never changes during the lifetime.
> 
> > Otherwise,
> > there has to be state about when PaC can update its POPA/POPA has already
> > been updated by PaC etc. Also, how is the PaC identified (to check whether
> > a given PaC can update only once or not) ?
> 
> I think the state could be maintained outside the PANA protocol, e.g.,
> by consulting the DHCP server about the state through SNMP, if needed.
> 
So, whenever you get a POPA update, you query the external DHCP server to see
whether this "PaC", can use this address or not ? It can be a third POPA update,
but it is okay as long as it is valid for the "PaC". Now, how do you identify this
PaC to the DHCP server ? I think the "client identifier" could be different when used
with DHCP Vs PANA. 

-mohan

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

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


From exim@www1.ietf.org  Mon May 10 19:43:16 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16735
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 19:43:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNKIo-0001bB-Nw
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 19:35:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ANZIlM006143
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 19:35:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNK9x-00089D-VW
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 19:26:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16114
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 19:26:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNK9w-00017H-D5
	for pana-web-archive@ietf.org; Mon, 10 May 2004 19:26:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNK8x-0000md-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 19:25:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNK7s-0000CE-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 19:24:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJvJ-0005GD-KG; Mon, 10 May 2004 19:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJsn-0004d6-El
	for pana@optimus.ietf.org; Mon, 10 May 2004 19:08:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15349
	for <pana@ietf.org>; Mon, 10 May 2004 19:08:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNJsk-0002fm-5B
	for pana@ietf.org; Mon, 10 May 2004 19:08:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNJrb-0002Is-00
	for pana@ietf.org; Mon, 10 May 2004 19:07:11 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNJqZ-0001tI-00
	for pana@ietf.org; Mon, 10 May 2004 19:06:07 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 10 May 2004 23:03:07 -0000
Message-ID: <013401c436e2$f5c2ce30$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040506135929.GH23909@steelhead> <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead> <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead> <00c201c436d7$0e778940$861167c0@adithya> <20040510220652.GN1742@steelhead>
Subject: Re: [Pana] host route
Date: Mon, 10 May 2004 16:03:08 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 
> On Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
> >  
> > 
> > > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > > 
> > > > As we have more than one update now, it might make sense to provide a separate
> > > > mechanism instead of over-loading the reauth.
> > > > 
> > > > There is a difference between device-ID update and POPA update. There is not
> > > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > > There is really no redirection attack as the route is not used until the packets are
> > > > sent that would use the route. So, the only possibility is to generate invalid host
> > > > routes. How can PAA check to make sure that this is not happening ? 
> > > 
> > > I think the only way for PAA to check this is, as PANA is doing for
> > > Device-Id checking, to compare the POPA aganst the source IP address
> > > of the IP packet that carries the POPA in a PANA payload.  This
> > > checking does not work if the PaC uses someone else's address for both
> > > the POPA and the source IP address of the IP packet.  However, this
> > > would not harm IF (i) the PAA does not allow the POPA update when the
> > > POPA is already associated with someone else and (ii) the PAA does not
> > > allow multiple host route entries per PaC.
> > > 
> > I think so. Are you ssuming that POPA never changes during the lifetime ? 
> 
> POPA may change if DHCP assigns a new address when the lease period 
> of the current address expires.  So I don't think we should assume 
> that POPA never changes during the lifetime.
> 
> > Otherwise,
> > there has to be state about when PaC can update its POPA/POPA has already
> > been updated by PaC etc. Also, how is the PaC identified (to check whether
> > a given PaC can update only once or not) ?
> 
> I think the state could be maintained outside the PANA protocol, e.g.,
> by consulting the DHCP server about the state through SNMP, if needed.
> 
So, whenever you get a POPA update, you query the external DHCP server to see
whether this "PaC", can use this address or not ? It can be a third POPA update,
but it is okay as long as it is valid for the "PaC". Now, how do you identify this
PaC to the DHCP server ? I think the "client identifier" could be different when used
with DHCP Vs PANA. 

-mohan

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

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



From pana-admin@ietf.org  Mon May 10 22:11:52 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23578
	for <pana-archive@lists.ietf.org>; Mon, 10 May 2004 22:11:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMbl-00062j-9j; Mon, 10 May 2004 22:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMUK-0004sf-Ro
	for pana@optimus.ietf.org; Mon, 10 May 2004 21:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22063
	for <pana@ietf.org>; Mon, 10 May 2004 21:55:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMUI-0004WW-0b
	for pana@ietf.org; Mon, 10 May 2004 21:55:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMTI-0004BM-00
	for pana@ietf.org; Mon, 10 May 2004 21:54:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMSL-0003qQ-00
	for pana@ietf.org; Mon, 10 May 2004 21:53:17 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4B1rGgH012597;
	Tue, 11 May 2004 10:53:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4B1rFVp027102;
	Tue, 11 May 2004 10:53:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id LAA27094 ; Tue, 11 May 2004 10:53:15 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA23567; Tue, 11 May 2004 10:53:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA28575; Tue, 11 May 2004 10:53:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4B1rAEU018859;
	Tue, 11 May 2004 10:53:10 +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 <0HXJ007A618J1C@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 10:53:09 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNMSW-00038U-00; Mon, 10 May 2004 18:53:28 -0700
Date: Mon, 10 May 2004 18:53:28 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <013401c436e2$f5c2ce30$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040511015328.GQ1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <00c201c436d7$0e778940$861167c0@adithya> <20040510220652.GN1742@steelhead>
 <013401c436e2$f5c2ce30$861167c0@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.1 required=5.0 tests=AWL 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 Mon, May 10, 2004 at 04:03:08PM -0700, Mohan Parthasarathy wrote:
>  
> > On Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
> > >  
> > > 
> > > > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > > > 
> > > > > As we have more than one update now, it might make sense to provide a separate
> > > > > mechanism instead of over-loading the reauth.
> > > > > 
> > > > > There is a difference between device-ID update and POPA update. There is not
> > > > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > > > There is really no redirection attack as the route is not used until the packets are
> > > > > sent that would use the route. So, the only possibility is to generate invalid host
> > > > > routes. How can PAA check to make sure that this is not happening ? 
> > > > 
> > > > I think the only way for PAA to check this is, as PANA is doing for
> > > > Device-Id checking, to compare the POPA aganst the source IP address
> > > > of the IP packet that carries the POPA in a PANA payload.  This
> > > > checking does not work if the PaC uses someone else's address for both
> > > > the POPA and the source IP address of the IP packet.  However, this
> > > > would not harm IF (i) the PAA does not allow the POPA update when the
> > > > POPA is already associated with someone else and (ii) the PAA does not
> > > > allow multiple host route entries per PaC.
> > > > 
> > > I think so. Are you ssuming that POPA never changes during the lifetime ? 
> > 
> > POPA may change if DHCP assigns a new address when the lease period 
> > of the current address expires.  So I don't think we should assume 
> > that POPA never changes during the lifetime.
> > 
> > > Otherwise,
> > > there has to be state about when PaC can update its POPA/POPA has already
> > > been updated by PaC etc. Also, how is the PaC identified (to check whether
> > > a given PaC can update only once or not) ?
> > 
> > I think the state could be maintained outside the PANA protocol, e.g.,
> > by consulting the DHCP server about the state through SNMP, if needed.
> > 
> So, whenever you get a POPA update, you query the external DHCP server to see
> whether this "PaC", can use this address or not ? It can be a third POPA update,
> but it is okay as long as it is valid for the "PaC". Now, how do you identify this
> PaC to the DHCP server ? I think the "client identifier" could be different when used
> with DHCP Vs PANA. 

I think we could use client hardware address carried in DHCP message
for this purpose, instead of relying on DHCP client identifier.

Yoshihiro Ohba


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


From exim@www1.ietf.org  Mon May 10 22:18:52 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24134
	for <pana-archive@odin.ietf.org>; Mon, 10 May 2004 22:18:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMot-00013q-Jb
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 22:16:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B2GZ3g004073
	for pana-archive@odin.ietf.org; Mon, 10 May 2004 22:16:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMls-0000Sz-Lk
	for pana-web-archive@optimus.ietf.org; Mon, 10 May 2004 22:13:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23672
	for <pana-web-archive@ietf.org>; Mon, 10 May 2004 22:13:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMlp-0003Ul-KD
	for pana-web-archive@ietf.org; Mon, 10 May 2004 22:13:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMkp-00039F-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 22:12:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMjr-0002ns-00
	for pana-web-archive@ietf.org; Mon, 10 May 2004 22:11:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMbl-00062j-9j; Mon, 10 May 2004 22:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMUK-0004sf-Ro
	for pana@optimus.ietf.org; Mon, 10 May 2004 21:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22063
	for <pana@ietf.org>; Mon, 10 May 2004 21:55:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMUI-0004WW-0b
	for pana@ietf.org; Mon, 10 May 2004 21:55:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMTI-0004BM-00
	for pana@ietf.org; Mon, 10 May 2004 21:54:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMSL-0003qQ-00
	for pana@ietf.org; Mon, 10 May 2004 21:53:17 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4B1rGgH012597;
	Tue, 11 May 2004 10:53:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4B1rFVp027102;
	Tue, 11 May 2004 10:53:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id LAA27094 ; Tue, 11 May 2004 10:53:15 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA23567; Tue, 11 May 2004 10:53:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA28575; Tue, 11 May 2004 10:53:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4B1rAEU018859;
	Tue, 11 May 2004 10:53:10 +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 <0HXJ007A618J1C@tsbpo1.po.toshiba.co.jp>; Tue,
 11 May 2004 10:53:09 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BNMSW-00038U-00; Mon, 10 May 2004 18:53:28 -0700
Date: Mon, 10 May 2004 18:53:28 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] host route
In-reply-to: <013401c436e2$f5c2ce30$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040511015328.GQ1742@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.5.1+cvs20040105i
References: <20040506135929.GH23909@steelhead>
 <005a01c4338c$7016ffd0$6401a8c0@adithya> <20040506174136.GN23909@steelhead>
 <001101c43395$c41d8870$6801a8c0@adithya> <20040510142147.GC1742@steelhead>
 <00c201c436d7$0e778940$861167c0@adithya> <20040510220652.GN1742@steelhead>
 <013401c436e2$f5c2ce30$861167c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 10, 2004 at 04:03:08PM -0700, Mohan Parthasarathy wrote:
>  
> > On Mon, May 10, 2004 at 02:37:55PM -0700, Mohan Parthasarathy wrote:
> > >  
> > > 
> > > > On Thu, May 06, 2004 at 11:12:55AM -0700, Mohan Parthasarathy wrote:
> > > > > > 
> > > > > As we have more than one update now, it might make sense to provide a separate
> > > > > mechanism instead of over-loading the reauth.
> > > > > 
> > > > > There is a difference between device-ID update and POPA update. There is not
> > > > > much incentive for the PaC to update with a device-ID that belongs to someone else.
> > > > > But PaC can always update the PAA with invalid POPAs consuming host routes.
> > > > > There is really no redirection attack as the route is not used until the packets are
> > > > > sent that would use the route. So, the only possibility is to generate invalid host
> > > > > routes. How can PAA check to make sure that this is not happening ? 
> > > > 
> > > > I think the only way for PAA to check this is, as PANA is doing for
> > > > Device-Id checking, to compare the POPA aganst the source IP address
> > > > of the IP packet that carries the POPA in a PANA payload.  This
> > > > checking does not work if the PaC uses someone else's address for both
> > > > the POPA and the source IP address of the IP packet.  However, this
> > > > would not harm IF (i) the PAA does not allow the POPA update when the
> > > > POPA is already associated with someone else and (ii) the PAA does not
> > > > allow multiple host route entries per PaC.
> > > > 
> > > I think so. Are you ssuming that POPA never changes during the lifetime ? 
> > 
> > POPA may change if DHCP assigns a new address when the lease period 
> > of the current address expires.  So I don't think we should assume 
> > that POPA never changes during the lifetime.
> > 
> > > Otherwise,
> > > there has to be state about when PaC can update its POPA/POPA has already
> > > been updated by PaC etc. Also, how is the PaC identified (to check whether
> > > a given PaC can update only once or not) ?
> > 
> > I think the state could be maintained outside the PANA protocol, e.g.,
> > by consulting the DHCP server about the state through SNMP, if needed.
> > 
> So, whenever you get a POPA update, you query the external DHCP server to see
> whether this "PaC", can use this address or not ? It can be a third POPA update,
> but it is okay as long as it is valid for the "PaC". Now, how do you identify this
> PaC to the DHCP server ? I think the "client identifier" could be different when used
> with DHCP Vs PANA. 

I think we could use client hardware address carried in DHCP message
for this purpose, instead of relying on DHCP client identifier.

Yoshihiro Ohba


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



From pana-admin@ietf.org  Tue May 11 16:58:05 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24870
	for <pana-archive@lists.ietf.org>; Tue, 11 May 2004 16:58:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNe3x-0007QH-4E; Tue, 11 May 2004 16:41:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNdpN-00024e-RW
	for pana@optimus.ietf.org; Tue, 11 May 2004 16:26:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22758
	for <pana@ietf.org>; Tue, 11 May 2004 16:26:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNdpL-0003Jw-R5
	for pana@ietf.org; Tue, 11 May 2004 16:26:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNdoT-0002sT-00
	for pana@ietf.org; Tue, 11 May 2004 16:25:17 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNdnW-0002Pl-00
	for pana@ietf.org; Tue, 11 May 2004 16:24:18 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 11 May 2004 19:56:52 -0000
Message-ID: <012701c43792$1c9842b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Tue, 11 May 2004 12:56:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Pana] draft-ietf-pana-ipsec-03.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

I did not see the announcement for the latest revision of the pana-ipsec draft. The PANA web
page seems to have the latest revision. The main change is to simplify the address configuration
mechanism. I have also created an Appendix to discuss implementation issues related to some of the
address configuration schemes which has now been removed from the main section.

Issue 66, 67, 68,69,70 are all related to address configuration. The text has been
modified to reflect what is in PANA framework document. So, these issues should
be resolved by now. 

Issue 82 : Should EP be updated with the new PSK when AAA-key changes during reauthentication ?
The answer is "yes" and it has been clarified in the latest revision.

-mohan


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


From exim@www1.ietf.org  Tue May 11 17:31:29 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27279
	for <pana-archive@odin.ietf.org>; Tue, 11 May 2004 17:31:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNePD-0003ub-Ja
	for pana-archive@odin.ietf.org; Tue, 11 May 2004 17:03:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BL3Fja015034
	for pana-archive@odin.ietf.org; Tue, 11 May 2004 17:03:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeLH-0002cN-8w
	for pana-web-archive@optimus.ietf.org; Tue, 11 May 2004 16:59:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24955
	for <pana-web-archive@ietf.org>; Tue, 11 May 2004 16:59:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNeLF-0002Xu-6v
	for pana-web-archive@ietf.org; Tue, 11 May 2004 16:59:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeKN-00029L-00
	for pana-web-archive@ietf.org; Tue, 11 May 2004 16:58:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeJk-0001kR-00
	for pana-web-archive@ietf.org; Tue, 11 May 2004 16:57:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNe3x-0007QH-4E; Tue, 11 May 2004 16:41:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNdpN-00024e-RW
	for pana@optimus.ietf.org; Tue, 11 May 2004 16:26:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22758
	for <pana@ietf.org>; Tue, 11 May 2004 16:26:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNdpL-0003Jw-R5
	for pana@ietf.org; Tue, 11 May 2004 16:26:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNdoT-0002sT-00
	for pana@ietf.org; Tue, 11 May 2004 16:25:17 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNdnW-0002Pl-00
	for pana@ietf.org; Tue, 11 May 2004 16:24:18 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 11 May 2004 19:56:52 -0000
Message-ID: <012701c43792$1c9842b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Tue, 11 May 2004 12:56:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: [Pana] draft-ietf-pana-ipsec-03.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I did not see the announcement for the latest revision of the pana-ipsec draft. The PANA web
page seems to have the latest revision. The main change is to simplify the address configuration
mechanism. I have also created an Appendix to discuss implementation issues related to some of the
address configuration schemes which has now been removed from the main section.

Issue 66, 67, 68,69,70 are all related to address configuration. The text has been
modified to reflect what is in PANA framework document. So, these issues should
be resolved by now. 

Issue 82 : Should EP be updated with the new PSK when AAA-key changes during reauthentication ?
The answer is "yes" and it has been clarified in the latest revision.

-mohan


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



From pana-admin@ietf.org  Wed May 12 11:07:34 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14584
	for <pana-archive@lists.ietf.org>; Wed, 12 May 2004 11:07:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNuFL-0002OD-Gq; Wed, 12 May 2004 09:58:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNu0G-0004eF-DK
	for pana@optimus.ietf.org; Wed, 12 May 2004 09:42:32 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02733;
	Wed, 12 May 2004 09:42:29 -0400 (EDT)
Message-Id: <200405121342.JAA02733@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 12 May 2004 09:42:29 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-04.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Protocol for Carrying Authentication for Network 
			  Access (PANA)
	Author(s)	: D. Forsberg, et al.
	Filename	: draft-ietf-pana-pana-04.txt
	Pages		: 72
	Date		: 2004-5-11
	
This document defines the Protocol for Carrying Authentication for 
Network Access (PANA), a link-layer agnostic transport for 
Extensible Authentication Protocol (EAP) to enable network access 
authentication between clients and access networks. PANA can carry 
any authentication method that can be specified as an EAP method, 
and can be used on any link that can carry IP. PANA covers the 
client-to-network access authentication part of an overall secure 
network access framework, which additionally includes other 
protocols and mechanisms for service provisioning, access control as 
a result of initial authentication, and accounting.

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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


From pana-admin@ietf.org  Wed May 12 11:53:41 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19901
	for <pana-archive@lists.ietf.org>; Wed, 12 May 2004 11:53:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNvPB-0003Z8-3a; Wed, 12 May 2004 11:12:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNuUe-00048K-UE
	for pana@optimus.ietf.org; Wed, 12 May 2004 10:13:56 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06936;
	Wed, 12 May 2004 10:13:53 -0400 (EDT)
Message-Id: <200405121413.KAA06936@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 12 May 2004 10:13:53 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-ipsec-03.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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

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

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Wed May 12 12:29:45 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23470
	for <pana-archive@odin.ietf.org>; Wed, 12 May 2004 12:29:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNwJ0-00051E-12
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 12:10:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CGA1pw019286
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 12:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNvd1-0001Xw-Ud
	for pana-web-archive@optimus.ietf.org; Wed, 12 May 2004 11:26:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16984
	for <pana-web-archive@ietf.org>; Wed, 12 May 2004 11:26:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNvd1-0006pM-5i
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:26:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNvZt-0005ZC-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:23:25 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNvXH-0004Hv-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:20:47 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNvUI-00032q-Ax
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:17:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNuFL-0002OD-Gq; Wed, 12 May 2004 09:58:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNu0G-0004eF-DK
	for pana@optimus.ietf.org; Wed, 12 May 2004 09:42:32 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02733;
	Wed, 12 May 2004 09:42:29 -0400 (EDT)
Message-Id: <200405121342.JAA02733@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 12 May 2004 09:42:29 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-04.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

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

	Title		: Protocol for Carrying Authentication for Network 
			  Access (PANA)
	Author(s)	: D. Forsberg, et al.
	Filename	: draft-ietf-pana-pana-04.txt
	Pages		: 72
	Date		: 2004-5-11
	
This document defines the Protocol for Carrying Authentication for 
Network Access (PANA), a link-layer agnostic transport for 
Extensible Authentication Protocol (EAP) to enable network access 
authentication between clients and access networks. PANA can carry 
any authentication method that can be specified as an EAP method, 
and can be used on any link that can carry IP. PANA covers the 
client-to-network access authentication part of an overall secure 
network access framework, which additionally includes other 
protocols and mechanisms for service provisioning, access control as 
a result of initial authentication, and accounting.

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Wed May 12 12:33:06 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23893
	for <pana-archive@odin.ietf.org>; Wed, 12 May 2004 12:33:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNwTq-0003BE-5m
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 12:21:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CGLEUw012208
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 12:21:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNw8a-0008Pn-1S
	for pana-web-archive@optimus.ietf.org; Wed, 12 May 2004 11:59:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20772
	for <pana-web-archive@ietf.org>; Wed, 12 May 2004 11:59:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNw8W-00057T-7h
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:59:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNw5z-0004Hd-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:56:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNw2n-0002ue-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:53:19 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNw2m-0003oj-46
	for pana-web-archive@ietf.org; Wed, 12 May 2004 11:53:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNvPB-0003Z8-3a; Wed, 12 May 2004 11:12:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNuUe-00048K-UE
	for pana@optimus.ietf.org; Wed, 12 May 2004 10:13:56 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06936;
	Wed, 12 May 2004 10:13:53 -0400 (EDT)
Message-Id: <200405121413.KAA06936@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 12 May 2004 10:13:53 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-ipsec-03.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

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

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

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

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


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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



From pana-admin@ietf.org  Wed May 12 18:21:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15736
	for <pana-archive@lists.ietf.org>; Wed, 12 May 2004 18:21:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO20M-0007pO-9r; Wed, 12 May 2004 18:15:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO1y5-0006DL-Pa
	for pana@optimus.ietf.org; Wed, 12 May 2004 18:12:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15075
	for <pana@ietf.org>; Wed, 12 May 2004 18:12:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO1y2-0000Kt-Pf
	for pana@ietf.org; Wed, 12 May 2004 18:12:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO1xA-0007eR-00
	for pana@ietf.org; Wed, 12 May 2004 18:11:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO1wR-00079y-00
	for pana@ietf.org; Wed, 12 May 2004 18:11:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4CMB6gH005218;
	Thu, 13 May 2004 07:11:06 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4CMB6xx008793;
	Thu, 13 May 2004 07:11:06 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA08790 ; Thu, 13 May 2004 07:11:06 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA28179; Thu, 13 May 2004 07:11:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA21155; Thu, 13 May 2004 07:11:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4CMB4EU004532;
	Thu, 13 May 2004 07:11:04 +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 <0HXM00KRPGADB0@tsbpo1.po.toshiba.co.jp>; Thu,
 13 May 2004 07:11:04 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BO1xB-0000Mx-00; Wed, 12 May 2004 15:11:53 -0700
Date: Wed, 12 May 2004 15:11:53 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040512221153.GI25541@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,FREE_ACCESS autolearn=no 
	version=2.60
Subject: [Pana] [framework] simplying WLAN section
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 have checked the latest version of IEEE 802.11i/D10.0, and I noticed
that higher-layer data traffic that is optionally allowed to be
received and processed on IEEE 802.1X Uncontrolled Ports does not have
to be terminated between stations (including AP).  Specifically, the
following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
from D10.0:

   Informative Note: STAs may optionally receive frames other than
   IEEE 802.1X messages in unprotected data MPDUs destined for the
   IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
   caveat that any protocol utilizing this mechanism should provide
   cryptographic data protection mechanisms, suitable for the intended
   application or usage, within the protocol itself.  These frames are
   never forwarded to or from the DS, but terminate at an application
   level service, such as a captive portal, on the AP.  This usage is
   outside the scope of this standard.

This means that in the PANA framework document, (virtual) AP hopping
operation described in 10.2.2.1 is not needed anymore when AP and PAA
are separated, and thus the same operation that was defined for
co-located AP and PAA is now applicable to the separate AP and PAA
case.


Suggested changes:

[1] Change section 10.2.2 to:

"
10.2.2 PANA with Bootstrapping IEEE 802.11i/WPA

   In this model, PANA is used for authentication and authorization,
   and L2 ciphering is used for access control, the latter is enabled
   by the former.  The L2 ciphering is based on using PSK (Pre-Shared
   Key) mode of WPA (Wi-Fi Protected Access) [WPA] or IEEE 802.11i
   [802.11i], which is derived from the EAP MSK as a result of
   successful PANA authentication.  In this document, the pre-shared
   key shared between station and AP is referred to as PMK (Pair-wise
   Master Key).  In this model, MAC address is used as the device
   identifier in PANA.

   This model allows the separation of PAA from APs (EPs).  A typical
   purpose of using this model is to reduce AP management cost by
   allowing physical separation of RADIUS/Diameter client from access
   points, where AP management can be a significant issue when
   deploying a large number of access points.

   By bootstrapping PSK mode of WPA and IEEE 802.11i from PANA it is
   also possible to improve wireless LAN security by providing protected
   disconnection procedure at L3.

   This model does not require any change in the current WPA and IEEE
   802.11i specifications.  This also means that PANA doesn't provide
   any L2 security features beyond those already provided for in WPA and
   IEEE 802.11i.

   The IEEE 802.11 specification [802.11] allows Class 1 data frames
   to be received in any state.  Also, the latest version of IEEE
   802.11i [802.11i] optionally allows higher-layer data traffic to be
   received and processed on their IEEE 802.1X Uncontrolled Ports.
   This feature allows processing IP-based traffic (such as ARP, IPv6
   neighbor discovery, DHCP, and PANA) on IEEE 802.1X Uncontrolled
   Port prior to client authentication.  (Note: WPA and its
   corresponding version of IEEE 802.11i draft do not explicitly
   define this operation, so it may be safer not to use this in WPA).

   Until the PaC is successfully authenticated, only a selected type
   of IP traffic is allowed over the IEEE 802.1X Uncontrolled Port.
   Any other IP traffic is dropped on the AP without being forwarded
   to the DS (Distribution System).  Upon successful PANA
   authentication, the traffic switches to the controlled port.  Host
   configuration, including obtaining an (potentially new) IP address,
   takes place on this port.  Usual DHCP-based, and also in the case of
   IPv6 stateless autoconfiguration, mechanism is available to the
   PaC.  After this point, the rest of the IP traffic, including PANA
   exchanges, are processed on the controlled port.

   When a PaC does not have a PMK for the AP, the following procedure
   is taken:

   1.  The PaC associates with the AP.

   2.  The PaC configures a PRPA by using DHCP (in the case of IPv4) or
       configures a link-local address (in the case of IPv6), and then
       runs PANA by using the address.

   3.  Upon successful authentication, the PaC obtains a PMK for each AP
       controlled by the PAA.

   4.  The PaC performs 4-way handshake to establish a PTK (Pair-wise
       Transient Key) between the PaC and AP, by using the PMK.

   5.  The PaC obtains a POPA by using any method that the client
       normally uses.
"


[2] Remove sections 10.2.2.1 and 10.2.2.2.


[3] Change section 10.2.3 to:

"
10.2.3 Capability Discovery

   When a PaC is a mobile, there may be multiple APs available in its
   vicinity.  Each AP are connected to one of the following types of
   access networks.

   a) Free access network

      There is no IEEE 802.1X or PANA authentication in this access
      network.

   b) PANA-secured network

      There is PANA authentication in this access network.

   c) IEEE 802.1X-secured network

      There is IEEE 802.1X authentication in this access network.

   Type (c) is distinguished from others by checking the capability
   information advertised in IEEE 802.11 Beacon frames (IEEE 802.11i
   defines RSN Information Element for this purpose).  Types (a) and
   (b) are not distinguishable until the PaC associates with the AP,
   get an IP address, and engage in PANA discovery.  The default PaC
   behavior would be to act as if this is a free network and attempt
   DHCP.  This would be detected by the access network and trigger
   unsolicited PANA discovery.  A type (b) network would send a
   PANA-Start-Request to the client and block general purpose data
   traffic.  This helps the client discover whether the network is
   type (a) or type (b).  Or if the PaC is pre-provisioned with the
   information that this is a PANA enabled network, it can attempt PAA
   discovery immediately.  The PaC behavior after connecting to an AP
   of type (b) network is described in Section 10.2, Section 10.2.1
   and Section 10.2.2.
"

Comments appreciated.

Yoshihiro Ohba






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


From exim@www1.ietf.org  Wed May 12 18:40:40 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16493
	for <pana-archive@odin.ietf.org>; Wed, 12 May 2004 18:40:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO2NC-0005g5-Nk
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 18:38:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CMck9N021822
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 18:38:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO27q-0002cL-6P
	for pana-web-archive@optimus.ietf.org; Wed, 12 May 2004 18:22:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15841
	for <pana-web-archive@ietf.org>; Wed, 12 May 2004 18:22:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO27n-0005NT-9F
	for pana-web-archive@ietf.org; Wed, 12 May 2004 18:22:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO26o-0004rv-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 18:21:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO25l-0004LN-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 18:20:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO20M-0007pO-9r; Wed, 12 May 2004 18:15:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO1y5-0006DL-Pa
	for pana@optimus.ietf.org; Wed, 12 May 2004 18:12:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15075
	for <pana@ietf.org>; Wed, 12 May 2004 18:12:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO1y2-0000Kt-Pf
	for pana@ietf.org; Wed, 12 May 2004 18:12:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO1xA-0007eR-00
	for pana@ietf.org; Wed, 12 May 2004 18:11:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO1wR-00079y-00
	for pana@ietf.org; Wed, 12 May 2004 18:11:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4CMB6gH005218;
	Thu, 13 May 2004 07:11:06 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4CMB6xx008793;
	Thu, 13 May 2004 07:11:06 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA08790 ; Thu, 13 May 2004 07:11:06 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA28179; Thu, 13 May 2004 07:11:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA21155; Thu, 13 May 2004 07:11:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4CMB4EU004532;
	Thu, 13 May 2004 07:11:04 +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 <0HXM00KRPGADB0@tsbpo1.po.toshiba.co.jp>; Thu,
 13 May 2004 07:11:04 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BO1xB-0000Mx-00; Wed, 12 May 2004 15:11:53 -0700
Date: Wed, 12 May 2004 15:11:53 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040512221153.GI25541@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
Subject: [Pana] [framework] simplying WLAN section
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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=1.4 required=5.0 tests=AWL,FREE_ACCESS autolearn=no 
	version=2.60

I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
that higher-layer data traffic that is optionally allowed to be
received and processed on IEEE 802.1X Uncontrolled Ports does not have
to be terminated between stations (including AP).  Specifically, the
following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
from D10.0:

   Informative Note: STAs may optionally receive frames other than
   IEEE 802.1X messages in unprotected data MPDUs destined for the
   IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
   caveat that any protocol utilizing this mechanism should provide
   cryptographic data protection mechanisms, suitable for the intended
   application or usage, within the protocol itself.  These frames are
   never forwarded to or from the DS, but terminate at an application
   level service, such as a captive portal, on the AP.  This usage is
   outside the scope of this standard.

This means that in the PANA framework document, (virtual) AP hopping
operation described in 10.2.2.1 is not needed anymore when AP and PAA
are separated, and thus the same operation that was defined for
co-located AP and PAA is now applicable to the separate AP and PAA
case.


Suggested changes:

[1] Change section 10.2.2 to:

"
10.2.2 PANA with Bootstrapping IEEE 802.11i/WPA

   In this model, PANA is used for authentication and authorization,
   and L2 ciphering is used for access control, the latter is enabled
   by the former.  The L2 ciphering is based on using PSK (Pre-Shared
   Key) mode of WPA (Wi-Fi Protected Access) [WPA] or IEEE 802.11i
   [802.11i], which is derived from the EAP MSK as a result of
   successful PANA authentication.  In this document, the pre-shared
   key shared between station and AP is referred to as PMK (Pair-wise
   Master Key).  In this model, MAC address is used as the device
   identifier in PANA.

   This model allows the separation of PAA from APs (EPs).  A typical
   purpose of using this model is to reduce AP management cost by
   allowing physical separation of RADIUS/Diameter client from access
   points, where AP management can be a significant issue when
   deploying a large number of access points.

   By bootstrapping PSK mode of WPA and IEEE 802.11i from PANA it is
   also possible to improve wireless LAN security by providing protected
   disconnection procedure at L3.

   This model does not require any change in the current WPA and IEEE
   802.11i specifications.  This also means that PANA doesn't provide
   any L2 security features beyond those already provided for in WPA and
   IEEE 802.11i.

   The IEEE 802.11 specification [802.11] allows Class 1 data frames
   to be received in any state.  Also, the latest version of IEEE
   802.11i [802.11i] optionally allows higher-layer data traffic to be
   received and processed on their IEEE 802.1X Uncontrolled Ports.
   This feature allows processing IP-based traffic (such as ARP, IPv6
   neighbor discovery, DHCP, and PANA) on IEEE 802.1X Uncontrolled
   Port prior to client authentication.  (Note: WPA and its
   corresponding version of IEEE 802.11i draft do not explicitly
   define this operation, so it may be safer not to use this in WPA).

   Until the PaC is successfully authenticated, only a selected type
   of IP traffic is allowed over the IEEE 802.1X Uncontrolled Port.
   Any other IP traffic is dropped on the AP without being forwarded
   to the DS (Distribution System).  Upon successful PANA
   authentication, the traffic switches to the controlled port.  Host
   configuration, including obtaining an (potentially new) IP address,
   takes place on this port.  Usual DHCP-based, and also in the case of
   IPv6 stateless autoconfiguration, mechanism is available to the
   PaC.  After this point, the rest of the IP traffic, including PANA
   exchanges, are processed on the controlled port.

   When a PaC does not have a PMK for the AP, the following procedure
   is taken:

   1.  The PaC associates with the AP.

   2.  The PaC configures a PRPA by using DHCP (in the case of IPv4) or
       configures a link-local address (in the case of IPv6), and then
       runs PANA by using the address.

   3.  Upon successful authentication, the PaC obtains a PMK for each AP
       controlled by the PAA.

   4.  The PaC performs 4-way handshake to establish a PTK (Pair-wise
       Transient Key) between the PaC and AP, by using the PMK.

   5.  The PaC obtains a POPA by using any method that the client
       normally uses.
"


[2] Remove sections 10.2.2.1 and 10.2.2.2.


[3] Change section 10.2.3 to:

"
10.2.3 Capability Discovery

   When a PaC is a mobile, there may be multiple APs available in its
   vicinity.  Each AP are connected to one of the following types of
   access networks.

   a) Free access network

      There is no IEEE 802.1X or PANA authentication in this access
      network.

   b) PANA-secured network

      There is PANA authentication in this access network.

   c) IEEE 802.1X-secured network

      There is IEEE 802.1X authentication in this access network.

   Type (c) is distinguished from others by checking the capability
   information advertised in IEEE 802.11 Beacon frames (IEEE 802.11i
   defines RSN Information Element for this purpose).  Types (a) and
   (b) are not distinguishable until the PaC associates with the AP,
   get an IP address, and engage in PANA discovery.  The default PaC
   behavior would be to act as if this is a free network and attempt
   DHCP.  This would be detected by the access network and trigger
   unsolicited PANA discovery.  A type (b) network would send a
   PANA-Start-Request to the client and block general purpose data
   traffic.  This helps the client discover whether the network is
   type (a) or type (b).  Or if the PaC is pre-provisioned with the
   information that this is a PANA enabled network, it can attempt PAA
   discovery immediately.  The PaC behavior after connecting to an AP
   of type (b) network is described in Section 10.2, Section 10.2.1
   and Section 10.2.2.
"

Comments appreciated.

Yoshihiro Ohba






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



From pana-admin@ietf.org  Wed May 12 21:35:00 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25188
	for <pana-archive@lists.ietf.org>; Wed, 12 May 2004 21:35:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO53t-0001zQ-Ui; Wed, 12 May 2004 21:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO4yc-0000es-Em
	for pana@optimus.ietf.org; Wed, 12 May 2004 21:25:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24850
	for <pana@ietf.org>; Wed, 12 May 2004 21:25:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO4yZ-00051q-N0
	for pana@ietf.org; Wed, 12 May 2004 21:25:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO4xg-0004VQ-00
	for pana@ietf.org; Wed, 12 May 2004 21:24:37 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BO4wk-0003x5-00
	for pana@ietf.org; Wed, 12 May 2004 21:23:38 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 12 May 2004 23:43:20 -0000
Message-ID: <018b01c4387a$e9dc7000$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040512221153.GI25541@steelhead>
Subject: Re: [Pana] [framework] simplying WLAN section
Date: Wed, 12 May 2004 16:43:23 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,FREE_ACCESS 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

 Yoshi,


> I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> that higher-layer data traffic that is optionally allowed to be
> received and processed on IEEE 802.1X Uncontrolled Ports does not have
> to be terminated between stations (including AP).  Specifically, the
> following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> from D10.0:
> 
>    Informative Note: STAs may optionally receive frames other than

I am a bit confused by this statement. If this note was removed in the latest draft does it not
mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
version 7.0 there was a possibility that messages other than IEEE802.1x may be
received and terminated at the application layer, but with 10.0, it can no longer
receive and would be dropped before the application sees it. If so, it would mean
that PANA messages won't be received.  What am i missing ? 

-mohan

>    IEEE 802.1X messages in unprotected data MPDUs destined for the
>    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>    caveat that any protocol utilizing this mechanism should provide
>    cryptographic data protection mechanisms, suitable for the intended
>    application or usage, within the protocol itself.  These frames are
>    never forwarded to or from the DS, but terminate at an application
>    level service, such as a captive portal, on the AP.  This usage is
>    outside the scope of this standard.
> 
> This means that in the PANA framework document, (virtual) AP hopping
> operation described in 10.2.2.1 is not needed anymore when AP and PAA
> are separated, and thus the same operation that was defined for
> co-located AP and PAA is now applicable to the separate AP and PAA
> case.
> 
> 
> Suggested changes:
> 
> [1] Change section 10.2.2 to:
> 
> "
> 10.2.2 PANA with Bootstrapping IEEE 802.11i/WPA
> 
>    In this model, PANA is used for authentication and authorization,
>    and L2 ciphering is used for access control, the latter is enabled
>    by the former.  The L2 ciphering is based on using PSK (Pre-Shared
>    Key) mode of WPA (Wi-Fi Protected Access) [WPA] or IEEE 802.11i
>    [802.11i], which is derived from the EAP MSK as a result of
>    successful PANA authentication.  In this document, the pre-shared
>    key shared between station and AP is referred to as PMK (Pair-wise
>    Master Key).  In this model, MAC address is used as the device
>    identifier in PANA.
> 
>    This model allows the separation of PAA from APs (EPs).  A typical
>    purpose of using this model is to reduce AP management cost by
>    allowing physical separation of RADIUS/Diameter client from access
>    points, where AP management can be a significant issue when
>    deploying a large number of access points.
> 
>    By bootstrapping PSK mode of WPA and IEEE 802.11i from PANA it is
>    also possible to improve wireless LAN security by providing protected
>    disconnection procedure at L3.
> 
>    This model does not require any change in the current WPA and IEEE
>    802.11i specifications.  This also means that PANA doesn't provide
>    any L2 security features beyond those already provided for in WPA and
>    IEEE 802.11i.
> 
>    The IEEE 802.11 specification [802.11] allows Class 1 data frames
>    to be received in any state.  Also, the latest version of IEEE
>    802.11i [802.11i] optionally allows higher-layer data traffic to be
>    received and processed on their IEEE 802.1X Uncontrolled Ports.
>    This feature allows processing IP-based traffic (such as ARP, IPv6
>    neighbor discovery, DHCP, and PANA) on IEEE 802.1X Uncontrolled
>    Port prior to client authentication.  (Note: WPA and its
>    corresponding version of IEEE 802.11i draft do not explicitly
>    define this operation, so it may be safer not to use this in WPA).
> 
>    Until the PaC is successfully authenticated, only a selected type
>    of IP traffic is allowed over the IEEE 802.1X Uncontrolled Port.
>    Any other IP traffic is dropped on the AP without being forwarded
>    to the DS (Distribution System).  Upon successful PANA
>    authentication, the traffic switches to the controlled port.  Host
>    configuration, including obtaining an (potentially new) IP address,
>    takes place on this port.  Usual DHCP-based, and also in the case of
>    IPv6 stateless autoconfiguration, mechanism is available to the
>    PaC.  After this point, the rest of the IP traffic, including PANA
>    exchanges, are processed on the controlled port.
> 
>    When a PaC does not have a PMK for the AP, the following procedure
>    is taken:
> 
>    1.  The PaC associates with the AP.
> 
>    2.  The PaC configures a PRPA by using DHCP (in the case of IPv4) or
>        configures a link-local address (in the case of IPv6), and then
>        runs PANA by using the address.
> 
>    3.  Upon successful authentication, the PaC obtains a PMK for each AP
>        controlled by the PAA.
> 
>    4.  The PaC performs 4-way handshake to establish a PTK (Pair-wise
>        Transient Key) between the PaC and AP, by using the PMK.
> 
>    5.  The PaC obtains a POPA by using any method that the client
>        normally uses.
> "
> 
> 
> [2] Remove sections 10.2.2.1 and 10.2.2.2.
> 
> 
> [3] Change section 10.2.3 to:
> 
> "
> 10.2.3 Capability Discovery
> 
>    When a PaC is a mobile, there may be multiple APs available in its
>    vicinity.  Each AP are connected to one of the following types of
>    access networks.
> 
>    a) Free access network
> 
>       There is no IEEE 802.1X or PANA authentication in this access
>       network.
> 
>    b) PANA-secured network
> 
>       There is PANA authentication in this access network.
> 
>    c) IEEE 802.1X-secured network
> 
>       There is IEEE 802.1X authentication in this access network.
> 
>    Type (c) is distinguished from others by checking the capability
>    information advertised in IEEE 802.11 Beacon frames (IEEE 802.11i
>    defines RSN Information Element for this purpose).  Types (a) and
>    (b) are not distinguishable until the PaC associates with the AP,
>    get an IP address, and engage in PANA discovery.  The default PaC
>    behavior would be to act as if this is a free network and attempt
>    DHCP.  This would be detected by the access network and trigger
>    unsolicited PANA discovery.  A type (b) network would send a
>    PANA-Start-Request to the client and block general purpose data
>    traffic.  This helps the client discover whether the network is
>    type (a) or type (b).  Or if the PaC is pre-provisioned with the
>    information that this is a PANA enabled network, it can attempt PAA
>    discovery immediately.  The PaC behavior after connecting to an AP
>    of type (b) network is described in Section 10.2, Section 10.2.1
>    and Section 10.2.2.
> "
> 
> Comments appreciated.
> 
> Yoshihiro Ohba
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From exim@www1.ietf.org  Wed May 12 21:45:00 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25635
	for <pana-archive@odin.ietf.org>; Wed, 12 May 2004 21:45:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO5G0-0004xs-3z
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 21:43:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4D1hWYh019059
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 21:43:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO59S-0003EG-MM
	for pana-web-archive@optimus.ietf.org; Wed, 12 May 2004 21:36:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25271
	for <pana-web-archive@ietf.org>; Wed, 12 May 2004 21:36:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO59P-0002kd-Sf
	for pana-web-archive@ietf.org; Wed, 12 May 2004 21:36:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO58F-0002Ez-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 21:35:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO57G-0001k7-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 21:34:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO53t-0001zQ-Ui; Wed, 12 May 2004 21:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO4yc-0000es-Em
	for pana@optimus.ietf.org; Wed, 12 May 2004 21:25:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24850
	for <pana@ietf.org>; Wed, 12 May 2004 21:25:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO4yZ-00051q-N0
	for pana@ietf.org; Wed, 12 May 2004 21:25:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO4xg-0004VQ-00
	for pana@ietf.org; Wed, 12 May 2004 21:24:37 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BO4wk-0003x5-00
	for pana@ietf.org; Wed, 12 May 2004 21:23:38 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 12 May 2004 23:43:20 -0000
Message-ID: <018b01c4387a$e9dc7000$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040512221153.GI25541@steelhead>
Subject: Re: [Pana] [framework] simplying WLAN section
Date: Wed, 12 May 2004 16:43:23 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=1.4 required=5.0 tests=AWL,FREE_ACCESS autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 Yoshi,


> I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> that higher-layer data traffic that is optionally allowed to be
> received and processed on IEEE 802.1X Uncontrolled Ports does not have
> to be terminated between stations (including AP).  Specifically, the
> following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> from D10.0:
> 
>    Informative Note: STAs may optionally receive frames other than

I am a bit confused by this statement. If this note was removed in the latest draft does it not
mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
version 7.0 there was a possibility that messages other than IEEE802.1x may be
received and terminated at the application layer, but with 10.0, it can no longer
receive and would be dropped before the application sees it. If so, it would mean
that PANA messages won't be received.  What am i missing ? 

-mohan

>    IEEE 802.1X messages in unprotected data MPDUs destined for the
>    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>    caveat that any protocol utilizing this mechanism should provide
>    cryptographic data protection mechanisms, suitable for the intended
>    application or usage, within the protocol itself.  These frames are
>    never forwarded to or from the DS, but terminate at an application
>    level service, such as a captive portal, on the AP.  This usage is
>    outside the scope of this standard.
> 
> This means that in the PANA framework document, (virtual) AP hopping
> operation described in 10.2.2.1 is not needed anymore when AP and PAA
> are separated, and thus the same operation that was defined for
> co-located AP and PAA is now applicable to the separate AP and PAA
> case.
> 
> 
> Suggested changes:
> 
> [1] Change section 10.2.2 to:
> 
> "
> 10.2.2 PANA with Bootstrapping IEEE 802.11i/WPA
> 
>    In this model, PANA is used for authentication and authorization,
>    and L2 ciphering is used for access control, the latter is enabled
>    by the former.  The L2 ciphering is based on using PSK (Pre-Shared
>    Key) mode of WPA (Wi-Fi Protected Access) [WPA] or IEEE 802.11i
>    [802.11i], which is derived from the EAP MSK as a result of
>    successful PANA authentication.  In this document, the pre-shared
>    key shared between station and AP is referred to as PMK (Pair-wise
>    Master Key).  In this model, MAC address is used as the device
>    identifier in PANA.
> 
>    This model allows the separation of PAA from APs (EPs).  A typical
>    purpose of using this model is to reduce AP management cost by
>    allowing physical separation of RADIUS/Diameter client from access
>    points, where AP management can be a significant issue when
>    deploying a large number of access points.
> 
>    By bootstrapping PSK mode of WPA and IEEE 802.11i from PANA it is
>    also possible to improve wireless LAN security by providing protected
>    disconnection procedure at L3.
> 
>    This model does not require any change in the current WPA and IEEE
>    802.11i specifications.  This also means that PANA doesn't provide
>    any L2 security features beyond those already provided for in WPA and
>    IEEE 802.11i.
> 
>    The IEEE 802.11 specification [802.11] allows Class 1 data frames
>    to be received in any state.  Also, the latest version of IEEE
>    802.11i [802.11i] optionally allows higher-layer data traffic to be
>    received and processed on their IEEE 802.1X Uncontrolled Ports.
>    This feature allows processing IP-based traffic (such as ARP, IPv6
>    neighbor discovery, DHCP, and PANA) on IEEE 802.1X Uncontrolled
>    Port prior to client authentication.  (Note: WPA and its
>    corresponding version of IEEE 802.11i draft do not explicitly
>    define this operation, so it may be safer not to use this in WPA).
> 
>    Until the PaC is successfully authenticated, only a selected type
>    of IP traffic is allowed over the IEEE 802.1X Uncontrolled Port.
>    Any other IP traffic is dropped on the AP without being forwarded
>    to the DS (Distribution System).  Upon successful PANA
>    authentication, the traffic switches to the controlled port.  Host
>    configuration, including obtaining an (potentially new) IP address,
>    takes place on this port.  Usual DHCP-based, and also in the case of
>    IPv6 stateless autoconfiguration, mechanism is available to the
>    PaC.  After this point, the rest of the IP traffic, including PANA
>    exchanges, are processed on the controlled port.
> 
>    When a PaC does not have a PMK for the AP, the following procedure
>    is taken:
> 
>    1.  The PaC associates with the AP.
> 
>    2.  The PaC configures a PRPA by using DHCP (in the case of IPv4) or
>        configures a link-local address (in the case of IPv6), and then
>        runs PANA by using the address.
> 
>    3.  Upon successful authentication, the PaC obtains a PMK for each AP
>        controlled by the PAA.
> 
>    4.  The PaC performs 4-way handshake to establish a PTK (Pair-wise
>        Transient Key) between the PaC and AP, by using the PMK.
> 
>    5.  The PaC obtains a POPA by using any method that the client
>        normally uses.
> "
> 
> 
> [2] Remove sections 10.2.2.1 and 10.2.2.2.
> 
> 
> [3] Change section 10.2.3 to:
> 
> "
> 10.2.3 Capability Discovery
> 
>    When a PaC is a mobile, there may be multiple APs available in its
>    vicinity.  Each AP are connected to one of the following types of
>    access networks.
> 
>    a) Free access network
> 
>       There is no IEEE 802.1X or PANA authentication in this access
>       network.
> 
>    b) PANA-secured network
> 
>       There is PANA authentication in this access network.
> 
>    c) IEEE 802.1X-secured network
> 
>       There is IEEE 802.1X authentication in this access network.
> 
>    Type (c) is distinguished from others by checking the capability
>    information advertised in IEEE 802.11 Beacon frames (IEEE 802.11i
>    defines RSN Information Element for this purpose).  Types (a) and
>    (b) are not distinguishable until the PaC associates with the AP,
>    get an IP address, and engage in PANA discovery.  The default PaC
>    behavior would be to act as if this is a free network and attempt
>    DHCP.  This would be detected by the access network and trigger
>    unsolicited PANA discovery.  A type (b) network would send a
>    PANA-Start-Request to the client and block general purpose data
>    traffic.  This helps the client discover whether the network is
>    type (a) or type (b).  Or if the PaC is pre-provisioned with the
>    information that this is a PANA enabled network, it can attempt PAA
>    discovery immediately.  The PaC behavior after connecting to an AP
>    of type (b) network is described in Section 10.2, Section 10.2.1
>    and Section 10.2.2.
> "
> 
> Comments appreciated.
> 
> Yoshihiro Ohba
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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



From pana-admin@ietf.org  Wed May 12 23:29:02 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29594
	for <pana-archive@lists.ietf.org>; Wed, 12 May 2004 23:29:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6rB-000230-DZ; Wed, 12 May 2004 23:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6pk-0001g2-6O
	for pana@optimus.ietf.org; Wed, 12 May 2004 23:24:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29370
	for <pana@ietf.org>; Wed, 12 May 2004 23:24:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO6pi-0007YE-AO
	for pana@ietf.org; Wed, 12 May 2004 23:24:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO6oh-00073U-00
	for pana@ietf.org; Wed, 12 May 2004 23:23:28 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO6nc-0006L9-00
	for pana@ietf.org; Wed, 12 May 2004 23:22:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4D3MIgH015731;
	Thu, 13 May 2004 12:22:18 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4D3MIIh003511;
	Thu, 13 May 2004 12:22:18 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA03510 ; Thu, 13 May 2004 12:22:18 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA01255; Thu, 13 May 2004 12:22:17 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA07834; Thu, 13 May 2004 12:22:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4D3MGEU011559;
	Thu, 13 May 2004 12:22:16 +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 <0HXM0093LUP12Y@tsbpo1.po.toshiba.co.jp>; Thu,
 13 May 2004 12:22:15 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BO6nz-0001Rs-00; Wed, 12 May 2004 20:22:43 -0700
Date: Wed, 12 May 2004 20:22:43 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [framework] simplying WLAN section
In-reply-to: <018b01c4387a$e9dc7000$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040513032243.GA1584@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.5.1+cvs20040105i
References: <20040512221153.GI25541@steelhead>
 <018b01c4387a$e9dc7000$861167c0@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.1 required=5.0 tests=AWL 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, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
>  Yoshi,
> 
> 
> > I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> > that higher-layer data traffic that is optionally allowed to be
> > received and processed on IEEE 802.1X Uncontrolled Ports does not have
> > to be terminated between stations (including AP).  Specifically, the
> > following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> > from D10.0:
> > 
> >    Informative Note: STAs may optionally receive frames other than
> 
> I am a bit confused by this statement. If this note was removed in the latest draft does it not
> mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
> version 7.0 there was a possibility that messages other than IEEE802.1x may be
> received and terminated at the application layer, but with 10.0, it can no longer
> receive and would be dropped before the application sees it. If so, it would mean
> that PANA messages won't be received.  What am i missing ? 

In other section of D10.0, it says that:

	Within an RSN, this is different. In an RSNA the IEEE 802.1X
	Port determines when to allow data traffic across an IEEE
	802.11 link. A single IEEE 802.1X Port maps to one association
	and each association maps to an IEEE 802.1X Port. An IEEE
	802.1X Port consists of an IEEE 802.1X Controlled Port and an
	IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
	is blocked from passing general data traffic between two STAs
	until an IEEE 802.1X authentication procedure completes
	successfully over the IEEE 802.1X Uncontrolled Port. Once the
	AKM completes successfully, data protection is enabled to
	prevent unauthorized access, and the IEEE 802.1X Controlled
	Port unblocks to allow protected Data traffic. IEEE 802.1X
	Supplicants and Authenticators exchange protocol information
	via the IEEE 802.1X Uncontrolled Port. It is expected that
	most other protocol exchanges will make use of the IEEE 802.1X
	Controlled Ports.  However, a given protocol may need to
	bypass the authorization function and make use of the IEEE
	802.1X Uncontrolled Port.

This means some application traffic can be processed over 802.1X
Uncontrolled Port.  So the removal of the informative note means that
the restriction of PANA traffic termination at an RSN-enabled AP was
removed.

Yoshihiro Ohba


> 
> -mohan
> 
>    IEEE 802.1X messages in unprotected data MPDUs destined for the
>    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>    caveat that any protocol utilizing this mechanism should provide
>    cryptographic data protection mechanisms, suitable for the intended
>    application or usage, within the protocol itself.  These frames are
>    never forwarded to or from the DS, but terminate at an application
>    level service, such as a captive portal, on the AP.  This usage is
>    outside the scope of this standard.
>
> This means that in the PANA framework document, (virtual) AP hopping
> operation described in 10.2.2.1 is not needed anymore when AP and PAA
> are separated, and thus the same operation that was defined for
> co-located AP and PAA is now applicable to the separate AP and PAA
> case.
>
>

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


From exim@www1.ietf.org  Wed May 12 23:32:58 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29769
	for <pana-archive@odin.ietf.org>; Wed, 12 May 2004 23:32:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6wV-0003Eh-2d
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 23:31:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4D3VVXL012439
	for pana-archive@odin.ietf.org; Wed, 12 May 2004 23:31:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6vX-00030o-Nu
	for pana-web-archive@optimus.ietf.org; Wed, 12 May 2004 23:30:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29691
	for <pana-web-archive@ietf.org>; Wed, 12 May 2004 23:30:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO6vV-0002py-Q6
	for pana-web-archive@ietf.org; Wed, 12 May 2004 23:30:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO6ub-0002L9-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 23:29:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO6tc-0001qI-00
	for pana-web-archive@ietf.org; Wed, 12 May 2004 23:28:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6rB-000230-DZ; Wed, 12 May 2004 23:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO6pk-0001g2-6O
	for pana@optimus.ietf.org; Wed, 12 May 2004 23:24:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29370
	for <pana@ietf.org>; Wed, 12 May 2004 23:24:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BO6pi-0007YE-AO
	for pana@ietf.org; Wed, 12 May 2004 23:24:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO6oh-00073U-00
	for pana@ietf.org; Wed, 12 May 2004 23:23:28 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO6nc-0006L9-00
	for pana@ietf.org; Wed, 12 May 2004 23:22:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4D3MIgH015731;
	Thu, 13 May 2004 12:22:18 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4D3MIIh003511;
	Thu, 13 May 2004 12:22:18 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA03510 ; Thu, 13 May 2004 12:22:18 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA01255; Thu, 13 May 2004 12:22:17 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA07834; Thu, 13 May 2004 12:22:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4D3MGEU011559;
	Thu, 13 May 2004 12:22:16 +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 <0HXM0093LUP12Y@tsbpo1.po.toshiba.co.jp>; Thu,
 13 May 2004 12:22:15 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BO6nz-0001Rs-00; Wed, 12 May 2004 20:22:43 -0700
Date: Wed, 12 May 2004 20:22:43 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [framework] simplying WLAN section
In-reply-to: <018b01c4387a$e9dc7000$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040513032243.GA1584@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.5.1+cvs20040105i
References: <20040512221153.GI25541@steelhead>
 <018b01c4387a$e9dc7000$861167c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
>  Yoshi,
> 
> 
> > I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> > that higher-layer data traffic that is optionally allowed to be
> > received and processed on IEEE 802.1X Uncontrolled Ports does not have
> > to be terminated between stations (including AP).  Specifically, the
> > following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> > from D10.0:
> > 
> >    Informative Note: STAs may optionally receive frames other than
> 
> I am a bit confused by this statement. If this note was removed in the latest draft does it not
> mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
> version 7.0 there was a possibility that messages other than IEEE802.1x may be
> received and terminated at the application layer, but with 10.0, it can no longer
> receive and would be dropped before the application sees it. If so, it would mean
> that PANA messages won't be received.  What am i missing ? 

In other section of D10.0, it says that:

	Within an RSN, this is different. In an RSNA the IEEE 802.1X
	Port determines when to allow data traffic across an IEEE
	802.11 link. A single IEEE 802.1X Port maps to one association
	and each association maps to an IEEE 802.1X Port. An IEEE
	802.1X Port consists of an IEEE 802.1X Controlled Port and an
	IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
	is blocked from passing general data traffic between two STAs
	until an IEEE 802.1X authentication procedure completes
	successfully over the IEEE 802.1X Uncontrolled Port. Once the
	AKM completes successfully, data protection is enabled to
	prevent unauthorized access, and the IEEE 802.1X Controlled
	Port unblocks to allow protected Data traffic. IEEE 802.1X
	Supplicants and Authenticators exchange protocol information
	via the IEEE 802.1X Uncontrolled Port. It is expected that
	most other protocol exchanges will make use of the IEEE 802.1X
	Controlled Ports.  However, a given protocol may need to
	bypass the authorization function and make use of the IEEE
	802.1X Uncontrolled Port.

This means some application traffic can be processed over 802.1X
Uncontrolled Port.  So the removal of the informative note means that
the restriction of PANA traffic termination at an RSN-enabled AP was
removed.

Yoshihiro Ohba


> 
> -mohan
> 
>    IEEE 802.1X messages in unprotected data MPDUs destined for the
>    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>    caveat that any protocol utilizing this mechanism should provide
>    cryptographic data protection mechanisms, suitable for the intended
>    application or usage, within the protocol itself.  These frames are
>    never forwarded to or from the DS, but terminate at an application
>    level service, such as a captive portal, on the AP.  This usage is
>    outside the scope of this standard.
>
> This means that in the PANA framework document, (virtual) AP hopping
> operation described in 10.2.2.1 is not needed anymore when AP and PAA
> are separated, and thus the same operation that was defined for
> co-located AP and PAA is now applicable to the separate AP and PAA
> case.
>
>

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



From pana-admin@ietf.org  Thu May 13 10:07:02 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13858
	for <pana-archive@lists.ietf.org>; Thu, 13 May 2004 10:07:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGhs-0006pe-TB; Thu, 13 May 2004 09:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGfw-0006Ml-00
	for pana@optimus.ietf.org; Thu, 13 May 2004 09:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13067
	for <pana@ietf.org>; Thu, 13 May 2004 09:55:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOGfu-0000QZ-3p
	for pana@ietf.org; Thu, 13 May 2004 09:55:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOGex-0007fM-00
	for pana@ietf.org; Thu, 13 May 2004 09:54:04 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOGe0-0006aZ-00
	for pana@ietf.org; Thu, 13 May 2004 09:53:04 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 281A31CD6; Thu, 13 May 2004 15:52:32 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id E455D1817; Thu, 13 May 2004 15:52:31 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id DBA3514431; Thu, 13 May 2004 15:51:47 +0200 (MET DST)
Message-ID: <40A37CF2.70503@dif.um.es>
Date: Thu, 13 May 2004 15:49:38 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Subject: Re: [Pana] [framework] simplying WLAN section
References: <20040512221153.GI25541@steelhead> <018b01c4387a$e9dc7000$861167c0@adithya> <20040513032243.GA1584@steelhead>
In-Reply-To: <20040513032243.GA1584@steelhead>
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=AWL 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 Yoshihiro

I had a similar doubt... now it is clear... Then text you wrote is good
for me...

Regard...




Yoshihiro Ohba wrote:

>On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
>  
>
>> Yoshi,
>>
>>
>>    
>>
>>>I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
>>>that higher-layer data traffic that is optionally allowed to be
>>>received and processed on IEEE 802.1X Uncontrolled Ports does not have
>>>to be terminated between stations (including AP).  Specifically, the
>>>following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
>>>from D10.0:
>>>
>>>   Informative Note: STAs may optionally receive frames other than
>>>      
>>>
>>I am a bit confused by this statement. If this note was removed in the latest draft does it not
>>mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
>>version 7.0 there was a possibility that messages other than IEEE802.1x may be
>>received and terminated at the application layer, but with 10.0, it can no longer
>>receive and would be dropped before the application sees it. If so, it would mean
>>that PANA messages won't be received.  What am i missing ? 
>>    
>>

>In other section of D10.0, it says that:
>
>	Within an RSN, this is different. In an RSNA the IEEE 802.1X
>	Port determines when to allow data traffic across an IEEE
>	802.11 link. A single IEEE 802.1X Port maps to one association
>	and each association maps to an IEEE 802.1X Port. An IEEE
>	802.1X Port consists of an IEEE 802.1X Controlled Port and an
>	IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
>	is blocked from passing general data traffic between two STAs
>	until an IEEE 802.1X authentication procedure completes
>	successfully over the IEEE 802.1X Uncontrolled Port. Once the
>	AKM completes successfully, data protection is enabled to
>	prevent unauthorized access, and the IEEE 802.1X Controlled
>	Port unblocks to allow protected Data traffic. IEEE 802.1X
>	Supplicants and Authenticators exchange protocol information
>	via the IEEE 802.1X Uncontrolled Port. It is expected that
>	most other protocol exchanges will make use of the IEEE 802.1X
>	Controlled Ports.  However, a given protocol may need to
>	bypass the authorization function and make use of the IEEE
>	802.1X Uncontrolled Port.
>
>This means some application traffic can be processed over 802.1X
>Uncontrolled Port.  So the removal of the informative note means that
>the restriction of PANA traffic termination at an RSN-enabled AP was
>removed.
>
>Yoshihiro Ohba
>
>
>  
>
>>-mohan
>>
>>   IEEE 802.1X messages in unprotected data MPDUs destined for the
>>   IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>>   caveat that any protocol utilizing this mechanism should provide
>>   cryptographic data protection mechanisms, suitable for the intended
>>   application or usage, within the protocol itself.  These frames are
>>   never forwarded to or from the DS, but terminate at an application
>>   level service, such as a captive portal, on the AP.  This usage is
>>   outside the scope of this standard.
>>
>>This means that in the PANA framework document, (virtual) AP hopping
>>operation described in 10.2.2.1 is not needed anymore when AP and PAA
>>are separated, and thus the same operation that was defined for
>>co-located AP and PAA is now applicable to the separate AP and PAA
>>case.
>>
>>
>>    
>>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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


From exim@www1.ietf.org  Thu May 13 10:22:31 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15302
	for <pana-archive@odin.ietf.org>; Thu, 13 May 2004 10:22:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGy2-00077h-82
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 10:13:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DEDkrY027376
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 10:13:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGsc-0004CG-JB
	for pana-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:08:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14028
	for <pana-web-archive@ietf.org>; Thu, 13 May 2004 10:08:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOGsa-0007dW-Du
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:08:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOGrq-00075v-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:07:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOGr3-0006XG-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:06:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGhs-0006pe-TB; Thu, 13 May 2004 09:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOGfw-0006Ml-00
	for pana@optimus.ietf.org; Thu, 13 May 2004 09:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13067
	for <pana@ietf.org>; Thu, 13 May 2004 09:55:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOGfu-0000QZ-3p
	for pana@ietf.org; Thu, 13 May 2004 09:55:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOGex-0007fM-00
	for pana@ietf.org; Thu, 13 May 2004 09:54:04 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOGe0-0006aZ-00
	for pana@ietf.org; Thu, 13 May 2004 09:53:04 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 281A31CD6; Thu, 13 May 2004 15:52:32 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id E455D1817; Thu, 13 May 2004 15:52:31 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id DBA3514431; Thu, 13 May 2004 15:51:47 +0200 (MET DST)
Message-ID: <40A37CF2.70503@dif.um.es>
Date: Thu, 13 May 2004 15:49:38 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
Subject: Re: [Pana] [framework] simplying WLAN section
References: <20040512221153.GI25541@steelhead> <018b01c4387a$e9dc7000$861167c0@adithya> <20040513032243.GA1584@steelhead>
In-Reply-To: <20040513032243.GA1584@steelhead>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshihiro

I had a similar doubt... now it is clear... Then text you wrote is good
for me...

Regard...




Yoshihiro Ohba wrote:

>On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
>  
>
>> Yoshi,
>>
>>
>>    
>>
>>>I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
>>>that higher-layer data traffic that is optionally allowed to be
>>>received and processed on IEEE 802.1X Uncontrolled Ports does not have
>>>to be terminated between stations (including AP).  Specifically, the
>>>following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
>>>from D10.0:
>>>
>>>   Informative Note: STAs may optionally receive frames other than
>>>      
>>>
>>I am a bit confused by this statement. If this note was removed in the latest draft does it not
>>mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
>>version 7.0 there was a possibility that messages other than IEEE802.1x may be
>>received and terminated at the application layer, but with 10.0, it can no longer
>>receive and would be dropped before the application sees it. If so, it would mean
>>that PANA messages won't be received.  What am i missing ? 
>>    
>>

>In other section of D10.0, it says that:
>
>	Within an RSN, this is different. In an RSNA the IEEE 802.1X
>	Port determines when to allow data traffic across an IEEE
>	802.11 link. A single IEEE 802.1X Port maps to one association
>	and each association maps to an IEEE 802.1X Port. An IEEE
>	802.1X Port consists of an IEEE 802.1X Controlled Port and an
>	IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
>	is blocked from passing general data traffic between two STAs
>	until an IEEE 802.1X authentication procedure completes
>	successfully over the IEEE 802.1X Uncontrolled Port. Once the
>	AKM completes successfully, data protection is enabled to
>	prevent unauthorized access, and the IEEE 802.1X Controlled
>	Port unblocks to allow protected Data traffic. IEEE 802.1X
>	Supplicants and Authenticators exchange protocol information
>	via the IEEE 802.1X Uncontrolled Port. It is expected that
>	most other protocol exchanges will make use of the IEEE 802.1X
>	Controlled Ports.  However, a given protocol may need to
>	bypass the authorization function and make use of the IEEE
>	802.1X Uncontrolled Port.
>
>This means some application traffic can be processed over 802.1X
>Uncontrolled Port.  So the removal of the informative note means that
>the restriction of PANA traffic termination at an RSN-enabled AP was
>removed.
>
>Yoshihiro Ohba
>
>
>  
>
>>-mohan
>>
>>   IEEE 802.1X messages in unprotected data MPDUs destined for the
>>   IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>>   caveat that any protocol utilizing this mechanism should provide
>>   cryptographic data protection mechanisms, suitable for the intended
>>   application or usage, within the protocol itself.  These frames are
>>   never forwarded to or from the DS, but terminate at an application
>>   level service, such as a captive portal, on the AP.  This usage is
>>   outside the scope of this standard.
>>
>>This means that in the PANA framework document, (virtual) AP hopping
>>operation described in 10.2.2.1 is not needed anymore when AP and PAA
>>are separated, and thus the same operation that was defined for
>>co-located AP and PAA is now applicable to the separate AP and PAA
>>case.
>>
>>
>>    
>>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From pana-admin@ietf.org  Thu May 13 10:41:59 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16575
	for <pana-archive@lists.ietf.org>; Thu, 13 May 2004 10:41:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHLV-0005UV-Pj; Thu, 13 May 2004 10:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHFj-0004LQ-6R
	for pana@optimus.ietf.org; Thu, 13 May 2004 10:32:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15970
	for <pana@ietf.org>; Thu, 13 May 2004 10:31:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHFg-0005Ky-CB
	for pana@ietf.org; Thu, 13 May 2004 10:32:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHEg-0004lQ-00
	for pana@ietf.org; Thu, 13 May 2004 10:30:59 -0400
Received: from viap098.atea.be ([194.78.143.98] helo=hrtades9.atea.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHDX-0003gP-00
	for pana@ietf.org; Thu, 13 May 2004 10:29:47 -0400
Received: from hrtades10.atea.be (siemens.atea.be [139.10.143.141]) by hrtades9.atea.be with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id JMT2ZQHQ; Thu, 13 May 2004 16:29:15 +0200
Received: by siemens.atea.be with Internet Mail Service (5.5.2653.19)
	id <J6CBD8FS>; Thu, 13 May 2004 16:29:15 +0200
Message-ID: <57FD2C3A246F76438CA6FDAD8FE9F1956920DD@hrtades7.atea.be>
From: Goeman Stefan <Stefan.Goeman@siemens.com>
To: "'pana@ietf.org'" <pana@ietf.org>
Date: Thu, 13 May 2004 16:29:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C438F6.A9F67C70"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60
Subject: [Pana] PANA - link local address - duplicate address detection
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C438F6.A9F67C70
Content-Type: text/plain;
	charset="iso-8859-1"

Hello,

I have a question that is puzzling me.
In IPv6 you could use an autoconfigured link local address and start PANA.
However, normally you should do duplicate address detection for this link
local address, and everybody knows the problems that exist with DAD. I know
that IETF SEND provides a solution to this problem, but personally I am not
so happy with this (PKI-based) approach.

Q1: So, I wonder what would be the real threat/problem if you would use a
link local address to start PANA, secure the link layer and configure a post
PANA IP-address with DHCPv6 for example?

Q2: In case of a wireless environment, would the following approach be
possible? A MN creates a link local address and performs DAD. The AP, where
the link layer terminates, "intercepts" this request and answers on behalf
of all MN connected to the AP (the AP knows all link local and other address
of the MN which are currently already connected). In this case a malicious
MN would not be able to falsely claim the link local address of the new MN
trying to obtain IP connectivity.

Greetings,
Stefan. 


Stefan Goeman 
SIEMENS ICM/ICN 
Stefan.Goeman@siemens.com  <mailto:Stefan.Goeman@siemens.atea.be> 

Mobile Solutions 
and Enabling Services
http://www.ic.siemens.be <http://www.ic.siemens.be/eng/default_rd.shtm>

Customer driven solution providers 	


------_=_NextPart_001_01C438F6.A9F67C70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>PANA - link local address - duplicate address detection</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question that is puzzling =
me.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">In IPv6 you could use an =
autoconfigured link local address and start PANA. However, normally you =
should do duplicate address detection for this link local address, and =
everybody knows the problems that exist with DAD. I know that IETF SEND =
provides a solution to this problem, but personally I am not so happy =
with this (PKI-based) approach.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Q1: So, I wonder what would be the =
real threat/problem if you would use a link local address to start =
PANA, secure the link layer and configure a post PANA IP-address with =
DHCPv6 for example?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Q2: In case of a wireless environment, =
would the following approach be possible? A MN creates a link local =
address and performs DAD. The AP, where the link layer terminates, =
&quot;intercepts&quot; this request and answers on behalf of all MN =
connected to the AP (the AP knows all link local and other address of =
the MN which are currently already connected). In this case a malicious =
MN would not be able to falsely claim the link local address of the new =
MN trying to obtain IP connectivity.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Greetings,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Stefan. </FONT>
</P>
<BR>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Stefan =
Goeman</FONT><BR>
<B></B><B><FONT COLOR=3D"#008080" FACE=3D"Times New =
Roman">SIEMENS</FONT><FONT FACE=3D"Arial"> </FONT><FONT =
COLOR=3D"#008080" SIZE=3D2 FACE=3D"Arial">ICM/ICN</FONT><FONT =
FACE=3D"Arial"></FONT></B><BR>
<A HREF=3D"mailto:Stefan.Goeman@siemens.atea.be"><U></U><U><FONT =
COLOR=3D"#0000FF" SIZE=3D1 =
FACE=3D"Verdana">Stefan.Goeman@siemens.com</FONT></U></A><BR>
<U></U><U></U>
<BR><B><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">Mobile =
Solutions=A0<BR>
and Enabling Services</FONT><BR>
</B><A HREF=3D"http://www.ic.siemens.be/eng/default_rd.shtm"><U><FONT =
COLOR=3D"#0000FF" =
FACE=3D"Arial">http://www.ic.siemens.be</FONT></U></A><FONT =
FACE=3D"Arial"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
=A0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT FACE=3D"Arial">Customer driven solution providers =
&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C438F6.A9F67C70--

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


From exim@www1.ietf.org  Thu May 13 10:48:59 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16998
	for <pana-archive@odin.ietf.org>; Thu, 13 May 2004 10:48:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHV7-0008Pq-41
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 10:47:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DElvaF032345
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 10:47:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHQl-0007G2-2d
	for pana-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:43:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16676
	for <pana-web-archive@ietf.org>; Thu, 13 May 2004 10:43:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHQi-0003h4-Lc
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:43:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHPk-00038j-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:42:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHOt-0002ZO-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 10:41:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHLV-0005UV-Pj; Thu, 13 May 2004 10:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHFj-0004LQ-6R
	for pana@optimus.ietf.org; Thu, 13 May 2004 10:32:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15970
	for <pana@ietf.org>; Thu, 13 May 2004 10:31:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHFg-0005Ky-CB
	for pana@ietf.org; Thu, 13 May 2004 10:32:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHEg-0004lQ-00
	for pana@ietf.org; Thu, 13 May 2004 10:30:59 -0400
Received: from viap098.atea.be ([194.78.143.98] helo=hrtades9.atea.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHDX-0003gP-00
	for pana@ietf.org; Thu, 13 May 2004 10:29:47 -0400
Received: from hrtades10.atea.be (siemens.atea.be [139.10.143.141]) by hrtades9.atea.be with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id JMT2ZQHQ; Thu, 13 May 2004 16:29:15 +0200
Received: by siemens.atea.be with Internet Mail Service (5.5.2653.19)
	id <J6CBD8FS>; Thu, 13 May 2004 16:29:15 +0200
Message-ID: <57FD2C3A246F76438CA6FDAD8FE9F1956920DD@hrtades7.atea.be>
From: Goeman Stefan <Stefan.Goeman@siemens.com>
To: "'pana@ietf.org'" <pana@ietf.org>
Date: Thu, 13 May 2004 16:29:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C438F6.A9F67C70"
Subject: [Pana] PANA - link local address - duplicate address detection
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.6 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C438F6.A9F67C70
Content-Type: text/plain;
	charset="iso-8859-1"

Hello,

I have a question that is puzzling me.
In IPv6 you could use an autoconfigured link local address and start PANA.
However, normally you should do duplicate address detection for this link
local address, and everybody knows the problems that exist with DAD. I know
that IETF SEND provides a solution to this problem, but personally I am not
so happy with this (PKI-based) approach.

Q1: So, I wonder what would be the real threat/problem if you would use a
link local address to start PANA, secure the link layer and configure a post
PANA IP-address with DHCPv6 for example?

Q2: In case of a wireless environment, would the following approach be
possible? A MN creates a link local address and performs DAD. The AP, where
the link layer terminates, "intercepts" this request and answers on behalf
of all MN connected to the AP (the AP knows all link local and other address
of the MN which are currently already connected). In this case a malicious
MN would not be able to falsely claim the link local address of the new MN
trying to obtain IP connectivity.

Greetings,
Stefan. 


Stefan Goeman 
SIEMENS ICM/ICN 
Stefan.Goeman@siemens.com  <mailto:Stefan.Goeman@siemens.atea.be> 

Mobile Solutions 
and Enabling Services
http://www.ic.siemens.be <http://www.ic.siemens.be/eng/default_rd.shtm>

Customer driven solution providers 	


------_=_NextPart_001_01C438F6.A9F67C70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>PANA - link local address - duplicate address detection</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question that is puzzling =
me.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">In IPv6 you could use an =
autoconfigured link local address and start PANA. However, normally you =
should do duplicate address detection for this link local address, and =
everybody knows the problems that exist with DAD. I know that IETF SEND =
provides a solution to this problem, but personally I am not so happy =
with this (PKI-based) approach.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Q1: So, I wonder what would be the =
real threat/problem if you would use a link local address to start =
PANA, secure the link layer and configure a post PANA IP-address with =
DHCPv6 for example?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Q2: In case of a wireless environment, =
would the following approach be possible? A MN creates a link local =
address and performs DAD. The AP, where the link layer terminates, =
&quot;intercepts&quot; this request and answers on behalf of all MN =
connected to the AP (the AP knows all link local and other address of =
the MN which are currently already connected). In this case a malicious =
MN would not be able to falsely claim the link local address of the new =
MN trying to obtain IP connectivity.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Greetings,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Stefan. </FONT>
</P>
<BR>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Stefan =
Goeman</FONT><BR>
<B></B><B><FONT COLOR=3D"#008080" FACE=3D"Times New =
Roman">SIEMENS</FONT><FONT FACE=3D"Arial"> </FONT><FONT =
COLOR=3D"#008080" SIZE=3D2 FACE=3D"Arial">ICM/ICN</FONT><FONT =
FACE=3D"Arial"></FONT></B><BR>
<A HREF=3D"mailto:Stefan.Goeman@siemens.atea.be"><U></U><U><FONT =
COLOR=3D"#0000FF" SIZE=3D1 =
FACE=3D"Verdana">Stefan.Goeman@siemens.com</FONT></U></A><BR>
<U></U><U></U>
<BR><B><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">Mobile =
Solutions=A0<BR>
and Enabling Services</FONT><BR>
</B><A HREF=3D"http://www.ic.siemens.be/eng/default_rd.shtm"><U><FONT =
COLOR=3D"#0000FF" =
FACE=3D"Arial">http://www.ic.siemens.be</FONT></U></A><FONT =
FACE=3D"Arial"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
=A0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT FACE=3D"Arial">Customer driven solution providers =
&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C438F6.A9F67C70--

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



From pana-admin@ietf.org  Thu May 13 12:37:00 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21856
	for <pana-archive@lists.ietf.org>; Thu, 13 May 2004 12:37:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJ8n-0007JG-Ib; Thu, 13 May 2004 12:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJ58-00067U-LI
	for pana@optimus.ietf.org; Thu, 13 May 2004 12:29:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21542
	for <pana@ietf.org>; Thu, 13 May 2004 12:29:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJ57-0005Q4-4N
	for pana@ietf.org; Thu, 13 May 2004 12:29:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJ46-0004u8-00
	for pana@ietf.org; Thu, 13 May 2004 12:28:11 -0400
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOJ35-0004Np-00
	for pana@ietf.org; Thu, 13 May 2004 12:27:07 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp812.mail.sc5.yahoo.com with SMTP; 13 May 2004 16:26:13 -0000
Message-ID: <005001c43907$01c94b20$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040512221153.GI25541@steelhead> <018b01c4387a$e9dc7000$861167c0@adithya> <20040513032243.GA1584@steelhead>
Subject: Re: [Pana] [framework] simplying WLAN section
Date: Thu, 13 May 2004 09:26:12 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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

 Ok, this text makes it clear. And your original text sounds fine to me.

-mohan

> On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
> >  Yoshi,
> > 
> > 
> > > I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> > > that higher-layer data traffic that is optionally allowed to be
> > > received and processed on IEEE 802.1X Uncontrolled Ports does not have
> > > to be terminated between stations (including AP).  Specifically, the
> > > following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> > > from D10.0:
> > > 
> > >    Informative Note: STAs may optionally receive frames other than
> > 
> > I am a bit confused by this statement. If this note was removed in the latest draft does it not
> > mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
> > version 7.0 there was a possibility that messages other than IEEE802.1x may be
> > received and terminated at the application layer, but with 10.0, it can no longer
> > receive and would be dropped before the application sees it. If so, it would mean
> > that PANA messages won't be received.  What am i missing ? 
> 
> In other section of D10.0, it says that:
> 
> Within an RSN, this is different. In an RSNA the IEEE 802.1X
> Port determines when to allow data traffic across an IEEE
> 802.11 link. A single IEEE 802.1X Port maps to one association
> and each association maps to an IEEE 802.1X Port. An IEEE
> 802.1X Port consists of an IEEE 802.1X Controlled Port and an
> IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
> is blocked from passing general data traffic between two STAs
> until an IEEE 802.1X authentication procedure completes
> successfully over the IEEE 802.1X Uncontrolled Port. Once the
> AKM completes successfully, data protection is enabled to
> prevent unauthorized access, and the IEEE 802.1X Controlled
> Port unblocks to allow protected Data traffic. IEEE 802.1X
> Supplicants and Authenticators exchange protocol information
> via the IEEE 802.1X Uncontrolled Port. It is expected that
> most other protocol exchanges will make use of the IEEE 802.1X
> Controlled Ports.  However, a given protocol may need to
> bypass the authorization function and make use of the IEEE
> 802.1X Uncontrolled Port.
> 
> This means some application traffic can be processed over 802.1X
> Uncontrolled Port.  So the removal of the informative note means that
> the restriction of PANA traffic termination at an RSN-enabled AP was
> removed.
> 
> Yoshihiro Ohba
> 
> 
> > 
> > -mohan
> > 
> >    IEEE 802.1X messages in unprotected data MPDUs destined for the
> >    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
> >    caveat that any protocol utilizing this mechanism should provide
> >    cryptographic data protection mechanisms, suitable for the intended
> >    application or usage, within the protocol itself.  These frames are
> >    never forwarded to or from the DS, but terminate at an application
> >    level service, such as a captive portal, on the AP.  This usage is
> >    outside the scope of this standard.
> >
> > This means that in the PANA framework document, (virtual) AP hopping
> > operation described in 10.2.2.1 is not needed anymore when AP and PAA
> > are separated, and thus the same operation that was defined for
> > co-located AP and PAA is now applicable to the separate AP and PAA
> > case.
> >
> >

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


From exim@www1.ietf.org  Thu May 13 12:55:21 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23164
	for <pana-archive@odin.ietf.org>; Thu, 13 May 2004 12:55:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJS9-0003EG-Tk
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 12:53:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DGr1Jr012412
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 12:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJOO-0002I0-Go
	for pana-web-archive@optimus.ietf.org; Thu, 13 May 2004 12:49:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22502
	for <pana-web-archive@ietf.org>; Thu, 13 May 2004 12:49:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJOM-0000EK-Pw
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:49:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJMu-00078u-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:47:38 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJLc-0006Xz-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:46:16 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BOJCE-0005dM-FM
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:36:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJ8n-0007JG-Ib; Thu, 13 May 2004 12:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJ58-00067U-LI
	for pana@optimus.ietf.org; Thu, 13 May 2004 12:29:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21542
	for <pana@ietf.org>; Thu, 13 May 2004 12:29:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJ57-0005Q4-4N
	for pana@ietf.org; Thu, 13 May 2004 12:29:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJ46-0004u8-00
	for pana@ietf.org; Thu, 13 May 2004 12:28:11 -0400
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOJ35-0004Np-00
	for pana@ietf.org; Thu, 13 May 2004 12:27:07 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp812.mail.sc5.yahoo.com with SMTP; 13 May 2004 16:26:13 -0000
Message-ID: <005001c43907$01c94b20$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040512221153.GI25541@steelhead> <018b01c4387a$e9dc7000$861167c0@adithya> <20040513032243.GA1584@steelhead>
Subject: Re: [Pana] [framework] simplying WLAN section
Date: Thu, 13 May 2004 09:26:12 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 Ok, this text makes it clear. And your original text sounds fine to me.

-mohan

> On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
> >  Yoshi,
> > 
> > 
> > > I have checked the latest version of IEEE 802.11i/D10.0, and I noticed
> > > that higher-layer data traffic that is optionally allowed to be
> > > received and processed on IEEE 802.1X Uncontrolled Ports does not have
> > > to be terminated between stations (including AP).  Specifically, the
> > > following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
> > > from D10.0:
> > > 
> > >    Informative Note: STAs may optionally receive frames other than
> > 
> > I am a bit confused by this statement. If this note was removed in the latest draft does it not
> > mean that "STAs may not receive frames other than IEEE802.1x messages" i.e till
> > version 7.0 there was a possibility that messages other than IEEE802.1x may be
> > received and terminated at the application layer, but with 10.0, it can no longer
> > receive and would be dropped before the application sees it. If so, it would mean
> > that PANA messages won't be received.  What am i missing ? 
> 
> In other section of D10.0, it says that:
> 
> Within an RSN, this is different. In an RSNA the IEEE 802.1X
> Port determines when to allow data traffic across an IEEE
> 802.11 link. A single IEEE 802.1X Port maps to one association
> and each association maps to an IEEE 802.1X Port. An IEEE
> 802.1X Port consists of an IEEE 802.1X Controlled Port and an
> IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
> is blocked from passing general data traffic between two STAs
> until an IEEE 802.1X authentication procedure completes
> successfully over the IEEE 802.1X Uncontrolled Port. Once the
> AKM completes successfully, data protection is enabled to
> prevent unauthorized access, and the IEEE 802.1X Controlled
> Port unblocks to allow protected Data traffic. IEEE 802.1X
> Supplicants and Authenticators exchange protocol information
> via the IEEE 802.1X Uncontrolled Port. It is expected that
> most other protocol exchanges will make use of the IEEE 802.1X
> Controlled Ports.  However, a given protocol may need to
> bypass the authorization function and make use of the IEEE
> 802.1X Uncontrolled Port.
> 
> This means some application traffic can be processed over 802.1X
> Uncontrolled Port.  So the removal of the informative note means that
> the restriction of PANA traffic termination at an RSN-enabled AP was
> removed.
> 
> Yoshihiro Ohba
> 
> 
> > 
> > -mohan
> > 
> >    IEEE 802.1X messages in unprotected data MPDUs destined for the
> >    IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
> >    caveat that any protocol utilizing this mechanism should provide
> >    cryptographic data protection mechanisms, suitable for the intended
> >    application or usage, within the protocol itself.  These frames are
> >    never forwarded to or from the DS, but terminate at an application
> >    level service, such as a captive portal, on the AP.  This usage is
> >    outside the scope of this standard.
> >
> > This means that in the PANA framework document, (virtual) AP hopping
> > operation described in 10.2.2.1 is not needed anymore when AP and PAA
> > are separated, and thus the same operation that was defined for
> > co-located AP and PAA is now applicable to the separate AP and PAA
> > case.
> >
> >

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



From pana-admin@ietf.org  Thu May 13 12:57:46 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23336
	for <pana-archive@lists.ietf.org>; Thu, 13 May 2004 12:57:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJT7-0003R0-16; Thu, 13 May 2004 12:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJOQ-0002I4-SA
	for pana@optimus.ietf.org; Thu, 13 May 2004 12:49:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22525
	for <pana@ietf.org>; Thu, 13 May 2004 12:49:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJOP-0000Hd-3c
	for pana@ietf.org; Thu, 13 May 2004 12:49:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJMz-00079J-00
	for pana@ietf.org; Thu, 13 May 2004 12:47:42 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOJLc-0006Ym-00
	for pana@ietf.org; Thu, 13 May 2004 12:46:17 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 13 May 2004 16:36:25 -0000
Message-ID: <008501c43908$6eac8c60$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Goeman Stefan" <Stefan.Goeman@siemens.com>, <pana@ietf.org>
References: <57FD2C3A246F76438CA6FDAD8FE9F1956920DD@hrtades7.atea.be>
Subject: Re: [Pana] PANA - link local address - duplicate address detection
Date: Thu, 13 May 2004 09:36:19 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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

 
> Hello,
> 
> I have a question that is puzzling me.
> In IPv6 you could use an autoconfigured link local address and start PANA.
> However, normally you should do duplicate address detection for this link
> local address, and everybody knows the problems that exist with DAD. I know
> that IETF SEND provides a solution to this problem, but personally I am not
> so happy with this (PKI-based) approach.
> 
> Q1: So, I wonder what would be the real threat/problem if you would use a
> link local address to start PANA, secure the link layer and configure a post
> PANA IP-address with DHCPv6 for example?
> 
> Q2: In case of a wireless environment, would the following approach be
> possible? A MN creates a link local address and performs DAD. The AP, where
> the link layer terminates, "intercepts" this request and answers on behalf
> of all MN connected to the AP (the AP knows all link local and other address
> of the MN which are currently already connected). In this case a malicious
> MN would not be able to falsely claim the link local address of the new MN
> trying to obtain IP connectivity.
> 
Please see this draft 
http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt

The originator of the DAD also gets the DAD packet and the link layer seems to
drop the packet. i.e Duplicate address is not detected today in IPv6 with wlans.

If this problem gets fixed, then this DoS attack can happen and PANA cannot stop it and also it is
not in the scope of PANA to stop it.

-mohan

> Greetings,
> Stefan. 
> 
> 
> Stefan Goeman 
> SIEMENS ICM/ICN 
> Stefan.Goeman@siemens.com  <mailto:Stefan.Goeman@siemens.atea.be> 
> 
> Mobile Solutions 
> and Enabling Services
> http://www.ic.siemens.be <http://www.ic.siemens.be/eng/default_rd.shtm>
> 
> Customer driven solution providers 
> 
> 

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


From exim@www1.ietf.org  Thu May 13 13:29:09 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26055
	for <pana-archive@odin.ietf.org>; Thu, 13 May 2004 13:29:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJmf-0000Ta-BR
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 13:14:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DHEDQ1001825
	for pana-archive@odin.ietf.org; Thu, 13 May 2004 13:14:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJYI-0004Wm-6T
	for pana-web-archive@optimus.ietf.org; Thu, 13 May 2004 12:59:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23457
	for <pana-web-archive@ietf.org>; Thu, 13 May 2004 12:59:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJYG-00065g-FO
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:59:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJXK-0005Yp-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:58:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJWJ-00051o-00
	for pana-web-archive@ietf.org; Thu, 13 May 2004 12:57:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJT7-0003R0-16; Thu, 13 May 2004 12:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJOQ-0002I4-SA
	for pana@optimus.ietf.org; Thu, 13 May 2004 12:49:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22525
	for <pana@ietf.org>; Thu, 13 May 2004 12:49:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOJOP-0000Hd-3c
	for pana@ietf.org; Thu, 13 May 2004 12:49:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJMz-00079J-00
	for pana@ietf.org; Thu, 13 May 2004 12:47:42 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOJLc-0006Ym-00
	for pana@ietf.org; Thu, 13 May 2004 12:46:17 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 13 May 2004 16:36:25 -0000
Message-ID: <008501c43908$6eac8c60$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Goeman Stefan" <Stefan.Goeman@siemens.com>, <pana@ietf.org>
References: <57FD2C3A246F76438CA6FDAD8FE9F1956920DD@hrtades7.atea.be>
Subject: Re: [Pana] PANA - link local address - duplicate address detection
Date: Thu, 13 May 2004 09:36:19 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 
> Hello,
> 
> I have a question that is puzzling me.
> In IPv6 you could use an autoconfigured link local address and start PANA.
> However, normally you should do duplicate address detection for this link
> local address, and everybody knows the problems that exist with DAD. I know
> that IETF SEND provides a solution to this problem, but personally I am not
> so happy with this (PKI-based) approach.
> 
> Q1: So, I wonder what would be the real threat/problem if you would use a
> link local address to start PANA, secure the link layer and configure a post
> PANA IP-address with DHCPv6 for example?
> 
> Q2: In case of a wireless environment, would the following approach be
> possible? A MN creates a link local address and performs DAD. The AP, where
> the link layer terminates, "intercepts" this request and answers on behalf
> of all MN connected to the AP (the AP knows all link local and other address
> of the MN which are currently already connected). In this case a malicious
> MN would not be able to falsely claim the link local address of the new MN
> trying to obtain IP connectivity.
> 
Please see this draft 
http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt

The originator of the DAD also gets the DAD packet and the link layer seems to
drop the packet. i.e Duplicate address is not detected today in IPv6 with wlans.

If this problem gets fixed, then this DoS attack can happen and PANA cannot stop it and also it is
not in the scope of PANA to stop it.

-mohan

> Greetings,
> Stefan. 
> 
> 
> Stefan Goeman 
> SIEMENS ICM/ICN 
> Stefan.Goeman@siemens.com  <mailto:Stefan.Goeman@siemens.atea.be> 
> 
> Mobile Solutions 
> and Enabling Services
> http://www.ic.siemens.be <http://www.ic.siemens.be/eng/default_rd.shtm>
> 
> Customer driven solution providers 
> 
> 

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



From pana-admin@ietf.org  Thu May 13 14:34:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03814
	for <pana-archive@lists.ietf.org>; Thu, 13 May 2004 14:34:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOKrJ-0004wy-DR; Thu, 13 May 2004 14:23:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOKZV-0005MU-71
	for pana@optimus.ietf.org; Thu, 13 May 2004 14:04:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29978
	for <pana@ietf.org>; Thu, 13 May 2004 14:04:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOKZS-0001j7-Qs
	for pana@ietf.org; Thu, 13 May 2004 14:04:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOKWX-0000K2-00
	for pana@ietf.org; Thu, 13 May 2004 14:01:38 -0400
Received: from dmzraw2.extranet.tce.com ([157.254.234.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOKTJ-0006bd-00
	for pana@ietf.org; Thu, 13 May 2004 13:58:17 -0400
Received: from smtprelay2.indy.tce.com ([157.254.96.95])
	by dmzraw2.extranet.tce.com (8.12.5/8.12.5) with ESMTP id i4DHvjAX001067;
	Thu, 13 May 2004 17:57:46 GMT
Received: from indymsxcs01.am.thmulti.com (localhost [127.0.0.1])
	by smtprelay2.indy.tce.com (8.12.9/8.12.8) with ESMTP id i4DHuYjc024118;
	Thu, 13 May 2004 17:57:39 GMT
Received: from mail pickup service by indymsxcs01.am.thmulti.com with Microsoft SMTPSVC; Thu, 13 May 2004 11:00:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Received: from smtprelay2.indy.tce.com ([157.254.96.95]) by indymsxcs01.am.thmulti.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 May 2004 09:06:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Received: from dmzraw1.extranet.tce.com (localhost [127.0.0.1]) by smtprelay2.indy.tce.com (8.12.9/8.12.8) with ESMTP id i4DE6ajQ007507 for <guillaume.bichot@thomson.net>; Thu, 13 May 2004 14:06:36 GMT
Received: from optimus.ietf.org (datatracker.ietf.org [132.151.6.22]) by dmzraw1.extranet.tce.com (8.12.5/8.12.5) with ESMTP id i4DE6YUE026417 for <guillaume.bichot@thomson.net>; Thu, 13 May 2004 14:06:36 GMT
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGhs-0006pe-TB; Thu, 13 May 2004 09:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGfw-0006Ml-00 for pana@optimus.ietf.org; Thu, 13 May 2004 09:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13067 for <pana@ietf.org>; Thu, 13 May 2004 09:55:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOGfu-0000QZ-3p for pana@ietf.org; Thu, 13 May 2004 09:55:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOGex-0007fM-00 for pana@ietf.org; Thu, 13 May 2004 09:54:04 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx with esmtp (Exim 4.12) id 1BOGe0-0006aZ-00 for pana@ietf.org; Thu, 13 May 2004 09:53:04 -0400
Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 281A31CD6; Thu, 13 May 2004 15:52:32 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253]) by smtp.um.es (Postfix) with ESMTP id E455D1817; Thu, 13 May 2004 15:52:31 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47]) by aries.dif.um.es (Postfix) with ESMTP id DBA3514431; Thu, 13 May 2004 15:51:47 +0200 (MET DST)
Content-class: urn:content-classes:message
Subject: Re: [Pana] [framework] simplying WLAN section
Date: Thu, 13 May 2004 08:49:38 -0500
Message-ID: <40A37CF2.70503@dif.um.es>
Thread-Topic: [Pana] [framework] simplying WLAN section
thread-index: AcQ5BjLfXt8GNQMZSR6bVY8qCp8ABQ==
From: "Rafael Marin Lopez" <rafa@dif.um.es>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Mohan Parthasarathy" <mohanp@sbcglobal.net>, <pana@ietf.org>
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=AWL 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 Yoshihiro

I had a similar doubt... now it is clear... Then text you wrote is good
for me...

Regard...




Yoshihiro Ohba wrote:

>On Wed, May 12, 2004 at 04:43:23PM -0700, Mohan Parthasarathy wrote:
> =20
>
>> Yoshi,
>>
>>
>>   =20
>>
>>>I have checked the latest version of IEEE 802.11i/D10.0, and I =
noticed
>>>that higher-layer data traffic that is optionally allowed to be
>>>received and processed on IEEE 802.1X Uncontrolled Ports does not =
have
>>>to be terminated between stations (including AP).  Specifically, the
>>>following note in section 8.4.10.1 of IEEE 802.11i/D7.0 was removed
>>>from D10.0:
>>>
>>>   Informative Note: STAs may optionally receive frames other than
>>>     =20
>>>
>>I am a bit confused by this statement. If this note was removed in the =
latest draft does it not
>>mean that "STAs may not receive frames other than IEEE802.1x messages" =
i.e till
>>version 7.0 there was a possibility that messages other than =
IEEE802.1x may be
>>received and terminated at the application layer, but with 10.0, it =
can no longer
>>receive and would be dropped before the application sees it. If so, it =
would mean
>>that PANA messages won't be received.  What am i missing ?=20
>>   =20
>>

>In other section of D10.0, it says that:
>
>	Within an RSN, this is different. In an RSNA the IEEE 802.1X
>	Port determines when to allow data traffic across an IEEE
>	802.11 link. A single IEEE 802.1X Port maps to one association
>	and each association maps to an IEEE 802.1X Port. An IEEE
>	802.1X Port consists of an IEEE 802.1X Controlled Port and an
>	IEEE 802.1X Uncontrolled Port. The IEEE 802.1X Controlled Port
>	is blocked from passing general data traffic between two STAs
>	until an IEEE 802.1X authentication procedure completes
>	successfully over the IEEE 802.1X Uncontrolled Port. Once the
>	AKM completes successfully, data protection is enabled to
>	prevent unauthorized access, and the IEEE 802.1X Controlled
>	Port unblocks to allow protected Data traffic. IEEE 802.1X
>	Supplicants and Authenticators exchange protocol information
>	via the IEEE 802.1X Uncontrolled Port. It is expected that
>	most other protocol exchanges will make use of the IEEE 802.1X
>	Controlled Ports.  However, a given protocol may need to
>	bypass the authorization function and make use of the IEEE
>	802.1X Uncontrolled Port.
>
>This means some application traffic can be processed over 802.1X
>Uncontrolled Port.  So the removal of the informative note means that
>the restriction of PANA traffic termination at an RSN-enabled AP was
>removed.
>
>Yoshihiro Ohba
>
>
> =20
>
>>-mohan
>>
>>   IEEE 802.1X messages in unprotected data MPDUs destined for the
>>   IEEE 802.1X Authenticator's Uncontrolled Port at any time, with the
>>   caveat that any protocol utilizing this mechanism should provide
>>   cryptographic data protection mechanisms, suitable for the intended
>>   application or usage, within the protocol itself.  These frames are
>>   never forwarded to or from the DS, but terminate at an application
>>   level service, such as a captive portal, on the AP.  This usage is
>>   outside the scope of this standard.
>>
>>This means that in the PANA framework document, (virtual) AP hopping
>>operation described in 10.2.2.1 is not needed anymore when AP and PAA
>>are separated, and thus the same operation that was defined for
>>co-located AP and PAA is now applicable to the separate AP and PAA
>>case.
>>
>>
>>   =20
>>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
> =20
>


--=20
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


_______________________________________________
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 May 14 08:15:58 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17481
	for <pana-archive@lists.ietf.org>; Fri, 14 May 2004 08:15:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObVp-0004r7-Cl; Fri, 14 May 2004 08:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObSD-0003ph-Uu
	for pana@optimus.ietf.org; Fri, 14 May 2004 08:06:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16926
	for <pana@ietf.org>; Fri, 14 May 2004 08:06:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BObSC-0002zF-Vf
	for pana@ietf.org; Fri, 14 May 2004 08:06:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BObRA-0002UO-00
	for pana@ietf.org; Fri, 14 May 2004 08:05:13 -0400
Received: from e34.co.us.ibm.com ([32.97.110.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BObQA-0001Ui-00
	for pana@ietf.org; Fri, 14 May 2004 08:04:10 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e34.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i4EC3dWv499990;
	Fri, 14 May 2004 08:03:39 -0400
Received: from cichlid.raleigh.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i4EC3aGR152332;
	Fri, 14 May 2004 06:03:37 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.12.10/8.12.5) with ESMTP id i4EC39Oc022824;
	Fri, 14 May 2004 08:03:09 -0400
Received: from cichlid.raleigh.ibm.com (narten@localhost)
	by cichlid.raleigh.ibm.com (8.12.10/8.12.10/Submit) with ESMTP id i4EC36SN022819;
	Fri, 14 May 2004 08:03:08 -0400
Message-Id: <200405141203.i4EC36SN022819@cichlid.raleigh.ibm.com>
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
cc: "Goeman Stefan" <Stefan.Goeman@siemens.com>, pana@ietf.org
Subject: Re: [Pana] PANA - link local address - duplicate address detection 
In-Reply-To: Message from mohanp@sbcglobal.net
   of "Thu, 13 May 2004 09:36:19 PDT." <008501c43908$6eac8c60$861167c0@adithya> 
Date: Fri, 14 May 2004 08:03:05 -0400
From: Thomas Narten <narten@us.ibm.com>
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>

> Please see this draft 
> http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt

> The originator of the DAD also gets the DAD packet and the link
> layer seems to drop the packet. i.e Duplicate address is not
> detected today in IPv6 with wlans.

I think this is a misreading of the problem statement. The above draft
basically says that if two nodes are using the same MAC (i.e,
link-layer) address, DAD doesn't work. Surprise surprise. If there are
two nodes in your network using the same link-layer address, there are
probably a bunch of things that don't work anymore, DAD being just one
example. But your last statement above seems rather strong.

> If this problem gets fixed, then this DoS attack can happen and PANA
> cannot stop it and also it is not in the scope of PANA to stop it.

PANA cannot prevent all DOS attacks. I know of no protocol that can.

Thomas

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


From exim@www1.ietf.org  Fri May 14 08:33:17 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18082
	for <pana-archive@odin.ietf.org>; Fri, 14 May 2004 08:33:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObiy-0007Py-Hh
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 08:23:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ECNaZD028515
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 08:23:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObcc-0006GH-Mc
	for pana-web-archive@optimus.ietf.org; Fri, 14 May 2004 08:17:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17540
	for <pana-web-archive@ietf.org>; Fri, 14 May 2004 08:17:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BObcb-0000jR-MX
	for pana-web-archive@ietf.org; Fri, 14 May 2004 08:17:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BObbc-0000FV-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 08:16:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BObb7-0007ZI-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 08:15:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObVp-0004r7-Cl; Fri, 14 May 2004 08:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BObSD-0003ph-Uu
	for pana@optimus.ietf.org; Fri, 14 May 2004 08:06:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16926
	for <pana@ietf.org>; Fri, 14 May 2004 08:06:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BObSC-0002zF-Vf
	for pana@ietf.org; Fri, 14 May 2004 08:06:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BObRA-0002UO-00
	for pana@ietf.org; Fri, 14 May 2004 08:05:13 -0400
Received: from e34.co.us.ibm.com ([32.97.110.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BObQA-0001Ui-00
	for pana@ietf.org; Fri, 14 May 2004 08:04:10 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e34.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i4EC3dWv499990;
	Fri, 14 May 2004 08:03:39 -0400
Received: from cichlid.raleigh.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i4EC3aGR152332;
	Fri, 14 May 2004 06:03:37 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.12.10/8.12.5) with ESMTP id i4EC39Oc022824;
	Fri, 14 May 2004 08:03:09 -0400
Received: from cichlid.raleigh.ibm.com (narten@localhost)
	by cichlid.raleigh.ibm.com (8.12.10/8.12.10/Submit) with ESMTP id i4EC36SN022819;
	Fri, 14 May 2004 08:03:08 -0400
Message-Id: <200405141203.i4EC36SN022819@cichlid.raleigh.ibm.com>
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
cc: "Goeman Stefan" <Stefan.Goeman@siemens.com>, pana@ietf.org
Subject: Re: [Pana] PANA - link local address - duplicate address detection 
In-Reply-To: Message from mohanp@sbcglobal.net
   of "Thu, 13 May 2004 09:36:19 PDT." <008501c43908$6eac8c60$861167c0@adithya> 
Date: Fri, 14 May 2004 08:03:05 -0400
From: Thomas Narten <narten@us.ibm.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>
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

> Please see this draft 
> http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt

> The originator of the DAD also gets the DAD packet and the link
> layer seems to drop the packet. i.e Duplicate address is not
> detected today in IPv6 with wlans.

I think this is a misreading of the problem statement. The above draft
basically says that if two nodes are using the same MAC (i.e,
link-layer) address, DAD doesn't work. Surprise surprise. If there are
two nodes in your network using the same link-layer address, there are
probably a bunch of things that don't work anymore, DAD being just one
example. But your last statement above seems rather strong.

> If this problem gets fixed, then this DoS attack can happen and PANA
> cannot stop it and also it is not in the scope of PANA to stop it.

PANA cannot prevent all DOS attacks. I know of no protocol that can.

Thomas

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



From pana-admin@ietf.org  Fri May 14 13:28:45 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07037
	for <pana-archive@lists.ietf.org>; Fri, 14 May 2004 13:28:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgMp-0007Kb-G8; Fri, 14 May 2004 13:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgGM-0005gb-IF
	for pana@optimus.ietf.org; Fri, 14 May 2004 13:14:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05976
	for <pana@ietf.org>; Fri, 14 May 2004 13:14:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOgGK-0005wI-H2
	for pana@ietf.org; Fri, 14 May 2004 13:14:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOgFJ-0005Rw-00
	for pana@ietf.org; Fri, 14 May 2004 13:13:18 -0400
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOgEd-0004xn-00
	for pana@ietf.org; Fri, 14 May 2004 13:12:35 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp803.mail.sc5.yahoo.com with SMTP; 14 May 2004 17:12:33 -0000
Message-ID: <003201c439d6$a5d46040$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Thomas Narten" <narten@us.ibm.com>
Cc: "Goeman Stefan" <Stefan.Goeman@siemens.com>, <pana@ietf.org>
References: <200405141203.i4EC36SN022819@cichlid.raleigh.ibm.com>
Subject: Re: [Pana] PANA - link local address - duplicate address detection 
Date: Fri, 14 May 2004 10:12:33 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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


 Thomas,

Some clarification below.


> > Please see this draft 
> > http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt
> 
> > The originator of the DAD also gets the DAD packet and the link
> > layer seems to drop the packet. i.e Duplicate address is not
> > detected today in IPv6 with wlans.
> 
> I think this is a misreading of the problem statement. The above draft
> basically says that if two nodes are using the same MAC (i.e,
> link-layer) address, DAD doesn't work. Surprise surprise. If there are
> two nodes in your network using the same link-layer address, there are
> probably a bunch of things that don't work anymore, DAD being just one
> example. But your last statement above seems rather strong.
> 
If there are two nodes with the same MAC address on a wired ethernet, DAD would
have detected the duplicated address assuming both the nodes auto-configure the
address using the MAC address ? The first step you do is to configure a link-local address
and do a DAD on it before doing anything else on the network. So, when the second
node with the same MAC address configures the link-local address, it should detect the
duplicate if it is wired ethernet as the switch does not send back the DAD packet back
on the same port on which it was sent. This fails to work on the WLANs. Is that
the right understanding ? I agree that the last statement of mine was too strong. DAD can
be detected if other address configuration mechanisms are used and hence
the DAD attack is still possible.  Is that what you meant ?

> > If this problem gets fixed, then this DoS attack can happen and PANA
> > cannot stop it and also it is not in the scope of PANA to stop it.
> 
> PANA cannot prevent all DOS attacks. I know of no protocol that can.
> 
Agreed. I was specifically talking about DAD and i don't know what exactly SEND did with it.

-mohan

> Thomas
> 
> _______________________________________________
> 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 May 14 13:41:21 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07741
	for <pana-archive@odin.ietf.org>; Fri, 14 May 2004 13:41:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgdf-0002pN-RR
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 13:38:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EHcRwS010869
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 13:38:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgW3-0000y9-Pe
	for pana-web-archive@optimus.ietf.org; Fri, 14 May 2004 13:30:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07145
	for <pana-web-archive@ietf.org>; Fri, 14 May 2004 13:30:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOgW1-0006RC-PZ
	for pana-web-archive@ietf.org; Fri, 14 May 2004 13:30:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOgUr-0005tD-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 13:29:22 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOgTo-0005Mf-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 13:28:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgMp-0007Kb-G8; Fri, 14 May 2004 13:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOgGM-0005gb-IF
	for pana@optimus.ietf.org; Fri, 14 May 2004 13:14:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05976
	for <pana@ietf.org>; Fri, 14 May 2004 13:14:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOgGK-0005wI-H2
	for pana@ietf.org; Fri, 14 May 2004 13:14:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOgFJ-0005Rw-00
	for pana@ietf.org; Fri, 14 May 2004 13:13:18 -0400
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOgEd-0004xn-00
	for pana@ietf.org; Fri, 14 May 2004 13:12:35 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp803.mail.sc5.yahoo.com with SMTP; 14 May 2004 17:12:33 -0000
Message-ID: <003201c439d6$a5d46040$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Thomas Narten" <narten@us.ibm.com>
Cc: "Goeman Stefan" <Stefan.Goeman@siemens.com>, <pana@ietf.org>
References: <200405141203.i4EC36SN022819@cichlid.raleigh.ibm.com>
Subject: Re: [Pana] PANA - link local address - duplicate address detection 
Date: Fri, 14 May 2004 10:12:33 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


 Thomas,

Some clarification below.


> > Please see this draft 
> > http://www.join.uni-muenster.de/Dokumente/drafts/draft-park-ipv6-dad-problem-wlan-00.txt
> 
> > The originator of the DAD also gets the DAD packet and the link
> > layer seems to drop the packet. i.e Duplicate address is not
> > detected today in IPv6 with wlans.
> 
> I think this is a misreading of the problem statement. The above draft
> basically says that if two nodes are using the same MAC (i.e,
> link-layer) address, DAD doesn't work. Surprise surprise. If there are
> two nodes in your network using the same link-layer address, there are
> probably a bunch of things that don't work anymore, DAD being just one
> example. But your last statement above seems rather strong.
> 
If there are two nodes with the same MAC address on a wired ethernet, DAD would
have detected the duplicated address assuming both the nodes auto-configure the
address using the MAC address ? The first step you do is to configure a link-local address
and do a DAD on it before doing anything else on the network. So, when the second
node with the same MAC address configures the link-local address, it should detect the
duplicate if it is wired ethernet as the switch does not send back the DAD packet back
on the same port on which it was sent. This fails to work on the WLANs. Is that
the right understanding ? I agree that the last statement of mine was too strong. DAD can
be detected if other address configuration mechanisms are used and hence
the DAD attack is still possible.  Is that what you meant ?

> > If this problem gets fixed, then this DoS attack can happen and PANA
> > cannot stop it and also it is not in the scope of PANA to stop it.
> 
> PANA cannot prevent all DOS attacks. I know of no protocol that can.
> 
Agreed. I was specifically talking about DAD and i don't know what exactly SEND did with it.

-mohan

> Thomas
> 
> _______________________________________________
> 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 May 14 19:25:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05855
	for <pana-archive@lists.ietf.org>; Fri, 14 May 2004 19:25:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOlrj-0007iF-VI; Fri, 14 May 2004 19:13:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOlhF-0005Tw-Gm
	for pana@optimus.ietf.org; Fri, 14 May 2004 19:02:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04967
	for <pana@ietf.org>; Fri, 14 May 2004 19:02:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOlhC-0003vP-7t
	for pana@ietf.org; Fri, 14 May 2004 19:02:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOlgB-0003Ot-00
	for pana@ietf.org; Fri, 14 May 2004 19:01:23 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOley-0002R2-00
	for pana@ietf.org; Fri, 14 May 2004 19:00:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4EMxtgH028432;
	Sat, 15 May 2004 07:59:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4EMxt2K018950;
	Sat, 15 May 2004 07:59:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA18948 ; Sat, 15 May 2004 07:59:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA10635; Sat, 15 May 2004 07:59:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA08288; Sat, 15 May 2004 07:59:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4EMxrEU022886;
	Sat, 15 May 2004 07:59:54 +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 <0HXQ00KU37VRDT@tsbpo1.po.toshiba.co.jp>; Sat,
 15 May 2004 07:59:53 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BOle3-0006NG-00; Fri, 14 May 2004 15:59:11 -0700
Date: Fri, 14 May 2004 15:59:11 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040514225911.GB22808@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] issue85 (question)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

As a result of recent discussion, I am preparing for adding new
messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
the PAA know the POPA of the PaC.

I have one question: Are these messages need to be integrity
protected?

I think the answer is yes in general, to prevent the host route to a
legitimate PaC from being altered by an attacker.  On the other hand,
this means that an EAP method that can generate keys would be needed
even for networks (e.g., DSL) that are secured by lower-layers.

Since there is an address ownership issue with regard to POPA, which
cannot be solved by integrity protecting the POPA update messages and
needs a mechanism outside the PANA protocol, I am wondering if the
POPA update procedure really needs to be integrity protected.

Opinions?

Yoshihiro Ohba

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


From exim@www1.ietf.org  Fri May 14 19:35:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06360
	for <pana-archive@odin.ietf.org>; Fri, 14 May 2004 19:35:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOmCH-0004Qp-Ag
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 19:34:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ENYXu1017035
	for pana-archive@odin.ietf.org; Fri, 14 May 2004 19:34:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOm5t-00030C-Ew
	for pana-web-archive@optimus.ietf.org; Fri, 14 May 2004 19:27:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05921
	for <pana-web-archive@ietf.org>; Fri, 14 May 2004 19:27:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOm5r-0000Hh-Sj
	for pana-web-archive@ietf.org; Fri, 14 May 2004 19:27:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOm4Y-0007Vp-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 19:26:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOm3V-00070B-00
	for pana-web-archive@ietf.org; Fri, 14 May 2004 19:25:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOlrj-0007iF-VI; Fri, 14 May 2004 19:13:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOlhF-0005Tw-Gm
	for pana@optimus.ietf.org; Fri, 14 May 2004 19:02:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04967
	for <pana@ietf.org>; Fri, 14 May 2004 19:02:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOlhC-0003vP-7t
	for pana@ietf.org; Fri, 14 May 2004 19:02:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOlgB-0003Ot-00
	for pana@ietf.org; Fri, 14 May 2004 19:01:23 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOley-0002R2-00
	for pana@ietf.org; Fri, 14 May 2004 19:00:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4EMxtgH028432;
	Sat, 15 May 2004 07:59:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4EMxt2K018950;
	Sat, 15 May 2004 07:59:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA18948 ; Sat, 15 May 2004 07:59:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA10635; Sat, 15 May 2004 07:59:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA08288; Sat, 15 May 2004 07:59:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4EMxrEU022886;
	Sat, 15 May 2004 07:59:54 +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 <0HXQ00KU37VRDT@tsbpo1.po.toshiba.co.jp>; Sat,
 15 May 2004 07:59:53 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BOle3-0006NG-00; Fri, 14 May 2004 15:59:11 -0700
Date: Fri, 14 May 2004 15:59:11 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040514225911.GB22808@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
Subject: [Pana] issue85 (question)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60

As a result of recent discussion, I am preparing for adding new
messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
the PAA know the POPA of the PaC.

I have one question: Are these messages need to be integrity
protected?

I think the answer is yes in general, to prevent the host route to a
legitimate PaC from being altered by an attacker.  On the other hand,
this means that an EAP method that can generate keys would be needed
even for networks (e.g., DSL) that are secured by lower-layers.

Since there is an address ownership issue with regard to POPA, which
cannot be solved by integrity protecting the POPA update messages and
needs a mechanism outside the PANA protocol, I am wondering if the
POPA update procedure really needs to be integrity protected.

Opinions?

Yoshihiro Ohba

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



From pana-admin@ietf.org  Mon May 17 14:38:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12981
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 14:38:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPmtC-0000s2-2G; Mon, 17 May 2004 14:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPme5-0006jr-8J
	for pana@optimus.ietf.org; Mon, 17 May 2004 14:15:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10206
	for <pana@ietf.org>; Mon, 17 May 2004 14:15:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPme2-0004iD-QD
	for pana@ietf.org; Mon, 17 May 2004 14:15:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPmd2-0004L4-00
	for pana@ietf.org; Mon, 17 May 2004 14:14:20 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPmc1-0003bu-00
	for pana@ietf.org; Mon, 17 May 2004 14:13:17 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXV00K01EL94X@mailout1.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 03:12:45 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXV00ENBEL9LE@mailout1.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 03:12:45 +0900 (KST)
Received: from Alperyegin ([105.253.155.18])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXV00J9NEL6F8@mmp1.samsung.com> for pana@ietf.org;
 Tue, 18 May 2004 03:12:45 +0900 (KST)
Date: Mon, 17 May 2004 11:12:43 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (question)
In-reply-to: <20040514225911.GB22808@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <001c01c43c3a$8e100200$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

> As a result of recent discussion, I am preparing for adding new
> messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> the PAA know the POPA of the PaC.

Semantically what PAA should learn is an IP address of the PaC, right?
Not necessarily "POPA". If so, we might consider using a more generic
name, that doesn't refer to "POPA" in the name.

> 
> I have one question: Are these messages need to be integrity
> protected?
> 
> I think the answer is yes in general, to prevent the host route to a
> legitimate PaC from being altered by an attacker.  On the other hand,
> this means that an EAP method that can generate keys would be needed
> even for networks (e.g., DSL) that are secured by lower-layers.
> 

When there is a PANA SA, we must use it I think. If there is not, that's
OK too. This is aligned with the rest of the protocol design.

In physically secured networks, operator doesn't have to use a
key-generating EAP method, hence there might not be a PANA SA.

Alper

> Since there is an address ownership issue with regard to POPA, which
> cannot be solved by integrity protecting the POPA update messages and
> needs a mechanism outside the PANA protocol, I am wondering if the
> POPA update procedure really needs to be integrity protected.
> 
> Opinions?
> 
> 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 May 17 14:52:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14248
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 14:52:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn9L-00049y-CT
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 14:47:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HIlhog015986
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 14:47:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn2Q-0002ku-9L
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 14:40:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13145
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 14:40:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPn2N-00066H-Hv
	for pana-web-archive@ietf.org; Mon, 17 May 2004 14:40:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn1U-0005ia-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 14:39:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn0J-0005Jo-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 14:38:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPmtC-0000s2-2G; Mon, 17 May 2004 14:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPme5-0006jr-8J
	for pana@optimus.ietf.org; Mon, 17 May 2004 14:15:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10206
	for <pana@ietf.org>; Mon, 17 May 2004 14:15:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPme2-0004iD-QD
	for pana@ietf.org; Mon, 17 May 2004 14:15:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPmd2-0004L4-00
	for pana@ietf.org; Mon, 17 May 2004 14:14:20 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPmc1-0003bu-00
	for pana@ietf.org; Mon, 17 May 2004 14:13:17 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXV00K01EL94X@mailout1.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 03:12:45 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXV00ENBEL9LE@mailout1.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 03:12:45 +0900 (KST)
Received: from Alperyegin ([105.253.155.18])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXV00J9NEL6F8@mmp1.samsung.com> for pana@ietf.org;
 Tue, 18 May 2004 03:12:45 +0900 (KST)
Date: Mon, 17 May 2004 11:12:43 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (question)
In-reply-to: <20040514225911.GB22808@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <001c01c43c3a$8e100200$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

> As a result of recent discussion, I am preparing for adding new
> messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> the PAA know the POPA of the PaC.

Semantically what PAA should learn is an IP address of the PaC, right?
Not necessarily "POPA". If so, we might consider using a more generic
name, that doesn't refer to "POPA" in the name.

> 
> I have one question: Are these messages need to be integrity
> protected?
> 
> I think the answer is yes in general, to prevent the host route to a
> legitimate PaC from being altered by an attacker.  On the other hand,
> this means that an EAP method that can generate keys would be needed
> even for networks (e.g., DSL) that are secured by lower-layers.
> 

When there is a PANA SA, we must use it I think. If there is not, that's
OK too. This is aligned with the rest of the protocol design.

In physically secured networks, operator doesn't have to use a
key-generating EAP method, hence there might not be a PANA SA.

Alper

> Since there is an address ownership issue with regard to POPA, which
> cannot be solved by integrity protecting the POPA update messages and
> needs a mechanism outside the PANA protocol, I am wondering if the
> POPA update procedure really needs to be integrity protected.
> 
> Opinions?
> 
> 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 May 17 15:45:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19307
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 15:45:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnbh-0006IR-A3; Mon, 17 May 2004 15:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnPO-0003QZ-3M
	for pana@optimus.ietf.org; Mon, 17 May 2004 15:04:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15083
	for <pana@ietf.org>; Mon, 17 May 2004 15:04:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPnPL-0007D7-3H
	for pana@ietf.org; Mon, 17 May 2004 15:04:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPnOL-0006sB-00
	for pana@ietf.org; Mon, 17 May 2004 15:03:14 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPnNQ-0006F0-00
	for pana@ietf.org; Mon, 17 May 2004 15:02:16 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id B81D718742; Mon, 17 May 2004 21:01:45 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id A008917FB7; Mon, 17 May 2004 21:01:45 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 5499E14426; Mon, 17 May 2004 21:00:58 +0200 (MET DST)
Message-ID: <40A90B6B.5080502@dif.um.es>
Date: Mon, 17 May 2004 20:58:51 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Subject: Re: [Pana] issue85 (question)
References: <20040514225911.GB22808@steelhead>
In-Reply-To: <20040514225911.GB22808@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
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=AWL 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

Yoshihiro Ohba wrote:

>As a result of recent discussion, I am preparing for adding new
>messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
>the PAA know the POPA of the PaC.
>
>I have one question: Are these messages need to be integrity
>protected?
>
>I think the answer is yes in general, to prevent the host route to a
>legitimate PaC from being altered by an attacker.  On the other hand,
>this means that an EAP method that can generate keys would be needed
>even for networks (e.g., DSL) that are secured by lower-layers.
>
>Since there is an address ownership issue with regard to POPA, which
>cannot be solved by integrity protecting the POPA update messages and
>needs a mechanism outside the PANA protocol, I am wondering if the
>POPA update procedure really needs to be integrity protected.
>  
>
In my opinion , PANA SA should be used when it exists . In another case,
when networks are not secured by low-layers, a man-in-the-middle could
modify this PANA-POPA-Update-Request. If PANA SA is used, I think PAA
could know attacker is same PaC which is sending
PANA-POPA-Update-Request. But if it is not used , PAA could not know if
attacker is an PaC sending POPA Update or a man-in-the-middle element.

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


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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


From exim@www1.ietf.org  Mon May 17 17:05:47 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27525
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 17:05:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPoHi-0003XO-Ro
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 16:00:27 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HK0Qfe013599
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 16:00:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPo64-0007fg-8A
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 15:48:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19449
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 15:48:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPo62-0007VY-5K
	for pana-web-archive@ietf.org; Mon, 17 May 2004 15:48:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPo4r-0006xi-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 15:47:10 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPo2y-0006G2-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 15:45:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnbh-0006IR-A3; Mon, 17 May 2004 15:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnPO-0003QZ-3M
	for pana@optimus.ietf.org; Mon, 17 May 2004 15:04:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15083
	for <pana@ietf.org>; Mon, 17 May 2004 15:04:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPnPL-0007D7-3H
	for pana@ietf.org; Mon, 17 May 2004 15:04:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPnOL-0006sB-00
	for pana@ietf.org; Mon, 17 May 2004 15:03:14 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPnNQ-0006F0-00
	for pana@ietf.org; Mon, 17 May 2004 15:02:16 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id B81D718742; Mon, 17 May 2004 21:01:45 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id A008917FB7; Mon, 17 May 2004 21:01:45 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 5499E14426; Mon, 17 May 2004 21:00:58 +0200 (MET DST)
Message-ID: <40A90B6B.5080502@dif.um.es>
Date: Mon, 17 May 2004 20:58:51 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Subject: Re: [Pana] issue85 (question)
References: <20040514225911.GB22808@steelhead>
In-Reply-To: <20040514225911.GB22808@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yoshihiro Ohba wrote:

>As a result of recent discussion, I am preparing for adding new
>messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
>the PAA know the POPA of the PaC.
>
>I have one question: Are these messages need to be integrity
>protected?
>
>I think the answer is yes in general, to prevent the host route to a
>legitimate PaC from being altered by an attacker.  On the other hand,
>this means that an EAP method that can generate keys would be needed
>even for networks (e.g., DSL) that are secured by lower-layers.
>
>Since there is an address ownership issue with regard to POPA, which
>cannot be solved by integrity protecting the POPA update messages and
>needs a mechanism outside the PANA protocol, I am wondering if the
>POPA update procedure really needs to be integrity protected.
>  
>
In my opinion , PANA SA should be used when it exists . In another case,
when networks are not secured by low-layers, a man-in-the-middle could
modify this PANA-POPA-Update-Request. If PANA SA is used, I think PAA
could know attacker is same PaC which is sending
PANA-POPA-Update-Request. But if it is not used , PAA could not know if
attacker is an PaC sending POPA Update or a man-in-the-middle element.

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


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From pana-admin@ietf.org  Mon May 17 17:16:43 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29285
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 17:16:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPobd-00037k-Qb; Mon, 17 May 2004 16:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPo85-0008JH-Ls
	for pana@optimus.ietf.org; Mon, 17 May 2004 15:50:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19797
	for <pana@ietf.org>; Mon, 17 May 2004 15:50:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPo83-0000Ma-CR
	for pana@ietf.org; Mon, 17 May 2004 15:50:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPo6f-0007b4-00
	for pana@ietf.org; Mon, 17 May 2004 15:49:01 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPo5L-00078j-00
	for pana@ietf.org; Mon, 17 May 2004 15:47:39 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4HJlbgH007799;
	Tue, 18 May 2004 04:47:37 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4HJlbwY024172;
	Tue, 18 May 2004 04:47:37 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA24171 ; Tue, 18 May 2004 04:47:37 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA09524; Tue, 18 May 2004 04:47:36 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA28568; Tue, 18 May 2004 04:47:36 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4HJlaEU000302;
	Tue, 18 May 2004 04:47:36 +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 <0HXV00KBIIZ8Z1@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 04:47:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BPo4D-0004lt-00; Mon, 17 May 2004 12:46:29 -0700
Date: Mon, 17 May 2004 12:46:29 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <001c01c43c3a$8e100200$c64ca143@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040517194629.GH8507@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6i
References: <20040514225911.GB22808@steelhead>
 <001c01c43c3a$8e100200$c64ca143@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Mon, May 17, 2004 at 11:12:43AM -0700, Alper Yegin wrote:
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> 
> Semantically what PAA should learn is an IP address of the PaC, right?
> Not necessarily "POPA". If so, we might consider using a more generic
> name, that doesn't refer to "POPA" in the name.

I used the term POPA because the issue starts from the issue of PRPA
to POPA update.  Do you have some other scenarios for the PAA needs to
learn an IP address of the PaC, or do we just use generic naming just
in case for other usages for this message exchange are found out?

> 
> > 
> > I have one question: Are these messages need to be integrity
> > protected?
> > 
> > I think the answer is yes in general, to prevent the host route to a
> > legitimate PaC from being altered by an attacker.  On the other hand,
> > this means that an EAP method that can generate keys would be needed
> > even for networks (e.g., DSL) that are secured by lower-layers.
> > 
> 
> When there is a PANA SA, we must use it I think. If there is not, that's
> OK too. This is aligned with the rest of the protocol design.

Hmm, according to the following text in section 4.4, PANA-Reauth
exchange always needs a PANA SA to exist (I think the occurence table
marking the MAC AVP as "0-1" is typo.)  So I don't think the protocol
design is completely aligned that way.

   "Both PANA-Reauth-Request/ PANA-Reauth-Answer
   messages MUST be protected with a MAC AVP."

> 
> In physically secured networks, operator doesn't have to use a
> key-generating EAP method, hence there might not be a PANA SA.


Or should we say "in physically secured networks, operator doesn't
have to use a key-generating EAP method except for PANA-Reauth
exchange"?

Yoshihiro Ohba




> 
> Alper
> 
> > Since there is an address ownership issue with regard to POPA, which
> > cannot be solved by integrity protecting the POPA update messages and
> > needs a mechanism outside the PANA protocol, I am wondering if the
> > POPA update procedure really needs to be integrity protected.
> > 
> > Opinions?
> > 
> > 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 May 17 17:37:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02577
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 17:37:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpT6-0002x7-Qn; Mon, 17 May 2004 17:16:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPoVS-0000Hk-QI
	for pana@optimus.ietf.org; Mon, 17 May 2004 16:14:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21896
	for <pana@ietf.org>; Mon, 17 May 2004 16:14:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPoVR-0001l7-22
	for pana@ietf.org; Mon, 17 May 2004 16:14:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPoTr-00018F-00
	for pana@ietf.org; Mon, 17 May 2004 16:13:00 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPoSi-0000Za-00
	for pana@ietf.org; Mon, 17 May 2004 16:11:48 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXV00901K2MIT@mailout2.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 05:11:10 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXV00ARJK2MJH@mailout2.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 05:11:10 +0900 (KST)
Received: from Alperyegin ([105.253.155.18])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXV006JCK2JEQ@mmp1.samsung.com> for pana@ietf.org;
 Tue, 18 May 2004 05:11:10 +0900 (KST)
Date: Mon, 17 May 2004 13:11:08 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (question)
In-reply-to: <20040517194629.GH8507@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Message-id: <003101c43c4b$18ec2740$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

> > > As a result of recent discussion, I am preparing for adding new 
> > > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to 
> > > let the PAA know the POPA of the PaC.
> >
> > Semantically what PAA should learn is an IP address of the PaC, 
> > right? Not necessarily "POPA". If so, we might consider using a more

> > generic name, that doesn't refer to "POPA" in the name.
> 
> I used the term POPA because the issue starts from the issue of PRPA 
> to POPA update.  Do you have some other scenarios for the PAA needs to

> learn an IP address of the PaC, or do we just use generic naming just 
> in case for other usages for this message exchange are found out?

Yes, it is the latter that I'm thinking. The PAA needs to know any
reachable IP address of the PaC, so that it can send a (solicited or
otherwise) message. The IP address does not get any special treatment as
a "POPA".  

> > > I have one question: Are these messages need to be integrity 
> > > protected?
> > >
> > > I think the answer is yes in general, to prevent the host route to

> > > a legitimate PaC from being altered by an attacker.  On the other 
> > > hand, this means that an EAP method that can generate keys would 
> > > be needed even for networks (e.g., DSL) that are secured by 
> > > lower-layers.
> > >
> >
> > When there is a PANA SA, we must use it I think. If there is not, 
> > that's OK too. This is aligned with the rest of the protocol design.
> 
> Hmm, according to the following text in section 4.4, PANA-Reauth 
> exchange always needs a PANA SA to exist (I think the occurence table 
> marking the MAC AVP as "0-1" is typo.)  So I don't think the protocol 
> design is completely aligned that way.
> 
>    "Both PANA-Reauth-Request/ PANA-Reauth-Answer
>    messages MUST be protected with a MAC AVP."

I think this is a bug. We don't want to limit the use of Reauth messages
to only when there is a PANA SA.

> > In physically secured networks, operator doesn't have to use a 
> > key-generating EAP method, hence there might not be a PANA SA.
> 
> 
> Or should we say "in physically secured networks, operator doesn't 
> have to use a key-generating EAP method except for PANA-Reauth 
> exchange"?

I think we can have Reauth run without a MAC AVP. 

Alper





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


From exim@www1.ietf.org  Mon May 17 17:56:17 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05488
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 17:56:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpsP-0000tI-Ui
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 17:42:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HLgPeV003420
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 17:42:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpcZ-0006YX-IC
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 17:26:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00689
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 17:26:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPpcX-00014h-8k
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:26:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPpXp-00005Z-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:21:11 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpT5-0006a5-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:16:15 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BPpT5-0002g9-TG
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:16:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPobd-00037k-Qb; Mon, 17 May 2004 16:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPo85-0008JH-Ls
	for pana@optimus.ietf.org; Mon, 17 May 2004 15:50:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19797
	for <pana@ietf.org>; Mon, 17 May 2004 15:50:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPo83-0000Ma-CR
	for pana@ietf.org; Mon, 17 May 2004 15:50:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPo6f-0007b4-00
	for pana@ietf.org; Mon, 17 May 2004 15:49:01 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPo5L-00078j-00
	for pana@ietf.org; Mon, 17 May 2004 15:47:39 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4HJlbgH007799;
	Tue, 18 May 2004 04:47:37 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4HJlbwY024172;
	Tue, 18 May 2004 04:47:37 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA24171 ; Tue, 18 May 2004 04:47:37 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA09524; Tue, 18 May 2004 04:47:36 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA28568; Tue, 18 May 2004 04:47:36 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4HJlaEU000302;
	Tue, 18 May 2004 04:47:36 +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 <0HXV00KBIIZ8Z1@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 04:47:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BPo4D-0004lt-00; Mon, 17 May 2004 12:46:29 -0700
Date: Mon, 17 May 2004 12:46:29 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <001c01c43c3a$8e100200$c64ca143@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040517194629.GH8507@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6i
References: <20040514225911.GB22808@steelhead>
 <001c01c43c3a$8e100200$c64ca143@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 17, 2004 at 11:12:43AM -0700, Alper Yegin wrote:
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> 
> Semantically what PAA should learn is an IP address of the PaC, right?
> Not necessarily "POPA". If so, we might consider using a more generic
> name, that doesn't refer to "POPA" in the name.

I used the term POPA because the issue starts from the issue of PRPA
to POPA update.  Do you have some other scenarios for the PAA needs to
learn an IP address of the PaC, or do we just use generic naming just
in case for other usages for this message exchange are found out?

> 
> > 
> > I have one question: Are these messages need to be integrity
> > protected?
> > 
> > I think the answer is yes in general, to prevent the host route to a
> > legitimate PaC from being altered by an attacker.  On the other hand,
> > this means that an EAP method that can generate keys would be needed
> > even for networks (e.g., DSL) that are secured by lower-layers.
> > 
> 
> When there is a PANA SA, we must use it I think. If there is not, that's
> OK too. This is aligned with the rest of the protocol design.

Hmm, according to the following text in section 4.4, PANA-Reauth
exchange always needs a PANA SA to exist (I think the occurence table
marking the MAC AVP as "0-1" is typo.)  So I don't think the protocol
design is completely aligned that way.

   "Both PANA-Reauth-Request/ PANA-Reauth-Answer
   messages MUST be protected with a MAC AVP."

> 
> In physically secured networks, operator doesn't have to use a
> key-generating EAP method, hence there might not be a PANA SA.


Or should we say "in physically secured networks, operator doesn't
have to use a key-generating EAP method except for PANA-Reauth
exchange"?

Yoshihiro Ohba




> 
> Alper
> 
> > Since there is an address ownership issue with regard to POPA, which
> > cannot be solved by integrity protecting the POPA update messages and
> > needs a mechanism outside the PANA protocol, I am wondering if the
> > POPA update procedure really needs to be integrity protected.
> > 
> > Opinions?
> > 
> > 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 May 17 18:13:22 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07700
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 18:13:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPq9K-00013y-SZ
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 17:59:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HLxsAu004082
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 17:59:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpyD-0003HD-Io
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 17:48:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04007
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 17:48:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPpyB-0007M2-5L
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:48:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPptD-000671-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:43:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpnH-0004cN-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 17:37:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpT6-0002x7-Qn; Mon, 17 May 2004 17:16:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPoVS-0000Hk-QI
	for pana@optimus.ietf.org; Mon, 17 May 2004 16:14:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21896
	for <pana@ietf.org>; Mon, 17 May 2004 16:14:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPoVR-0001l7-22
	for pana@ietf.org; Mon, 17 May 2004 16:14:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPoTr-00018F-00
	for pana@ietf.org; Mon, 17 May 2004 16:13:00 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPoSi-0000Za-00
	for pana@ietf.org; Mon, 17 May 2004 16:11:48 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HXV00901K2MIT@mailout2.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 05:11:10 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HXV00ARJK2MJH@mailout2.samsung.com> for pana@ietf.org; Tue,
 18 May 2004 05:11:10 +0900 (KST)
Received: from Alperyegin ([105.253.155.18])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HXV006JCK2JEQ@mmp1.samsung.com> for pana@ietf.org;
 Tue, 18 May 2004 05:11:10 +0900 (KST)
Date: Mon, 17 May 2004 13:11:08 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (question)
In-reply-to: <20040517194629.GH8507@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Cc: pana@ietf.org
Message-id: <003101c43c4b$18ec2740$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

> > > As a result of recent discussion, I am preparing for adding new 
> > > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to 
> > > let the PAA know the POPA of the PaC.
> >
> > Semantically what PAA should learn is an IP address of the PaC, 
> > right? Not necessarily "POPA". If so, we might consider using a more

> > generic name, that doesn't refer to "POPA" in the name.
> 
> I used the term POPA because the issue starts from the issue of PRPA 
> to POPA update.  Do you have some other scenarios for the PAA needs to

> learn an IP address of the PaC, or do we just use generic naming just 
> in case for other usages for this message exchange are found out?

Yes, it is the latter that I'm thinking. The PAA needs to know any
reachable IP address of the PaC, so that it can send a (solicited or
otherwise) message. The IP address does not get any special treatment as
a "POPA".  

> > > I have one question: Are these messages need to be integrity 
> > > protected?
> > >
> > > I think the answer is yes in general, to prevent the host route to

> > > a legitimate PaC from being altered by an attacker.  On the other 
> > > hand, this means that an EAP method that can generate keys would 
> > > be needed even for networks (e.g., DSL) that are secured by 
> > > lower-layers.
> > >
> >
> > When there is a PANA SA, we must use it I think. If there is not, 
> > that's OK too. This is aligned with the rest of the protocol design.
> 
> Hmm, according to the following text in section 4.4, PANA-Reauth 
> exchange always needs a PANA SA to exist (I think the occurence table 
> marking the MAC AVP as "0-1" is typo.)  So I don't think the protocol 
> design is completely aligned that way.
> 
>    "Both PANA-Reauth-Request/ PANA-Reauth-Answer
>    messages MUST be protected with a MAC AVP."

I think this is a bug. We don't want to limit the use of Reauth messages
to only when there is a PANA SA.

> > In physically secured networks, operator doesn't have to use a 
> > key-generating EAP method, hence there might not be a PANA SA.
> 
> 
> Or should we say "in physically secured networks, operator doesn't 
> have to use a key-generating EAP method except for PANA-Reauth 
> exchange"?

I think we can have Reauth run without a MAC AVP. 

Alper





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



From pana-admin@ietf.org  Mon May 17 18:59:33 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11465
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 18:59:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqfS-0006Lk-39; Mon, 17 May 2004 18:33:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqZI-0002AG-50
	for pana@optimus.ietf.org; Mon, 17 May 2004 18:26:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09096
	for <pana@ietf.org>; Mon, 17 May 2004 18:26:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPqZF-0005V5-6g
	for pana@ietf.org; Mon, 17 May 2004 18:26:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqYC-00057Z-00
	for pana@ietf.org; Mon, 17 May 2004 18:25:37 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BPqXT-0004kh-00
	for pana@ietf.org; Mon, 17 May 2004 18:24:51 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 17 May 2004 21:31:36 -0000
Message-ID: <006e01c43c56$55654250$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040514225911.GB22808@steelhead>
Subject: Re: [Pana] issue85 (question)
Date: Mon, 17 May 2004 14:31:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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

 

> As a result of recent discussion, I am preparing for adding new
> messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> the PAA know the POPA of the PaC.
> 
What happened to the device-id update ? I thought we wanted to use a generic
update mechanism that can use either device-id or POPA.

> I have one question: Are these messages need to be integrity
> protected?
> 
> I think the answer is yes in general, to prevent the host route to a
> legitimate PaC from being altered by an attacker.  On the other hand,
> this means that an EAP method that can generate keys would be needed
> even for networks (e.g., DSL) that are secured by lower-layers.
> 
> Since there is an address ownership issue with regard to POPA, which
> cannot be solved by integrity protecting the POPA update messages and
> needs a mechanism outside the PANA protocol, I am wondering if the
> POPA update procedure really needs to be integrity protected.
> 
I agree with others that "use protection when there is PANA SA" approach.

-mohan

> Opinions?
> 
> 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 May 17 19:21:34 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12443
	for <pana-archive@lists.ietf.org>; Mon, 17 May 2004 19:21:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPr6Z-0006Xe-97; Mon, 17 May 2004 19:01:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqxD-0002PH-GO
	for pana@optimus.ietf.org; Mon, 17 May 2004 18:51:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11283
	for <pana@ietf.org>; Mon, 17 May 2004 18:51:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPqxA-000748-9Q
	for pana@ietf.org; Mon, 17 May 2004 18:51:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqwC-0006i7-00
	for pana@ietf.org; Mon, 17 May 2004 18:50:25 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqvJ-0006JL-00
	for pana@ietf.org; Mon, 17 May 2004 18:49:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4HMnHgH013333;
	Tue, 18 May 2004 07:49:17 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4HMnH2Z009227;
	Tue, 18 May 2004 07:49:17 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA09225 ; Tue, 18 May 2004 07:49:17 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA08315; Tue, 18 May 2004 07:49:16 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA20214; Tue, 18 May 2004 07:49:16 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4HMnFEU027775;
	Tue, 18 May 2004 07:49:15 +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 <0HXV002HARDZBZ@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 07:49:14 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BPqua-0005Ro-00; Mon, 17 May 2004 15:48:44 -0700
Date: Mon, 17 May 2004 15:48:43 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <006e01c43c56$55654250$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040517224843.GL8507@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.6i
References: <20040514225911.GB22808@steelhead>
 <006e01c43c56$55654250$861167c0@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.1 required=5.0 tests=AWL 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 Mon, May 17, 2004 at 02:31:36PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> > 
> What happened to the device-id update ? I thought we wanted to use a generic
> update mechanism that can use either device-id or POPA.

OK, how about PANA-Address-Update-{Request,Answer}?

> 
> > I have one question: Are these messages need to be integrity
> > protected?
> > 
> > I think the answer is yes in general, to prevent the host route to a
> > legitimate PaC from being altered by an attacker.  On the other hand,
> > this means that an EAP method that can generate keys would be needed
> > even for networks (e.g., DSL) that are secured by lower-layers.
> > 
> > Since there is an address ownership issue with regard to POPA, which
> > cannot be solved by integrity protecting the POPA update messages and
> > needs a mechanism outside the PANA protocol, I am wondering if the
> > POPA update procedure really needs to be integrity protected.
> > 
> I agree with others that "use protection when there is PANA SA" approach.

OK.

Yoshihiro Ohba


> 
> -mohan
> 
> > Opinions?
> > 
> > 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 May 17 19:26:15 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12654
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 19:26:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrN7-0002oa-Uk
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 19:18:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HNID58010816
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 19:18:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPr6B-0005yT-QT
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:00:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11565
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 19:00:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPr68-0002Ho-LR
	for pana-web-archive@ietf.org; Mon, 17 May 2004 19:00:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPr50-0001v8-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 18:59:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPr4a-0001a7-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 18:59:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqfS-0006Lk-39; Mon, 17 May 2004 18:33:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqZI-0002AG-50
	for pana@optimus.ietf.org; Mon, 17 May 2004 18:26:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09096
	for <pana@ietf.org>; Mon, 17 May 2004 18:26:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPqZF-0005V5-6g
	for pana@ietf.org; Mon, 17 May 2004 18:26:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqYC-00057Z-00
	for pana@ietf.org; Mon, 17 May 2004 18:25:37 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BPqXT-0004kh-00
	for pana@ietf.org; Mon, 17 May 2004 18:24:51 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 17 May 2004 21:31:36 -0000
Message-ID: <006e01c43c56$55654250$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20040514225911.GB22808@steelhead>
Subject: Re: [Pana] issue85 (question)
Date: Mon, 17 May 2004 14:31:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 

> As a result of recent discussion, I am preparing for adding new
> messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> the PAA know the POPA of the PaC.
> 
What happened to the device-id update ? I thought we wanted to use a generic
update mechanism that can use either device-id or POPA.

> I have one question: Are these messages need to be integrity
> protected?
> 
> I think the answer is yes in general, to prevent the host route to a
> legitimate PaC from being altered by an attacker.  On the other hand,
> this means that an EAP method that can generate keys would be needed
> even for networks (e.g., DSL) that are secured by lower-layers.
> 
> Since there is an address ownership issue with regard to POPA, which
> cannot be solved by integrity protecting the POPA update messages and
> needs a mechanism outside the PANA protocol, I am wondering if the
> POPA update procedure really needs to be integrity protected.
> 
I agree with others that "use protection when there is PANA SA" approach.

-mohan

> Opinions?
> 
> 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 May 17 19:38:37 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13486
	for <pana-archive@odin.ietf.org>; Mon, 17 May 2004 19:38:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrXZ-0007sE-Jp
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 19:29:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HNT1xZ030257
	for pana-archive@odin.ietf.org; Mon, 17 May 2004 19:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrRZ-0005ES-HQ
	for pana-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:22:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12522
	for <pana-web-archive@ietf.org>; Mon, 17 May 2004 19:22:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrRY-00024j-3r
	for pana-web-archive@ietf.org; Mon, 17 May 2004 19:22:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrQY-0001hy-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 19:21:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrPr-0001Lb-00
	for pana-web-archive@ietf.org; Mon, 17 May 2004 19:21:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPr6Z-0006Xe-97; Mon, 17 May 2004 19:01:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqxD-0002PH-GO
	for pana@optimus.ietf.org; Mon, 17 May 2004 18:51:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11283
	for <pana@ietf.org>; Mon, 17 May 2004 18:51:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPqxA-000748-9Q
	for pana@ietf.org; Mon, 17 May 2004 18:51:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqwC-0006i7-00
	for pana@ietf.org; Mon, 17 May 2004 18:50:25 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqvJ-0006JL-00
	for pana@ietf.org; Mon, 17 May 2004 18:49:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4HMnHgH013333;
	Tue, 18 May 2004 07:49:17 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4HMnH2Z009227;
	Tue, 18 May 2004 07:49:17 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA09225 ; Tue, 18 May 2004 07:49:17 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA08315; Tue, 18 May 2004 07:49:16 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA20214; Tue, 18 May 2004 07:49:16 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4HMnFEU027775;
	Tue, 18 May 2004 07:49:15 +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 <0HXV002HARDZBZ@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 07:49:14 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BPqua-0005Ro-00; Mon, 17 May 2004 15:48:44 -0700
Date: Mon, 17 May 2004 15:48:43 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <006e01c43c56$55654250$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040517224843.GL8507@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.6i
References: <20040514225911.GB22808@steelhead>
 <006e01c43c56$55654250$861167c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 17, 2004 at 02:31:36PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> > 
> What happened to the device-id update ? I thought we wanted to use a generic
> update mechanism that can use either device-id or POPA.

OK, how about PANA-Address-Update-{Request,Answer}?

> 
> > I have one question: Are these messages need to be integrity
> > protected?
> > 
> > I think the answer is yes in general, to prevent the host route to a
> > legitimate PaC from being altered by an attacker.  On the other hand,
> > this means that an EAP method that can generate keys would be needed
> > even for networks (e.g., DSL) that are secured by lower-layers.
> > 
> > Since there is an address ownership issue with regard to POPA, which
> > cannot be solved by integrity protecting the POPA update messages and
> > needs a mechanism outside the PANA protocol, I am wondering if the
> > POPA update procedure really needs to be integrity protected.
> > 
> I agree with others that "use protection when there is PANA SA" approach.

OK.

Yoshihiro Ohba


> 
> -mohan
> 
> > Opinions?
> > 
> > Yoshihiro Ohba
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana

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



From pana-admin@ietf.org  Tue May 18 10:22:50 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17546
	for <pana-archive@lists.ietf.org>; Tue, 18 May 2004 10:22:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ5CR-0005nm-RI; Tue, 18 May 2004 10:04:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ53x-00021a-Of
	for pana@optimus.ietf.org; Tue, 18 May 2004 09:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15164
	for <pana@ietf.org>; Tue, 18 May 2004 09:55:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ53v-000695-NX
	for pana@ietf.org; Tue, 18 May 2004 09:55:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ537-0005lS-00
	for pana@ietf.org; Tue, 18 May 2004 09:54:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ52K-0005O7-00
	for pana@ietf.org; Tue, 18 May 2004 09:53:41 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4IDrcgH003290;
	Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4IDrcs4011256;
	Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA11255 ; Tue, 18 May 2004 22:53:38 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA00437; Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA10347; Tue, 18 May 2004 22:53:37 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4IDrbEU003878;
	Tue, 18 May 2004 22:53:37 +0900 (JST)
Received: from steelhead (iVPN01-140.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 <0HXW00B81X9AYR@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 22:53:36 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BQ51q-0007Te-00; Tue, 18 May 2004 06:53:10 -0700
Date: Tue, 18 May 2004 06:53:10 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <006e01c43c56$55654250$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040518135310.GT8507@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.6i
References: <20040514225911.GB22808@steelhead>
 <006e01c43c56$55654250$861167c0@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.1 required=5.0 tests=AWL 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 Mon, May 17, 2004 at 02:31:36PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> > 
> What happened to the device-id update ? I thought we wanted to use a generic
> update mechanism that can use either device-id or POPA.

One more question: can't it be used for updating both device-id and
POPA at the same time when MAC address is used for the device-id?

Yoshihiro Ohba


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


From exim@www1.ietf.org  Tue May 18 10:42:57 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19963
	for <pana-archive@odin.ietf.org>; Tue, 18 May 2004 10:42:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ5aU-00014u-S9
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 10:28:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IESw1W004145
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 10:28:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ5W0-00080A-TA
	for pana-web-archive@optimus.ietf.org; Tue, 18 May 2004 10:24:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17683
	for <pana-web-archive@ietf.org>; Tue, 18 May 2004 10:24:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ5Vy-0001dt-O3
	for pana-web-archive@ietf.org; Tue, 18 May 2004 10:24:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ5Uy-0001EH-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 10:23:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ5U5-0000qQ-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 10:22:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ5CR-0005nm-RI; Tue, 18 May 2004 10:04:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ53x-00021a-Of
	for pana@optimus.ietf.org; Tue, 18 May 2004 09:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15164
	for <pana@ietf.org>; Tue, 18 May 2004 09:55:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ53v-000695-NX
	for pana@ietf.org; Tue, 18 May 2004 09:55:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ537-0005lS-00
	for pana@ietf.org; Tue, 18 May 2004 09:54:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ52K-0005O7-00
	for pana@ietf.org; Tue, 18 May 2004 09:53:41 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4IDrcgH003290;
	Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4IDrcs4011256;
	Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA11255 ; Tue, 18 May 2004 22:53:38 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA00437; Tue, 18 May 2004 22:53:38 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA10347; Tue, 18 May 2004 22:53:37 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4IDrbEU003878;
	Tue, 18 May 2004 22:53:37 +0900 (JST)
Received: from steelhead (iVPN01-140.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 <0HXW00B81X9AYR@tsbpo1.po.toshiba.co.jp>; Tue,
 18 May 2004 22:53:36 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BQ51q-0007Te-00; Tue, 18 May 2004 06:53:10 -0700
Date: Tue, 18 May 2004 06:53:10 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (question)
In-reply-to: <006e01c43c56$55654250$861167c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20040518135310.GT8507@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.6i
References: <20040514225911.GB22808@steelhead>
 <006e01c43c56$55654250$861167c0@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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 17, 2004 at 02:31:36PM -0700, Mohan Parthasarathy wrote:
>  
> 
> > As a result of recent discussion, I am preparing for adding new
> > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > the PAA know the POPA of the PaC.
> > 
> What happened to the device-id update ? I thought we wanted to use a generic
> update mechanism that can use either device-id or POPA.

One more question: can't it be used for updating both device-id and
POPA at the same time when MAC address is used for the device-id?

Yoshihiro Ohba


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



From pana-admin@ietf.org  Tue May 18 12:53:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27147
	for <pana-archive@lists.ietf.org>; Tue, 18 May 2004 12:53:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7j9-0001bi-PD; Tue, 18 May 2004 12:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7WU-0005uU-SH
	for pana@optimus.ietf.org; Tue, 18 May 2004 12:32:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25910
	for <pana@ietf.org>; Tue, 18 May 2004 12:32:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ7WT-0005SU-4Q
	for pana@ietf.org; Tue, 18 May 2004 12:32:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ7VX-0005Ow-00
	for pana@ietf.org; Tue, 18 May 2004 12:32:00 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQ7Uk-0005Lo-00
	for pana@ietf.org; Tue, 18 May 2004 12:31:10 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 18 May 2004 16:14:51 -0000
Message-ID: <004e01c43cf3$41a1f8b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040514225911.GB22808@steelhead> <006e01c43c56$55654250$861167c0@adithya> <20040518135310.GT8507@steelhead>
Subject: Re: [Pana] issue85 (question)
Date: Tue, 18 May 2004 09:14:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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

 > > 
> > > As a result of recent discussion, I am preparing for adding new
> > > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > > the PAA know the POPA of the PaC.
> > > 
> > What happened to the device-id update ? I thought we wanted to use a generic
> > update mechanism that can use either device-id or POPA.
> 
> One more question: can't it be used for updating both device-id and
> POPA at the same time when MAC address is used for the device-id?
> 
I guess so. So, calling it something like "PANA-update-{Request/Answer}"
and then carrying two separate AVPs like "device-id" and/or "Address" would
be generic enough to handle all the cases.

-mohan


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

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


From exim@www1.ietf.org  Tue May 18 13:07:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28010
	for <pana-archive@odin.ietf.org>; Tue, 18 May 2004 13:07:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7zL-0005gq-0f
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 13:02:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IH2kqP021872
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 13:02:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7rm-0003nn-QY
	for pana-web-archive@optimus.ietf.org; Tue, 18 May 2004 12:54:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27182
	for <pana-web-archive@ietf.org>; Tue, 18 May 2004 12:54:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ7rl-0006sw-1l
	for pana-web-archive@ietf.org; Tue, 18 May 2004 12:54:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ7qm-0006pk-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 12:53:57 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ7pp-0006nD-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 12:52:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7j9-0001bi-PD; Tue, 18 May 2004 12:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7WU-0005uU-SH
	for pana@optimus.ietf.org; Tue, 18 May 2004 12:32:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25910
	for <pana@ietf.org>; Tue, 18 May 2004 12:32:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ7WT-0005SU-4Q
	for pana@ietf.org; Tue, 18 May 2004 12:32:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ7VX-0005Ow-00
	for pana@ietf.org; Tue, 18 May 2004 12:32:00 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQ7Uk-0005Lo-00
	for pana@ietf.org; Tue, 18 May 2004 12:31:10 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp810.mail.sc5.yahoo.com with SMTP; 18 May 2004 16:14:51 -0000
Message-ID: <004e01c43cf3$41a1f8b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <20040514225911.GB22808@steelhead> <006e01c43c56$55654250$861167c0@adithya> <20040518135310.GT8507@steelhead>
Subject: Re: [Pana] issue85 (question)
Date: Tue, 18 May 2004 09:14:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 > > 
> > > As a result of recent discussion, I am preparing for adding new
> > > messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
> > > the PAA know the POPA of the PaC.
> > > 
> > What happened to the device-id update ? I thought we wanted to use a generic
> > update mechanism that can use either device-id or POPA.
> 
> One more question: can't it be used for updating both device-id and
> POPA at the same time when MAC address is used for the device-id?
> 
I guess so. So, calling it something like "PANA-update-{Request/Answer}"
and then carrying two separate AVPs like "device-id" and/or "Address" would
be generic enough to handle all the cases.

-mohan


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

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



From pana-admin@ietf.org  Tue May 18 13:27:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29167
	for <pana-archive@lists.ietf.org>; Tue, 18 May 2004 13:27:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8H6-0002Yr-L4; Tue, 18 May 2004 13:21:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ81V-0006Lm-C9
	for pana@optimus.ietf.org; Tue, 18 May 2004 13:05:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27788
	for <pana@ietf.org>; Tue, 18 May 2004 13:04:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ81T-0007a5-Hf
	for pana@ietf.org; Tue, 18 May 2004 13:04:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ80e-0007VR-00
	for pana@ietf.org; Tue, 18 May 2004 13:04:08 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ7zg-0007Lx-00
	for pana@ietf.org; Tue, 18 May 2004 13:03:08 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 3868330E37; Tue, 18 May 2004 19:02:36 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 19D9930E1E; Tue, 18 May 2004 19:02:36 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id A2A8814426; Tue, 18 May 2004 19:01:47 +0200 (MET DST)
Message-ID: <40AA40FD.90007@dif.um.es>
Date: Tue, 18 May 2004 18:59:41 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Subject: Re: [Pana] issue85 (question)
References: <20040514225911.GB22808@steelhead> <006e01c43c56$55654250$861167c0@adithya> <20040518135310.GT8507@steelhead> <004e01c43cf3$41a1f8b0$861167c0@adithya>
In-Reply-To: <004e01c43cf3$41a1f8b0$861167c0@adithya>
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=AWL 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

Mohan Parthasarathy wrote:

> > > 
>  
>
>>>>As a result of recent discussion, I am preparing for adding new
>>>>messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
>>>>the PAA know the POPA of the PaC.
>>>>
>>>>        
>>>>
>>>What happened to the device-id update ? I thought we wanted to use a generic
>>>update mechanism that can use either device-id or POPA.
>>>      
>>>
>>One more question: can't it be used for updating both device-id and
>>POPA at the same time when MAC address is used for the device-id?
>>
>>    
>>
>I guess so. So, calling it something like "PANA-update-{Request/Answer}"
>and then carrying two separate AVPs like "device-id" and/or "Address" would
>be generic enough to handle all the cases.
>  
>
Yes I like this idea... sounds good.

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


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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


From exim@www1.ietf.org  Tue May 18 13:36:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29671
	for <pana-archive@odin.ietf.org>; Tue, 18 May 2004 13:36:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8Sj-0005SK-1g
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 13:33:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IHX9PT020967
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 13:33:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8OB-00042U-D9
	for pana-web-archive@optimus.ietf.org; Tue, 18 May 2004 13:28:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29224
	for <pana-web-archive@ietf.org>; Tue, 18 May 2004 13:28:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ8O9-0001Ej-BM
	for pana-web-archive@ietf.org; Tue, 18 May 2004 13:28:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8N5-0001AY-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 13:27:20 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8Mh-00016q-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 13:26:55 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BQ8Mb-00005d-SQ
	for pana-web-archive@ietf.org; Tue, 18 May 2004 13:26:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8H6-0002Yr-L4; Tue, 18 May 2004 13:21:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ81V-0006Lm-C9
	for pana@optimus.ietf.org; Tue, 18 May 2004 13:05:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27788
	for <pana@ietf.org>; Tue, 18 May 2004 13:04:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ81T-0007a5-Hf
	for pana@ietf.org; Tue, 18 May 2004 13:04:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ80e-0007VR-00
	for pana@ietf.org; Tue, 18 May 2004 13:04:08 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ7zg-0007Lx-00
	for pana@ietf.org; Tue, 18 May 2004 13:03:08 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 3868330E37; Tue, 18 May 2004 19:02:36 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 19D9930E1E; Tue, 18 May 2004 19:02:36 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id A2A8814426; Tue, 18 May 2004 19:01:47 +0200 (MET DST)
Message-ID: <40AA40FD.90007@dif.um.es>
Date: Tue, 18 May 2004 18:59:41 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Subject: Re: [Pana] issue85 (question)
References: <20040514225911.GB22808@steelhead> <006e01c43c56$55654250$861167c0@adithya> <20040518135310.GT8507@steelhead> <004e01c43cf3$41a1f8b0$861167c0@adithya>
In-Reply-To: <004e01c43cf3$41a1f8b0$861167c0@adithya>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mohan Parthasarathy wrote:

> > > 
>  
>
>>>>As a result of recent discussion, I am preparing for adding new
>>>>messages PANA-POPA-Update-Request and PANA-POPA-Update-Answer to let
>>>>the PAA know the POPA of the PaC.
>>>>
>>>>        
>>>>
>>>What happened to the device-id update ? I thought we wanted to use a generic
>>>update mechanism that can use either device-id or POPA.
>>>      
>>>
>>One more question: can't it be used for updating both device-id and
>>POPA at the same time when MAC address is used for the device-id?
>>
>>    
>>
>I guess so. So, calling it something like "PANA-update-{Request/Answer}"
>and then carrying two separate AVPs like "device-id" and/or "Address" would
>be generic enough to handle all the cases.
>  
>
Yes I like this idea... sounds good.

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


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From pana-admin@ietf.org  Tue May 18 22:03:01 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05752
	for <pana-archive@lists.ietf.org>; Tue, 18 May 2004 22:03:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGKX-00080o-JK; Tue, 18 May 2004 21:57:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGGw-0007LU-Ig
	for pana@optimus.ietf.org; Tue, 18 May 2004 21:53:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04933
	for <pana@ietf.org>; Tue, 18 May 2004 21:53:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQGGt-0002lR-KG
	for pana@ietf.org; Tue, 18 May 2004 21:53:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQGFy-0002fK-00
	for pana@ietf.org; Tue, 18 May 2004 21:52:32 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQGF4-0002X3-00
	for pana@ietf.org; Tue, 18 May 2004 21:51:35 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4J1pXgH024665;
	Wed, 19 May 2004 10:51:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4J1pW1o016851;
	Wed, 19 May 2004 10:51:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id LAA16848 ; Wed, 19 May 2004 10:51:32 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA18221; Wed, 19 May 2004 10:51:32 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA06146; Wed, 19 May 2004 10:51:29 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4J1pSEU014444;
	Wed, 19 May 2004 10:51:28 +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 <0HXX0014SUHO4F@tsbpo1.po.toshiba.co.jp>; Wed,
 19 May 2004 10:51:27 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BQGEt-0001fy-00; Tue, 18 May 2004 18:51:23 -0700
Date: Tue, 18 May 2004 18:51:23 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040519015123.GC29343@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.6i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] issue85 (initial text)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is the initial text for issue 85.

Comments are appreciated.

----------


[1] Add the following item in section 4.1.1

"   
   o  IP-Address AVP: Conveys an IP-Address of a PaC.  
"
 

[2] Add the following items in section 4.1.5:

"
      *  IP address of PaC (may be the same as the Device-Id of PaC)
                                                                             
      *  IP address of PAA (may be the same as the Device-Id of PAA)
"
                                                                                

[3] Add the following item in section section 4.1.7:

"
      When an IP-Address AVP is included, the AVP is valid if (i) the
      Address type contained in the AVP matches the expected one
      (i.e., either IPv4 or IPv6) that is used for the current PANA
      session and (ii) the AVP value matches the one extracted from
      the IP header.
"

[4] Update the following paragraph of section 4.4 

"
   The second type of re-authentication is based on a single protected
   message exchange without entering the authentication phase.
   PANA-Reauth-Request and PANA-Reauth-Answer messages are used for this
   purpose.  If there is an established PANA SA, both the PaC and the
   PAA are allowed to send a PANA-Reauth-Request message to the
   communicating peer whenever it needs to make sure the availability of
   the PANA SA on the peer and expect the peer to return a PANA-
   Reauth-Answer message.  Both PANA-Reauth-Request/ PANA-Reauth-Answer
   messages MUST be protected with a MAC AVP.
"

to:

"
   The second type of re-authentication is based on a single protected
   message exchange without entering the authentication phase.
   PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
   this purpose.  If there is an established PANA SA, both the PaC and
   the PAA are allowed to send a PANA-Reauth-Request message to the
   communicating peer whenever it needs to make sure the availability
   of the PANA SA on the peer and expect the peer to return a
   PANA-Reauth-Answer message.  In this case, both
   PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
   with a MAC AVP.  If there is an established PANA session but
   without an established PANA SA, both the PaC and the PAA are
   allowed to send a PANA-Reauth-Request message to the communicating
   peer whenever it needs to make sure the availability of the PANA
   session on the peer and expect the peer to return a
   PANA-Reauth-Answer message.  In this case, both
   PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
   with a MAC AVP.
"

[5] Insert the following section after section 4.7:

"
4.8. Updating PaC's Address

A PaC's address can change in certain situations.  For example, the
PANA framework [I-D.ietf-pana-framework] describes a case in which a
PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
the PaC and PAA create host routes to each other in order to maintain
on-link communication based on the POPA where the link-layer address
of the PaC is used as the device identifier.  Also, a PaC's device
identifier may change regardless of whether a link-layer address or an
IP address is used as the device identifier.  As a result, it is
possible when a link-layer address is used as the device identifier
that both the device identifier and an IP address change.  In any
case, the PAA needs to be notified about the change of address(es).

After the PaC has changed its address(es), it MUST send a
PANA-Address-Update-Request message to the PAA.  The message carries
the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
least one of these AVPs MUST appear in the request.  If an IP address
is used as the device identifier, a Device-Id AVP MUST be used and an
IP-Address AVP MUST NOT be used.  If an address contained in the
request is invalid, the PAA sends a PANA-Error message with a result
code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
whether the device identifier or the IP address is invalid (in case
both a Device-Id AVP and an IP-Address AVP are included and both are
invalid, whichever result code is returned).  Otherwise, the PAA
updates the address(es) of the PaC of the session attributes and
returns a PANA-Address-Update-Answer message.  If there is an
established PANA SA, both PANA-Address-Update-Request and
PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
"

[6] Change Figure 10 to:

"
                 Message                     Direction: 
                                             PaC---PAA
                 ----------------------------------------
                 PANA-PAA-Discover           -------->
                                                                                
                 PANA-Start-Request          <--------
                 PANA-Start-Answer           -------->
                                                                                
                 PANA-Auth-Request           <--------
                 PANA-Auth-Answer            -------->
                                                                                
                 PANA-FirstAuth-End-Request  <--------
                 PANA-FirstAuth-End-Answer   -------->
                                                                                
                 PANA-Bind-Request           <--------
                 PANA-Bind-Answer            -------->
                                                                                
                 PANA-Reauth-Request         <------->
                 PANA-Reauth-Answer          <------->
                                                                                
                 PANA-Termination-Request    <------->
                 PANA-Termination-Answer     <------->
                                                                                
                 PANA-Address-Update-Request -------->
                 PANA-Address-Update-Answer  <--------

                 PANA-Error                  <------->
"

[7] Change sections 6.4.9 and 6.4.10 from:

"
6.4.9 PANA-Reauth-Request (PRAR)
                                                                            
   PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
                                                                            
         PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                       [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >
                                                                            
                                                                            
6.4.10 PANA-Reauth-Answer (PRAA)
                                                                            
   PANA-Reauth-Answer (PRAA) is sent in response to a
   PANA-Reauth-Request.
                                                                            
         PANA-Reauth-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                       [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >
"

to:

"
6.4.9 PANA-Reauth-Request (PRAR)
                                                                            
   PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
                                                                            
         PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >
                                                                            
                                                                            
6.4.10 PANA-Reauth-Answer (PRAA)
                                                                            
   PANA-Reauth-Answer (PRAA) is sent in response to a
   PANA-Reauth-Request.
                                                                            
         PANA-Reauth-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >
"

[8] Add the following sections:

"
6.4.16 PANA-Address-Update-Request (PAUR)
                                                                                
   PANA-Address-Update-Request (PAUR) is sent by the PaC to the PAA.
                                                                                
         PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
                       < Session-Id >
                   0*1 { Device-Id }
                   0*1 { IP-Address }
                   0*1 < MAC >


6.4.17 PANA-Address-Update-Answer (PAUA)
                                                                                
   PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC in
   response to a PANA-Address-Update-Request.
                                                                                
         PANA-Address-Update-Answer ::= < PANA-Header: 9 >
                       < Session-Id >
                   0*1 < MAC >
"

"
6.5.19 IP-Address AVP
                                                                                
   The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
   The payload format of the IP-Address AVP is the same as that of the
   Device-Id AVP (see See section Section 6.5.2).  Address families
   for IPv4 or IPv6 MUST be used for this AVP.
"


[9] Add the following result code in section 6.5.7.2:

"
   PANA_INVALID_DEVICE_ID  5019
                                                                                
      Error code from PAA to PaC or from PaC to PAA.  This error is
      returned in a PANA-Error message when the Device-Id AVP
      contained in a received PANA-Bind-Request, PANA-Bind-Answer or
      PANA-Address-Update-Request message is invalid.

   PANA_INVALID_IP_ADDRESS  5020
                                                                                
      Error code from PAA to PaC.  This error is returned in a
      PANA-Error message when the IP-Address AVP in the received
      PANA-Address-Update-Request message is invalid.

"

[10]  Modify the AVP occurrence table as:

"
                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
      Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
      Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
      PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  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  |  0  |  0  |  0  |  0  |
      NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
      EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
      Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
                                                                                
                 Figure 11: AVP Occurrence Table (1/3)

                          +---------------------------------------------+
                          |      Message                                |
                          |       Type                                  |
                          +------+------+-----+-----+-----+------+------+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |
      --------------------+------+------+-----+-----+-----+------+------+
      Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0   |
      Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1   |
      Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0   |
      EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0   |
      MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1  |
      Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0   |
      ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1  |
      IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      --------------------+------+------+-----+-----+-----+------+------+
                                                                                
                 Figure 12: AVP Occurrence Table (2/3)
                                                                                

                          +-------------+
                          |   Message   |
                          |     Type    |
                          +------+------+
      Attribute Name      | PAUR | PAUA |
      --------------------+------+------+
      Result-Code         |  0   |  0   |
      Session-Id          |  1   |  1   |
      Termination-Cause   |  0   |  0   |
      EAP-Payload         |  0   |  0   |
      MAC                 | 0-1  | 0-1  |
      Nonce               |  0   |  0   |
      Device-Id           | 0-1  |  0   |
      Cookie              |  0   |  0   |
      Protection-Cap.     |  0   |  0   |
      PPAC                |  0   |  0   |
      Session-Lifetime    |  0   |  0   |
      Failed-AVP          |  0   |  0   |
      ISP-Information     |  0   |  0   |
      NAP-Information     |  0   |  0   |
      EP-Device-Id        |  0   |  0   |
      Key-Id              |  0   |  0   |
      IP-Address          | 0-1  |  0   |
      --------------------+------+------+
                                                                                
                 Figure 13: AVP Occurrence Table (3/3)
"

[11]  Change the text in section 7 from:

"
         PANA-PAA-Discover (PDI)
         PANA-Start-Request (PSR)*
         PANA-Start-Answer (PSA)**
         PANA-Bind-Request (PBR)
         PANA-FirstAuth-End-Request (PFER)
         PANA-Reauth-Request (PRAR)
         PANA-Termination-Request (PTR)
                                                                                
         *)  PSR that carries a Cookie AVP is not retransmitted.
         **) PSA that does not carry a Cookie AVP is not retransmitted.
"

to:

"
         PANA-PAA-Discover (PDI)
         PANA-Start-Request (PSR)*
         PANA-Start-Answer (PSA)**
         PANA-Bind-Request (PBR)
         PANA-FirstAuth-End-Request (PFER)
         PANA-Reauth-Request (PRAR)
         PANA-Termination-Request (PTR)
         PANA-Address-Update-Request (PAUR)
                                                                                
         *)  PSR that carries a Cookie AVP is not retransmitted.
         **) PSA that does not carry a Cookie AVP is not retransmitted.
"
                                                                                
[12]  Add the folliwng text in section 8:

"
   j) Updating PaC's address
                                                                                
   An attacker can generate a PANA-Address-Update-Request with an
   invalid Device-Id AVP or an IP-Address AVP.  There are several
   threats:

   - An attacker spoofs an address and registers itself with the
   address.  If the registered address is not assigned to any PaC,
   subsequent PANA messages sent from the PAA to the attacker will not
   reach any node and this is not a significant harm.  If the
   registered address is assigned to some PaC, subsequent PANA
   messages sent from the PAA to the attacker will reach the PaC, but
   will be silently discarded because the Session-Id is different.

   - An attacker registers other PaC with any address.  As a result,
   subsequent PANA messages sent from the PAA to the PaC will not
   reach the PaC.

   To avoid all those attacks against an address update, an additional
   mechanism may be defined outside the PANA protocol for the PAA to
   validate ownership of the address.
"


Best regards,

Yoshihiro Ohba

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


From exim@www1.ietf.org  Tue May 18 22:14:15 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06149
	for <pana-archive@odin.ietf.org>; Tue, 18 May 2004 22:14:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGZ7-0002YC-GE
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 22:12:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J2CHEl009800
	for pana-archive@odin.ietf.org; Tue, 18 May 2004 22:12:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGRR-0000ac-Iv
	for pana-web-archive@optimus.ietf.org; Tue, 18 May 2004 22:04:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05820
	for <pana-web-archive@ietf.org>; Tue, 18 May 2004 22:04:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQGRO-00046b-Ex
	for pana-web-archive@ietf.org; Tue, 18 May 2004 22:04:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQGQX-00041l-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 22:03:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQGPf-0003xD-00
	for pana-web-archive@ietf.org; Tue, 18 May 2004 22:02:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGKX-00080o-JK; Tue, 18 May 2004 21:57:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQGGw-0007LU-Ig
	for pana@optimus.ietf.org; Tue, 18 May 2004 21:53:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04933
	for <pana@ietf.org>; Tue, 18 May 2004 21:53:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQGGt-0002lR-KG
	for pana@ietf.org; Tue, 18 May 2004 21:53:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQGFy-0002fK-00
	for pana@ietf.org; Tue, 18 May 2004 21:52:32 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQGF4-0002X3-00
	for pana@ietf.org; Tue, 18 May 2004 21:51:35 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4J1pXgH024665;
	Wed, 19 May 2004 10:51:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4J1pW1o016851;
	Wed, 19 May 2004 10:51:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id LAA16848 ; Wed, 19 May 2004 10:51:32 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA18221; Wed, 19 May 2004 10:51:32 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA06146; Wed, 19 May 2004 10:51:29 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4J1pSEU014444;
	Wed, 19 May 2004 10:51:28 +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 <0HXX0014SUHO4F@tsbpo1.po.toshiba.co.jp>; Wed,
 19 May 2004 10:51:27 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BQGEt-0001fy-00; Tue, 18 May 2004 18:51:23 -0700
Date: Tue, 18 May 2004 18:51:23 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040519015123.GC29343@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.6i
Subject: [Pana] issue85 (initial text)
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

This is the initial text for issue 85.

Comments are appreciated.

----------


[1] Add the following item in section 4.1.1

"   
   o  IP-Address AVP: Conveys an IP-Address of a PaC.  
"
 

[2] Add the following items in section 4.1.5:

"
      *  IP address of PaC (may be the same as the Device-Id of PaC)
                                                                             
      *  IP address of PAA (may be the same as the Device-Id of PAA)
"
                                                                                

[3] Add the following item in section section 4.1.7:

"
      When an IP-Address AVP is included, the AVP is valid if (i) the
      Address type contained in the AVP matches the expected one
      (i.e., either IPv4 or IPv6) that is used for the current PANA
      session and (ii) the AVP value matches the one extracted from
      the IP header.
"

[4] Update the following paragraph of section 4.4 

"
   The second type of re-authentication is based on a single protected
   message exchange without entering the authentication phase.
   PANA-Reauth-Request and PANA-Reauth-Answer messages are used for this
   purpose.  If there is an established PANA SA, both the PaC and the
   PAA are allowed to send a PANA-Reauth-Request message to the
   communicating peer whenever it needs to make sure the availability of
   the PANA SA on the peer and expect the peer to return a PANA-
   Reauth-Answer message.  Both PANA-Reauth-Request/ PANA-Reauth-Answer
   messages MUST be protected with a MAC AVP.
"

to:

"
   The second type of re-authentication is based on a single protected
   message exchange without entering the authentication phase.
   PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
   this purpose.  If there is an established PANA SA, both the PaC and
   the PAA are allowed to send a PANA-Reauth-Request message to the
   communicating peer whenever it needs to make sure the availability
   of the PANA SA on the peer and expect the peer to return a
   PANA-Reauth-Answer message.  In this case, both
   PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
   with a MAC AVP.  If there is an established PANA session but
   without an established PANA SA, both the PaC and the PAA are
   allowed to send a PANA-Reauth-Request message to the communicating
   peer whenever it needs to make sure the availability of the PANA
   session on the peer and expect the peer to return a
   PANA-Reauth-Answer message.  In this case, both
   PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
   with a MAC AVP.
"

[5] Insert the following section after section 4.7:

"
4.8. Updating PaC's Address

A PaC's address can change in certain situations.  For example, the
PANA framework [I-D.ietf-pana-framework] describes a case in which a
PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
the PaC and PAA create host routes to each other in order to maintain
on-link communication based on the POPA where the link-layer address
of the PaC is used as the device identifier.  Also, a PaC's device
identifier may change regardless of whether a link-layer address or an
IP address is used as the device identifier.  As a result, it is
possible when a link-layer address is used as the device identifier
that both the device identifier and an IP address change.  In any
case, the PAA needs to be notified about the change of address(es).

After the PaC has changed its address(es), it MUST send a
PANA-Address-Update-Request message to the PAA.  The message carries
the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
least one of these AVPs MUST appear in the request.  If an IP address
is used as the device identifier, a Device-Id AVP MUST be used and an
IP-Address AVP MUST NOT be used.  If an address contained in the
request is invalid, the PAA sends a PANA-Error message with a result
code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
whether the device identifier or the IP address is invalid (in case
both a Device-Id AVP and an IP-Address AVP are included and both are
invalid, whichever result code is returned).  Otherwise, the PAA
updates the address(es) of the PaC of the session attributes and
returns a PANA-Address-Update-Answer message.  If there is an
established PANA SA, both PANA-Address-Update-Request and
PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
"

[6] Change Figure 10 to:

"
                 Message                     Direction: 
                                             PaC---PAA
                 ----------------------------------------
                 PANA-PAA-Discover           -------->
                                                                                
                 PANA-Start-Request          <--------
                 PANA-Start-Answer           -------->
                                                                                
                 PANA-Auth-Request           <--------
                 PANA-Auth-Answer            -------->
                                                                                
                 PANA-FirstAuth-End-Request  <--------
                 PANA-FirstAuth-End-Answer   -------->
                                                                                
                 PANA-Bind-Request           <--------
                 PANA-Bind-Answer            -------->
                                                                                
                 PANA-Reauth-Request         <------->
                 PANA-Reauth-Answer          <------->
                                                                                
                 PANA-Termination-Request    <------->
                 PANA-Termination-Answer     <------->
                                                                                
                 PANA-Address-Update-Request -------->
                 PANA-Address-Update-Answer  <--------

                 PANA-Error                  <------->
"

[7] Change sections 6.4.9 and 6.4.10 from:

"
6.4.9 PANA-Reauth-Request (PRAR)
                                                                            
   PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
                                                                            
         PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                       [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >
                                                                            
                                                                            
6.4.10 PANA-Reauth-Answer (PRAA)
                                                                            
   PANA-Reauth-Answer (PRAA) is sent in response to a
   PANA-Reauth-Request.
                                                                            
         PANA-Reauth-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                       [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >
"

to:

"
6.4.9 PANA-Reauth-Request (PRAR)
                                                                            
   PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
                                                                            
         PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >
                                                                            
                                                                            
6.4.10 PANA-Reauth-Answer (PRAA)
                                                                            
   PANA-Reauth-Answer (PRAA) is sent in response to a
   PANA-Reauth-Request.
                                                                            
         PANA-Reauth-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >
"

[8] Add the following sections:

"
6.4.16 PANA-Address-Update-Request (PAUR)
                                                                                
   PANA-Address-Update-Request (PAUR) is sent by the PaC to the PAA.
                                                                                
         PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
                       < Session-Id >
                   0*1 { Device-Id }
                   0*1 { IP-Address }
                   0*1 < MAC >


6.4.17 PANA-Address-Update-Answer (PAUA)
                                                                                
   PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC in
   response to a PANA-Address-Update-Request.
                                                                                
         PANA-Address-Update-Answer ::= < PANA-Header: 9 >
                       < Session-Id >
                   0*1 < MAC >
"

"
6.5.19 IP-Address AVP
                                                                                
   The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
   The payload format of the IP-Address AVP is the same as that of the
   Device-Id AVP (see See section Section 6.5.2).  Address families
   for IPv4 or IPv6 MUST be used for this AVP.
"


[9] Add the following result code in section 6.5.7.2:

"
   PANA_INVALID_DEVICE_ID  5019
                                                                                
      Error code from PAA to PaC or from PaC to PAA.  This error is
      returned in a PANA-Error message when the Device-Id AVP
      contained in a received PANA-Bind-Request, PANA-Bind-Answer or
      PANA-Address-Update-Request message is invalid.

   PANA_INVALID_IP_ADDRESS  5020
                                                                                
      Error code from PAA to PaC.  This error is returned in a
      PANA-Error message when the IP-Address AVP in the received
      PANA-Address-Update-Request message is invalid.

"

[10]  Modify the AVP occurrence table as:

"
                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
      Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
      Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
      MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
      Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
      Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
      PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  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  |  0  |  0  |  0  |  0  |
      NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
      EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
      Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
                                                                                
                 Figure 11: AVP Occurrence Table (1/3)

                          +---------------------------------------------+
                          |      Message                                |
                          |       Type                                  |
                          +------+------+-----+-----+-----+------+------+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |
      --------------------+------+------+-----+-----+-----+------+------+
      Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0   |
      Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1   |
      Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0   |
      EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0   |
      MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1  |
      Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0   |
      ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1  |
      IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0   |
      --------------------+------+------+-----+-----+-----+------+------+
                                                                                
                 Figure 12: AVP Occurrence Table (2/3)
                                                                                

                          +-------------+
                          |   Message   |
                          |     Type    |
                          +------+------+
      Attribute Name      | PAUR | PAUA |
      --------------------+------+------+
      Result-Code         |  0   |  0   |
      Session-Id          |  1   |  1   |
      Termination-Cause   |  0   |  0   |
      EAP-Payload         |  0   |  0   |
      MAC                 | 0-1  | 0-1  |
      Nonce               |  0   |  0   |
      Device-Id           | 0-1  |  0   |
      Cookie              |  0   |  0   |
      Protection-Cap.     |  0   |  0   |
      PPAC                |  0   |  0   |
      Session-Lifetime    |  0   |  0   |
      Failed-AVP          |  0   |  0   |
      ISP-Information     |  0   |  0   |
      NAP-Information     |  0   |  0   |
      EP-Device-Id        |  0   |  0   |
      Key-Id              |  0   |  0   |
      IP-Address          | 0-1  |  0   |
      --------------------+------+------+
                                                                                
                 Figure 13: AVP Occurrence Table (3/3)
"

[11]  Change the text in section 7 from:

"
         PANA-PAA-Discover (PDI)
         PANA-Start-Request (PSR)*
         PANA-Start-Answer (PSA)**
         PANA-Bind-Request (PBR)
         PANA-FirstAuth-End-Request (PFER)
         PANA-Reauth-Request (PRAR)
         PANA-Termination-Request (PTR)
                                                                                
         *)  PSR that carries a Cookie AVP is not retransmitted.
         **) PSA that does not carry a Cookie AVP is not retransmitted.
"

to:

"
         PANA-PAA-Discover (PDI)
         PANA-Start-Request (PSR)*
         PANA-Start-Answer (PSA)**
         PANA-Bind-Request (PBR)
         PANA-FirstAuth-End-Request (PFER)
         PANA-Reauth-Request (PRAR)
         PANA-Termination-Request (PTR)
         PANA-Address-Update-Request (PAUR)
                                                                                
         *)  PSR that carries a Cookie AVP is not retransmitted.
         **) PSA that does not carry a Cookie AVP is not retransmitted.
"
                                                                                
[12]  Add the folliwng text in section 8:

"
   j) Updating PaC's address
                                                                                
   An attacker can generate a PANA-Address-Update-Request with an
   invalid Device-Id AVP or an IP-Address AVP.  There are several
   threats:

   - An attacker spoofs an address and registers itself with the
   address.  If the registered address is not assigned to any PaC,
   subsequent PANA messages sent from the PAA to the attacker will not
   reach any node and this is not a significant harm.  If the
   registered address is assigned to some PaC, subsequent PANA
   messages sent from the PAA to the attacker will reach the PaC, but
   will be silently discarded because the Session-Id is different.

   - An attacker registers other PaC with any address.  As a result,
   subsequent PANA messages sent from the PAA to the PaC will not
   reach the PaC.

   To avoid all those attacks against an address update, an additional
   mechanism may be defined outside the PANA protocol for the PAA to
   validate ownership of the address.
"


Best regards,

Yoshihiro Ohba

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



From pana-admin@ietf.org  Fri May 21 17:18:48 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04314
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 17:18:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBq-0000pW-OO; Fri, 21 May 2004 17:04:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0w-0002vL-Sq
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02013
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0u-0002Wk-PZ
	for pana@ietf.org; Fri, 21 May 2004 16:53:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGyz-0002AS-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:09 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvo-0001b9-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:53 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY3005010EXJF@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:21 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300MPN0EXIF@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:21 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:21 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <005701c43f74$d0c64ef0$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD review of draft-ietf-pana-requirements-07.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

And this is for the requirements draft.

Alper


-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:54 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD review of draft-ietf-pana-requirements-07.txt

> 4.2. IP Address Assignment 
>     
>    Assigning an IP address to the client is outside the scope of PANA.

>    PANA protocol design MAY require the PaC to configure an IP address

>    before using this protocol. Allocating IP addresses to 
>    unauthenticated PaCs may create security vulnerabilities, such as
IP 

Please update to reflect current WG decisions. I.e., PANA assumes an
IP address exists and just uses it.

>    links. Furthermore, two nodes on the same IP subnet do not 
>    necessarily satisfy this requirement, as they can be more than one 
>    hop away from each other [MULTILINK]. A PAA can be on the NAS 

we don't have multilinks... Probably best to just delete this text.


Thomas


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


From pana-admin@ietf.org  Fri May 21 17:19:18 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04353
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 17:19:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBr-0000pl-FS; Fri, 21 May 2004 17:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0y-0002vQ-7n
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02020
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0v-0002Wp-U5
	for pana@ietf.org; Fri, 21 May 2004 16:53:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGz0-0002Af-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:11 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvp-0001b9-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:53 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY3005010F1JH@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:25 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300AK60F09P@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:25 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:24 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <006301c43f74$d2f8bf50$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD review comments on draft-ietf-pana-threats-eval-04.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Please see below for Thomas Narten's review comments on the pana-threats
draft.

- Chairs

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:51 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD review comments on draft-ietf-pana-threats-eval-04.txt

Note: for all the review comments, let's discuss today (if necessary),
then  forward to authors/WG.

2004-05-21 review of -04

>    Authentication Server (AS)  
>      
>       An entity that authenticates the PANA client. It may be
co-located  
>       with PANA authentication agent or part of the back-end  
>       infrastructure.  

Here, no distinction is made between Local AS and Home AS. But below:

>      1) PAA and AS: PaC belonging to the same administrative domain as

>         the AS, often needs to use resources provided by PAA that  
>         belongs to another administrative domain. PAA authenticates
the  

Here, it seems it is asume AS is Home AS. 

>      3) PaC and AS: PaC and AS belong to the same administrative
domain  
>         and share a trust relationship. When PaC uses a different
domain  

Same here. Please clarify.


>    It is possible that some of the entities like PAA, AS and EP are

>    co-located. In those cases, it can be safely assumed that there are

>    no significant external threats.  

Doesn't make sense. there is still the PAC-PAA path... Oh, you are
talking only about among the three. Could be more clear (like just
mention you are talking here about communication amoung the three
entities).

>    PANA MUST be able to prevent service theft. In some cases e.g. non-

>    shared links, it is sufficient to provide access control
information  
>    like IP address, MAC address, etc., to EP, which in turn can
prevent  
>    unauthorized users from gaining access to the network by policing
the  
>    packets for matching addresses. In the case of shared links, this  
>    information is not sufficient to prevent service theft. PANA MUST
be  
>    able to bootstrap a shared secret between the PaC and PAA which can

>    be further used to setup a security association (e.g., IPsec)
between  
>    PaC and EP to prevent service theft on shared links.   

Seems wrong. Even in unshared links, if the authorized client
disconnects, and an intruder gets on the link, it can continue using
the DIs.

>    Requirement 9  
>      
>    PANA SHOULD not assume that the PaC has acquired an IP address
before  
>    PANA begins.   

Needs updating.  (also in summary)

>    In environments where the link is shared, this threat is present as

>    any node can pretend to be a PAA. Even if the nodes are
authenticated  
>    at layer 2, this threat is present. It is difficult to protect the

>    discovery process, as there is no a priori trust relationship
between  
>    PAA and PaC. It might be possible for the EP to filter out the  
>    packets coming from PaC that resembles PAA packets and hence this  
>    threat can be prevented in such environments.  

I don't follow. on a shared LAN, its not clear traffic has to go
through the EP. Are there some assumptions going on here?

>    Requirement 1  
>      
>    PANA MUST not assume that the discovery process is protected.
Since,  
>    it is difficult to protect the discovery process, the security-  
>    critical information exchanged during the discovery process SHOULD
be  
>    limited.  

More like discovery should be treated as a hint, and reverified at a
higher layer before accepting as valid. Is the actual requirement that
the PAA  must authenticate itself to the client, to prevent spoofing
during the discovery process?


>        o All the PaCs may be authenticated to the access network at  
>           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
>           association with layer 2 authentication agent (e.g., 802.11

>           [IEEE-802.11] Access point), but still do not trust each  
>           other.  

not sure I follow. In what  way do they not trust each other? What are
the implications, and what does PANA have to do with this?

Nits:

title needs to expand PANA

>    T6.1.1: A malicious node can pretend to be a PAA by sending a
spoofed  
>    advertisement.  

subsubsection headings seem off (all have T in front, and are indented
like normal text)


>    In the following discussion, any reference to link that is not
shared  

s/to/to a/

>      2) PAA and EP: PAA and EP belong to the same administrative
domain.  

s/PAA/The PAA/

>      3) PaC and AS: PaC and AS belong to the same administrative
domain  

s/PaC/The PaC/

NOte: there are multiple places where terms like PAA are used where
you need to use "the PAA", or "a PAA", etc.

>    Some authentication protocols e.g., EAP, has a special message to  

s/has/have/

>    PANA MUST be able to prevent service theft. In some cases e.g. non-


s/e.g./, e.g.,/ (do this throughout probably)


Thomas


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


From pana-admin@ietf.org  Fri May 21 17:19:50 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04374
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 17:19:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBr-0000pt-PI; Fri, 21 May 2004 17:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0z-0002vT-1B
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02024
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0w-0002X1-Uk
	for pana@ietf.org; Fri, 21 May 2004 16:53:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGz2-0002Av-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:12 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvq-0001bP-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:54 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY300E010EZXB@mailout2.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:23 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY3005NZ0EYL2@mailout2.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:23 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:22 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Please see below for Thomas Narten's review comments on the
usage-scenarios draft.

Chairs note: The current I-D seems like it will benefit from a re-write.
It has text that is not essential to answering the fundamental
questions. The text can be condensed. While doing that, we can also
reduce it to an appendix section in the requirements draft, and reduce
the document load.

- Chairs

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:53 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt

2004-05-20 review of -06:

Overall, a weak and unconvincing document. But probably harmless.

Need to get verification from DSL and CDMA2000 community on their
sections and whether pana is of any real interest to them.

abstract says:

>    Network access authentication is a function that is typically
>    required in most scenarios.

please change "most" to "many". Far from clear that this is required
in "most" scenarios.

Nits:

"PANA" acronym should be expanded in title (see ID nits)

The acronyms need definitions in some cases. E.g.:

>    MSC: Mobile Switching Center
>    MT: Mobile Termination
>    VLR: Visiting Location Register

mean nothing to me. There are others too that are not obvious. Expand
their meaning a bit?

normative references are not right. Many of the listed ones appear to
be non-normative.

>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods.
>    Among the various types of link-layers, only IEEE 802 defines how
to
>    carry EAP on the link-layer [802.1X].  Other link-layers resort to
>    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
>    carrying EAP. The ungainly insertion of this extra layer incurs
>    additional round-trips at connection time, generates overhead of
PPP
>    processing even for subsequent data packets, and forces the network
>    topology into a point-to-point model. EAP could achieve greater
>    applicability if it could be carried directly over IP. That way,
the
>    resulting IP packets could be carried over any link technology
>    without incurring additional cost or limitation on the
architectures.

would a PPP person agree with this characterization? (need to check)

>    In the absence of such lower-layer security and authentication
>    mechanism not only are service providers unable to control the
>    unauthorized use of their networks but also end-users feel insecure
>    about using such networks at all.  In order to support
authentication

I don't follow? End user can use SSH and be done with it... Where are
folks to afraid to use a network due to insecurity?

Thomas


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


From exim@www1.ietf.org  Fri May 21 17:56:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06488
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 17:56:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHq2-0007oJ-NC
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LLjwVq030018
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHjI-0005ow-06
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 17:39:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05663
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 17:38:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRHjE-00008u-TZ
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:38:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHhq-0007da-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:37:31 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHgf-0007Sw-06
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:36:18 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRHQJ-0007YW-2B
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:19:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBr-0000pt-PI; Fri, 21 May 2004 17:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0z-0002vT-1B
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02024
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0w-0002X1-Uk
	for pana@ietf.org; Fri, 21 May 2004 16:53:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGz2-0002Av-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:12 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvq-0001bP-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:54 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY300E010EZXB@mailout2.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:23 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY3005NZ0EYL2@mailout2.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:23 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:22 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Please see below for Thomas Narten's review comments on the
usage-scenarios draft.

Chairs note: The current I-D seems like it will benefit from a re-write.
It has text that is not essential to answering the fundamental
questions. The text can be condensed. While doing that, we can also
reduce it to an appendix section in the requirements draft, and reduce
the document load.

- Chairs

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:53 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt

2004-05-20 review of -06:

Overall, a weak and unconvincing document. But probably harmless.

Need to get verification from DSL and CDMA2000 community on their
sections and whether pana is of any real interest to them.

abstract says:

>    Network access authentication is a function that is typically
>    required in most scenarios.

please change "most" to "many". Far from clear that this is required
in "most" scenarios.

Nits:

"PANA" acronym should be expanded in title (see ID nits)

The acronyms need definitions in some cases. E.g.:

>    MSC: Mobile Switching Center
>    MT: Mobile Termination
>    VLR: Visiting Location Register

mean nothing to me. There are others too that are not obvious. Expand
their meaning a bit?

normative references are not right. Many of the listed ones appear to
be non-normative.

>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods.
>    Among the various types of link-layers, only IEEE 802 defines how
to
>    carry EAP on the link-layer [802.1X].  Other link-layers resort to
>    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
>    carrying EAP. The ungainly insertion of this extra layer incurs
>    additional round-trips at connection time, generates overhead of
PPP
>    processing even for subsequent data packets, and forces the network
>    topology into a point-to-point model. EAP could achieve greater
>    applicability if it could be carried directly over IP. That way,
the
>    resulting IP packets could be carried over any link technology
>    without incurring additional cost or limitation on the
architectures.

would a PPP person agree with this characterization? (need to check)

>    In the absence of such lower-layer security and authentication
>    mechanism not only are service providers unable to control the
>    unauthorized use of their networks but also end-users feel insecure
>    about using such networks at all.  In order to support
authentication

I don't follow? End user can use SSH and be done with it... Where are
folks to afraid to use a network due to insecurity?

Thomas


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



From exim@www1.ietf.org  Fri May 21 17:57:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06529
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 17:57:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHq3-0007p4-0K
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LLjwQs030053
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHjJ-0005p4-1c
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 17:39:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05671
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 17:38:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRHjG-000096-Bs
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:38:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHhr-0007dq-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:37:32 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHgg-0007Sw-01
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:36:18 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRHPo-0007Y9-A4
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:18:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBr-0000pl-FS; Fri, 21 May 2004 17:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0y-0002vQ-7n
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02020
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0v-0002Wp-U5
	for pana@ietf.org; Fri, 21 May 2004 16:53:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGz0-0002Af-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:11 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvp-0001b9-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:53 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY3005010F1JH@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:25 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300AK60F09P@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:25 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:24 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <006301c43f74$d2f8bf50$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD review comments on draft-ietf-pana-threats-eval-04.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Please see below for Thomas Narten's review comments on the pana-threats
draft.

- Chairs

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:51 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD review comments on draft-ietf-pana-threats-eval-04.txt

Note: for all the review comments, let's discuss today (if necessary),
then  forward to authors/WG.

2004-05-21 review of -04

>    Authentication Server (AS)  
>      
>       An entity that authenticates the PANA client. It may be
co-located  
>       with PANA authentication agent or part of the back-end  
>       infrastructure.  

Here, no distinction is made between Local AS and Home AS. But below:

>      1) PAA and AS: PaC belonging to the same administrative domain as

>         the AS, often needs to use resources provided by PAA that  
>         belongs to another administrative domain. PAA authenticates
the  

Here, it seems it is asume AS is Home AS. 

>      3) PaC and AS: PaC and AS belong to the same administrative
domain  
>         and share a trust relationship. When PaC uses a different
domain  

Same here. Please clarify.


>    It is possible that some of the entities like PAA, AS and EP are

>    co-located. In those cases, it can be safely assumed that there are

>    no significant external threats.  

Doesn't make sense. there is still the PAC-PAA path... Oh, you are
talking only about among the three. Could be more clear (like just
mention you are talking here about communication amoung the three
entities).

>    PANA MUST be able to prevent service theft. In some cases e.g. non-

>    shared links, it is sufficient to provide access control
information  
>    like IP address, MAC address, etc., to EP, which in turn can
prevent  
>    unauthorized users from gaining access to the network by policing
the  
>    packets for matching addresses. In the case of shared links, this  
>    information is not sufficient to prevent service theft. PANA MUST
be  
>    able to bootstrap a shared secret between the PaC and PAA which can

>    be further used to setup a security association (e.g., IPsec)
between  
>    PaC and EP to prevent service theft on shared links.   

Seems wrong. Even in unshared links, if the authorized client
disconnects, and an intruder gets on the link, it can continue using
the DIs.

>    Requirement 9  
>      
>    PANA SHOULD not assume that the PaC has acquired an IP address
before  
>    PANA begins.   

Needs updating.  (also in summary)

>    In environments where the link is shared, this threat is present as

>    any node can pretend to be a PAA. Even if the nodes are
authenticated  
>    at layer 2, this threat is present. It is difficult to protect the

>    discovery process, as there is no a priori trust relationship
between  
>    PAA and PaC. It might be possible for the EP to filter out the  
>    packets coming from PaC that resembles PAA packets and hence this  
>    threat can be prevented in such environments.  

I don't follow. on a shared LAN, its not clear traffic has to go
through the EP. Are there some assumptions going on here?

>    Requirement 1  
>      
>    PANA MUST not assume that the discovery process is protected.
Since,  
>    it is difficult to protect the discovery process, the security-  
>    critical information exchanged during the discovery process SHOULD
be  
>    limited.  

More like discovery should be treated as a hint, and reverified at a
higher layer before accepting as valid. Is the actual requirement that
the PAA  must authenticate itself to the client, to prevent spoofing
during the discovery process?


>        o All the PaCs may be authenticated to the access network at  
>           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
>           association with layer 2 authentication agent (e.g., 802.11

>           [IEEE-802.11] Access point), but still do not trust each  
>           other.  

not sure I follow. In what  way do they not trust each other? What are
the implications, and what does PANA have to do with this?

Nits:

title needs to expand PANA

>    T6.1.1: A malicious node can pretend to be a PAA by sending a
spoofed  
>    advertisement.  

subsubsection headings seem off (all have T in front, and are indented
like normal text)


>    In the following discussion, any reference to link that is not
shared  

s/to/to a/

>      2) PAA and EP: PAA and EP belong to the same administrative
domain.  

s/PAA/The PAA/

>      3) PaC and AS: PaC and AS belong to the same administrative
domain  

s/PaC/The PaC/

NOte: there are multiple places where terms like PAA are used where
you need to use "the PAA", or "a PAA", etc.

>    Some authentication protocols e.g., EAP, has a special message to  

s/has/have/

>    PANA MUST be able to prevent service theft. In some cases e.g. non-


s/e.g./, e.g.,/ (do this throughout probably)


Thomas


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



From exim@www1.ietf.org  Fri May 21 17:57:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06549
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 17:57:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHq3-0007pw-9o
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LLjxur030115
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 17:45:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHjK-0005pA-Ud
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 17:39:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05682
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 17:38:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRHjI-00009T-89
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:39:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHhv-0007eM-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:37:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHgh-0007Sw-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:36:19 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRHPK-0007Xm-AB
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:18:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHBq-0000pW-OO; Fri, 21 May 2004 17:04:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH0w-0002vL-Sq
	for pana@optimus.ietf.org; Fri, 21 May 2004 16:53:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02013
	for <pana@ietf.org>; Fri, 21 May 2004 16:53:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRH0u-0002Wk-PZ
	for pana@ietf.org; Fri, 21 May 2004 16:53:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGyz-0002AS-00
	for pana@ietf.org; Fri, 21 May 2004 16:51:09 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGvo-0001b9-00
	for pana@ietf.org; Fri, 21 May 2004 16:47:53 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY3005010EXJF@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:21 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300MPN0EXIF@mailout3.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 05:47:21 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30013N0EU2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 05:47:21 +0900 (KST)
Date: Fri, 21 May 2004 13:47:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <005701c43f74$d0c64ef0$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Pana] FW: AD review of draft-ietf-pana-requirements-07.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

And this is for the requirements draft.

Alper


-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Friday, May 21, 2004 8:54 AM
To: Basavaraj.Patil@nokia.com; Alper Yegin
Cc: Margaret Wasserman
Subject: AD review of draft-ietf-pana-requirements-07.txt

> 4.2. IP Address Assignment 
>     
>    Assigning an IP address to the client is outside the scope of PANA.

>    PANA protocol design MAY require the PaC to configure an IP address

>    before using this protocol. Allocating IP addresses to 
>    unauthenticated PaCs may create security vulnerabilities, such as
IP 

Please update to reflect current WG decisions. I.e., PANA assumes an
IP address exists and just uses it.

>    links. Furthermore, two nodes on the same IP subnet do not 
>    necessarily satisfy this requirement, as they can be more than one 
>    hop away from each other [MULTILINK]. A PAA can be on the NAS 

we don't have multilinks... Probably best to just delete this text.


Thomas


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



From pana-admin@ietf.org  Fri May 21 17:59:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06676
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 17:59:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHr5-00084U-6G; Fri, 21 May 2004 17:47:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHnt-00071A-8R
	for pana@optimus.ietf.org; Fri, 21 May 2004 17:43:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06030
	for <pana@ietf.org>; Fri, 21 May 2004 17:43:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRHnq-0000cO-JC
	for pana@ietf.org; Fri, 21 May 2004 17:43:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHn0-0000YP-00
	for pana@ietf.org; Fri, 21 May 2004 17:42:51 -0400
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHm9-0000P4-00
	for pana@ietf.org; Fri, 21 May 2004 17:41:57 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id i4LLfQoK021685;
	Fri, 21 May 2004 14:41:26 -0700 (PDT)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id i4LLfPcc010684;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1])
	by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11) with ESMTP id i4LLfPth002156;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11/Submit) id i4LLfPsj002153;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16558.30597.335081.536774@gargle.gargle.HOWL>
Date: Fri, 21 May 2004 17:41:25 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: pana@ietf.org, Thomas Narten <narten@us.ibm.com>
Subject: Re: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
In-Reply-To: Alper Yegin's message of 21 May 2004 13:47:19
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
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=AWL 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

Alper Yegin (actually Thomas Narten) writes:
> >    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
> >    natural way to encapsulate many different authentication methods.
> >    Among the various types of link-layers, only IEEE 802 defines how
> to
> >    carry EAP on the link-layer [802.1X].  Other link-layers resort to
> >    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
> >    carrying EAP. The ungainly insertion of this extra layer incurs
> >    additional round-trips at connection time, generates overhead of
> PPP
> >    processing even for subsequent data packets, and forces the network
> >    topology into a point-to-point model. EAP could achieve greater
> >    applicability if it could be carried directly over IP. That way,
> the
> >    resulting IP packets could be carried over any link technology
> >    without incurring additional cost or limitation on the
> architectures.
> 
> would a PPP person agree with this characterization? (need to check)

As a lurking PPP person, I can say that I would not quite agree with
the characterization, and that it does seem like it needs some
wordsmithing.

PPP is a link layer protocol.  When you use EAP on PPP, you are using
EAP atop a link layer protocol, just as intended.  It's simply untrue
that only IEEE 802 is a link layer protocol.

The issue, of course, is that some folks seem to feel the need to run
one link layer atop another (e.g., PPP atop Ethernet) to achieve a
high level of overhead.  I do agree with the characterization of this
construct (particularly when done via PPPoE) as "ungainly."

A simple rewrite:

   The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
   natural way to encapsulate many different authentication methods
   over many different link layers, including IEEE 802 [802.1X] and
   PPP.

   Some implementations have layered PPP (itself a link layer) atop
   other link layers (such as IEEE 802) as a method of carrying EAP.
   Since EAP runs over IEEE 802, this is unnecessary and
   counterproductive.

-- 
James Carlson, IP Systems Group                <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677

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


From exim@www1.ietf.org  Fri May 21 18:07:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07471
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 18:07:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRI7J-0003Mm-JL
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 18:03:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LM3ncf012933
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 18:03:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRI4Q-00029e-4N
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 18:00:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06776
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 18:00:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRI4N-00020V-Ay
	for pana-web-archive@ietf.org; Fri, 21 May 2004 18:00:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRI3O-0001vA-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:59:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRI2T-0001pg-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 17:58:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHr5-00084U-6G; Fri, 21 May 2004 17:47:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRHnt-00071A-8R
	for pana@optimus.ietf.org; Fri, 21 May 2004 17:43:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06030
	for <pana@ietf.org>; Fri, 21 May 2004 17:43:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRHnq-0000cO-JC
	for pana@ietf.org; Fri, 21 May 2004 17:43:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHn0-0000YP-00
	for pana@ietf.org; Fri, 21 May 2004 17:42:51 -0400
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHm9-0000P4-00
	for pana@ietf.org; Fri, 21 May 2004 17:41:57 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id i4LLfQoK021685;
	Fri, 21 May 2004 14:41:26 -0700 (PDT)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id i4LLfPcc010684;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1])
	by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11) with ESMTP id i4LLfPth002156;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11/Submit) id i4LLfPsj002153;
	Fri, 21 May 2004 17:41:25 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16558.30597.335081.536774@gargle.gargle.HOWL>
Date: Fri, 21 May 2004 17:41:25 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: pana@ietf.org, Thomas Narten <narten@us.ibm.com>
Subject: Re: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
In-Reply-To: Alper Yegin's message of 21 May 2004 13:47:19
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alper Yegin (actually Thomas Narten) writes:
> >    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
> >    natural way to encapsulate many different authentication methods.
> >    Among the various types of link-layers, only IEEE 802 defines how
> to
> >    carry EAP on the link-layer [802.1X].  Other link-layers resort to
> >    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
> >    carrying EAP. The ungainly insertion of this extra layer incurs
> >    additional round-trips at connection time, generates overhead of
> PPP
> >    processing even for subsequent data packets, and forces the network
> >    topology into a point-to-point model. EAP could achieve greater
> >    applicability if it could be carried directly over IP. That way,
> the
> >    resulting IP packets could be carried over any link technology
> >    without incurring additional cost or limitation on the
> architectures.
> 
> would a PPP person agree with this characterization? (need to check)

As a lurking PPP person, I can say that I would not quite agree with
the characterization, and that it does seem like it needs some
wordsmithing.

PPP is a link layer protocol.  When you use EAP on PPP, you are using
EAP atop a link layer protocol, just as intended.  It's simply untrue
that only IEEE 802 is a link layer protocol.

The issue, of course, is that some folks seem to feel the need to run
one link layer atop another (e.g., PPP atop Ethernet) to achieve a
high level of overhead.  I do agree with the characterization of this
construct (particularly when done via PPPoE) as "ungainly."

A simple rewrite:

   The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
   natural way to encapsulate many different authentication methods
   over many different link layers, including IEEE 802 [802.1X] and
   PPP.

   Some implementations have layered PPP (itself a link layer) atop
   other link layers (such as IEEE 802) as a method of carrying EAP.
   Since EAP runs over IEEE 802, this is unnecessary and
   counterproductive.

-- 
James Carlson, IP Systems Group                <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677

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



From pana-admin@ietf.org  Fri May 21 18:26:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09138
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 18:26:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIK4-0006fk-P7; Fri, 21 May 2004 18:17:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIC3-00050s-Gy
	for pana@optimus.ietf.org; Fri, 21 May 2004 18:08:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07614
	for <pana@ietf.org>; Fri, 21 May 2004 18:08:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRIC0-0002g4-Nu
	for pana@ietf.org; Fri, 21 May 2004 18:08:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRIB2-0002aT-00
	for pana@ietf.org; Fri, 21 May 2004 18:07:40 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRIA3-0002TF-00
	for pana@ietf.org; Fri, 21 May 2004 18:06:40 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY300601423PN@mailout1.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 07:06:03 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300JLF4222L@mailout1.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 07:06:02 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30010L41Y2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 07:06:02 +0900 (KST)
Date: Fri, 21 May 2004 15:05:59 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <16558.30597.335081.536774@gargle.gargle.HOWL>
To: "'James Carlson'" <james.d.carlson@sun.com>
Cc: pana@ietf.org, "'Thomas Narten'" <narten@us.ibm.com>
Message-id: <006a01c43f7f$cea96160$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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

> Alper Yegin (actually Thomas Narten) writes:
> > >    The Extensible Authentication Protocol (EAP) [RFC2284bis]
offers a
> > >    natural way to encapsulate many different authentication
methods.
> > >    Among the various types of link-layers, only IEEE 802 defines
how
> > to
> > >    carry EAP on the link-layer [802.1X].  Other link-layers resort
to
> > >    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way
of
> > >    carrying EAP. The ungainly insertion of this extra layer incurs
> > >    additional round-trips at connection time, generates overhead
of
> > PPP
> > >    processing even for subsequent data packets, and forces the
network
> > >    topology into a point-to-point model. EAP could achieve greater
> > >    applicability if it could be carried directly over IP. That
way,
> > the
> > >    resulting IP packets could be carried over any link technology
> > >    without incurring additional cost or limitation on the
> > architectures.
> >
> > would a PPP person agree with this characterization? (need to check)
> 
> As a lurking PPP person, I can say that I would not quite agree with
> the characterization, and that it does seem like it needs some
> wordsmithing.
> 
> PPP is a link layer protocol.  When you use EAP on PPP, you are using
> EAP atop a link layer protocol, just as intended.  It's simply untrue
> that only IEEE 802 is a link layer protocol.
> 
> The issue, of course, is that some folks seem to feel the need to run
> one link layer atop another (e.g., PPP atop Ethernet) to achieve a
> high level of overhead.  I do agree with the characterization of this
> construct (particularly when done via PPPoE) as "ungainly."
> 
> A simple rewrite:
> 
>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods
>    over many different link layers, including IEEE 802 [802.1X] and
>    PPP.
> 
>    Some implementations have layered PPP (itself a link layer) atop
>    other link layers (such as IEEE 802) as a method of carrying EAP.
>    Since EAP runs over IEEE 802, this is unnecessary and
>    counterproductive.

Aside from the IEEE 802 and PPPoE context, there is also PPP over ATM,
and PPP over cdma2000 networks. 

Btw, even in IEEE 802-based DSL networks, using 802.1X would have issues
if it has to go through bridges (e.g., CPE modem, DSLAM).

Alper




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


From exim@www1.ietf.org  Fri May 21 18:38:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10080
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 18:38:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIcB-0001ns-Se
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 18:35:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LMZhH6006931
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 18:35:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIUV-0000go-G9
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 18:27:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09274
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 18:27:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRIUS-0004Qt-GB
	for pana-web-archive@ietf.org; Fri, 21 May 2004 18:27:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRITR-0004Kt-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 18:26:42 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRIST-0004Fc-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 18:25:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIK4-0006fk-P7; Fri, 21 May 2004 18:17:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRIC3-00050s-Gy
	for pana@optimus.ietf.org; Fri, 21 May 2004 18:08:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07614
	for <pana@ietf.org>; Fri, 21 May 2004 18:08:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRIC0-0002g4-Nu
	for pana@ietf.org; Fri, 21 May 2004 18:08:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRIB2-0002aT-00
	for pana@ietf.org; Fri, 21 May 2004 18:07:40 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRIA3-0002TF-00
	for pana@ietf.org; Fri, 21 May 2004 18:06:40 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HY300601423PN@mailout1.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 07:06:03 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HY300JLF4222L@mailout1.samsung.com> for pana@ietf.org; Sat,
 22 May 2004 07:06:02 +0900 (KST)
Received: from Alperyegin ([105.253.155.57])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HY30010L41Y2M@mmp2.samsung.com> for pana@ietf.org;
 Sat, 22 May 2004 07:06:02 +0900 (KST)
Date: Fri, 21 May 2004 15:05:59 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <16558.30597.335081.536774@gargle.gargle.HOWL>
To: "'James Carlson'" <james.d.carlson@sun.com>
Cc: pana@ietf.org, "'Thomas Narten'" <narten@us.ibm.com>
Message-id: <006a01c43f7f$cea96160$c64ca143@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

> Alper Yegin (actually Thomas Narten) writes:
> > >    The Extensible Authentication Protocol (EAP) [RFC2284bis]
offers a
> > >    natural way to encapsulate many different authentication
methods.
> > >    Among the various types of link-layers, only IEEE 802 defines
how
> > to
> > >    carry EAP on the link-layer [802.1X].  Other link-layers resort
to
> > >    using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way
of
> > >    carrying EAP. The ungainly insertion of this extra layer incurs
> > >    additional round-trips at connection time, generates overhead
of
> > PPP
> > >    processing even for subsequent data packets, and forces the
network
> > >    topology into a point-to-point model. EAP could achieve greater
> > >    applicability if it could be carried directly over IP. That
way,
> > the
> > >    resulting IP packets could be carried over any link technology
> > >    without incurring additional cost or limitation on the
> > architectures.
> >
> > would a PPP person agree with this characterization? (need to check)
> 
> As a lurking PPP person, I can say that I would not quite agree with
> the characterization, and that it does seem like it needs some
> wordsmithing.
> 
> PPP is a link layer protocol.  When you use EAP on PPP, you are using
> EAP atop a link layer protocol, just as intended.  It's simply untrue
> that only IEEE 802 is a link layer protocol.
> 
> The issue, of course, is that some folks seem to feel the need to run
> one link layer atop another (e.g., PPP atop Ethernet) to achieve a
> high level of overhead.  I do agree with the characterization of this
> construct (particularly when done via PPPoE) as "ungainly."
> 
> A simple rewrite:
> 
>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods
>    over many different link layers, including IEEE 802 [802.1X] and
>    PPP.
> 
>    Some implementations have layered PPP (itself a link layer) atop
>    other link layers (such as IEEE 802) as a method of carrying EAP.
>    Since EAP runs over IEEE 802, this is unnecessary and
>    counterproductive.

Aside from the IEEE 802 and PPPoE context, there is also PPP over ATM,
and PPP over cdma2000 networks. 

Btw, even in IEEE 802-based DSL networks, using 802.1X would have issues
if it has to go through bridges (e.g., CPE modem, DSLAM).

Alper




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



From pana-admin@ietf.org  Fri May 21 20:19:15 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15088
	for <pana-archive@lists.ietf.org>; Fri, 21 May 2004 20:19:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKBF-0006Hx-DM; Fri, 21 May 2004 20:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJxd-0002zu-UT
	for pana@optimus.ietf.org; Fri, 21 May 2004 20:01:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14212
	for <pana@ietf.org>; Fri, 21 May 2004 20:01:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRJxb-0005S3-Vp
	for pana@ietf.org; Fri, 21 May 2004 20:01:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRJwe-0005M0-00
	for pana@ietf.org; Fri, 21 May 2004 20:00:57 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRJvo-0005GO-00
	for pana@ietf.org; Fri, 21 May 2004 20:00:04 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 22 May 2004 00:00:04 -0000
Message-ID: <027801c43f8f$ba0799b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper.yegin@samsung.com>, <pana@ietf.org>
Cc: "Thomas Narten" <narten@us.ibm.com>
References: <006301c43f74$d2f8bf50$c64ca143@sisa.samsung.com>
Subject: Re: [Pana] FW: AD review comments on draft-ietf-pana-threats-eval-04.txt
Date: Fri, 21 May 2004 17:00:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL 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

 My responses for the ones that has questions or clarifications below :

> 
> >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> 
> >    shared links, it is sufficient to provide access control
> information  
> >    like IP address, MAC address, etc., to EP, which in turn can
> prevent  
> >    unauthorized users from gaining access to the network by policing
> the  
> >    packets for matching addresses. In the case of shared links, this  
> >    information is not sufficient to prevent service theft. PANA MUST
> be  
> >    able to bootstrap a shared secret between the PaC and PAA which can
> 
> >    be further used to setup a security association (e.g., IPsec)
> between  
> >    PaC and EP to prevent service theft on shared links.   
> 
> Seems wrong. Even in unshared links, if the authorized client
> disconnects, and an intruder gets on the link, it can continue using
> the DIs.
> 
When an authorized client disconnects, the filters at the enforcement point should
be reset appropriately so that any one using the same DI is not allowed access.
Are you saying that the client was disconnected without the access network (EP/PAA)
knowing ? Could you clarify ?

> >    Requirement 9  
> >      
> >    PANA SHOULD not assume that the PaC has acquired an IP address
> before  
> >    PANA begins.   
> 
> Needs updating.  (also in summary)
> 
Okay.

> >    In environments where the link is shared, this threat is present as
> 
> >    any node can pretend to be a PAA. Even if the nodes are
> authenticated  
> >    at layer 2, this threat is present. It is difficult to protect the
> 
> >    discovery process, as there is no a priori trust relationship
> between  
> >    PAA and PaC. It might be possible for the EP to filter out the  
> >    packets coming from PaC that resembles PAA packets and hence this  
> >    threat can be prevented in such environments.  
> 
> I don't follow. on a shared LAN, its not clear traffic has to go
> through the EP. Are there some assumptions going on here?
> 
EP is the policy enforcement point. All data has to go through it. In 802.11, it could
be the AP. In regular LAN, it could be the switch or the router. Perhaps, it is not
explicitly stated. From the requirements document,

Enforcement Point (EP) 
    
        A node on the access network where per-packet enforcement  
        policies (i.e., filters) are applied on the inbound  
        and outbound traffic of client devices. Information such as DI  
        and (optionally) cryptographic keys are provided by PAA per  
        client for constructing filters on the EP. 

Do you think we need explicit clarification  that EP sees all packets or some such thing ?


> >    Requirement 1  
> >      
> >    PANA MUST not assume that the discovery process is protected.
> Since,  
> >    it is difficult to protect the discovery process, the security-  
> >    critical information exchanged during the discovery process SHOULD
> be  
> >    limited.  
> 
> More like discovery should be treated as a hint, and reverified at a
> higher layer before accepting as valid. Is the actual requirement that
> the PAA  must authenticate itself to the client, to prevent spoofing
> during the discovery process?
> 
No. It tries to say that the discovery is just a hint and don't assume that everything
is true. You can't do much about it anyway because you don't have a trust relationship
with the node (PAA) you are talking to.  So, the PANA protocol MUST not assume that the
channel is protected during discovery. Hence, PAA should not include anything that is
sensitive as the PaC has no way of believing it. The other way is to reverify the contents
once you are successfully authenticated so that you know whether you are fooled or not.
If you are fooled, you have to start the process again and this go on forever if the malicious
node can spoof the information. If you never include it in the discovery and include only
when it is safe i.e., after successful authentication protected by MAC, it would be better.
On unshared links, you can trust the information coming from the other end and hence you
may include sensitive information. But, i am not sure whether it is worth it.

> 
> >        o All the PaCs may be authenticated to the access network at  
> >           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
> >           association with layer 2 authentication agent (e.g., 802.11
> 
> >           [IEEE-802.11] Access point), but still do not trust each  
> >           other.  
> 
> not sure I follow. In what  way do they not trust each other? What are
> the implications, and what does PANA have to do with this?
> 
To clarify, it says that the PaC's don't trust each other as in a trusted environment
like the office. This means it is a hostile environment to start with. Any node can
act like PAA, any node can spoof packets like you, any node can eavesdrop on you etc.
On such links, PANA should be designed such a way that only the "good" nodes are
authenticated and PaC's authenticate only to the "good" PAA. 

> Nits:
> 
> title needs to expand PANA
> 
> >    T6.1.1: A malicious node can pretend to be a PAA by sending a
> spoofed  
> >    advertisement.  
> 
> subsubsection headings seem off (all have T in front, and are indented
> like normal text)
> 
I was merely meant it as a way to number it. I can try and indent the following lines
if that would make it look better.

> 
> >    In the following discussion, any reference to link that is not
> shared  
> 
> s/to/to a/
> 
> >      2) PAA and EP: PAA and EP belong to the same administrative
> domain.  
> 
> s/PAA/The PAA/
> 
> >      3) PaC and AS: PaC and AS belong to the same administrative
> domain  
> 
> s/PaC/The PaC/
> 
> NOte: there are multiple places where terms like PAA are used where
> you need to use "the PAA", or "a PAA", etc.
> 
> >    Some authentication protocols e.g., EAP, has a special message to  
> 
> s/has/have/
> 
> >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> 
> 
> s/e.g./, e.g.,/ (do this throughout probably)
> 
> 
Ok.

-mohan

> Thomas
> 
> 
> _______________________________________________
> 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 May 21 20:24:18 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15418
	for <pana-archive@odin.ietf.org>; Fri, 21 May 2004 20:24:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKH3-0007hf-PC
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 20:22:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M0M1fC029606
	for pana-archive@odin.ietf.org; Fri, 21 May 2004 20:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKFs-0007Pj-3K
	for pana-web-archive@optimus.ietf.org; Fri, 21 May 2004 20:20:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15186
	for <pana-web-archive@ietf.org>; Fri, 21 May 2004 20:20:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRKFp-0007Wc-T3
	for pana-web-archive@ietf.org; Fri, 21 May 2004 20:20:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKEs-0007QH-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 20:19:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRKDt-0007Ib-00
	for pana-web-archive@ietf.org; Fri, 21 May 2004 20:18:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKBF-0006Hx-DM; Fri, 21 May 2004 20:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJxd-0002zu-UT
	for pana@optimus.ietf.org; Fri, 21 May 2004 20:01:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14212
	for <pana@ietf.org>; Fri, 21 May 2004 20:01:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRJxb-0005S3-Vp
	for pana@ietf.org; Fri, 21 May 2004 20:01:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRJwe-0005M0-00
	for pana@ietf.org; Fri, 21 May 2004 20:00:57 -0400
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRJvo-0005GO-00
	for pana@ietf.org; Fri, 21 May 2004 20:00:04 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 22 May 2004 00:00:04 -0000
Message-ID: <027801c43f8f$ba0799b0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper.yegin@samsung.com>, <pana@ietf.org>
Cc: "Thomas Narten" <narten@us.ibm.com>
References: <006301c43f74$d2f8bf50$c64ca143@sisa.samsung.com>
Subject: Re: [Pana] FW: AD review comments on draft-ietf-pana-threats-eval-04.txt
Date: Fri, 21 May 2004 17:00:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 My responses for the ones that has questions or clarifications below :

> 
> >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> 
> >    shared links, it is sufficient to provide access control
> information  
> >    like IP address, MAC address, etc., to EP, which in turn can
> prevent  
> >    unauthorized users from gaining access to the network by policing
> the  
> >    packets for matching addresses. In the case of shared links, this  
> >    information is not sufficient to prevent service theft. PANA MUST
> be  
> >    able to bootstrap a shared secret between the PaC and PAA which can
> 
> >    be further used to setup a security association (e.g., IPsec)
> between  
> >    PaC and EP to prevent service theft on shared links.   
> 
> Seems wrong. Even in unshared links, if the authorized client
> disconnects, and an intruder gets on the link, it can continue using
> the DIs.
> 
When an authorized client disconnects, the filters at the enforcement point should
be reset appropriately so that any one using the same DI is not allowed access.
Are you saying that the client was disconnected without the access network (EP/PAA)
knowing ? Could you clarify ?

> >    Requirement 9  
> >      
> >    PANA SHOULD not assume that the PaC has acquired an IP address
> before  
> >    PANA begins.   
> 
> Needs updating.  (also in summary)
> 
Okay.

> >    In environments where the link is shared, this threat is present as
> 
> >    any node can pretend to be a PAA. Even if the nodes are
> authenticated  
> >    at layer 2, this threat is present. It is difficult to protect the
> 
> >    discovery process, as there is no a priori trust relationship
> between  
> >    PAA and PaC. It might be possible for the EP to filter out the  
> >    packets coming from PaC that resembles PAA packets and hence this  
> >    threat can be prevented in such environments.  
> 
> I don't follow. on a shared LAN, its not clear traffic has to go
> through the EP. Are there some assumptions going on here?
> 
EP is the policy enforcement point. All data has to go through it. In 802.11, it could
be the AP. In regular LAN, it could be the switch or the router. Perhaps, it is not
explicitly stated. From the requirements document,

Enforcement Point (EP) 
    
        A node on the access network where per-packet enforcement  
        policies (i.e., filters) are applied on the inbound  
        and outbound traffic of client devices. Information such as DI  
        and (optionally) cryptographic keys are provided by PAA per  
        client for constructing filters on the EP. 

Do you think we need explicit clarification  that EP sees all packets or some such thing ?


> >    Requirement 1  
> >      
> >    PANA MUST not assume that the discovery process is protected.
> Since,  
> >    it is difficult to protect the discovery process, the security-  
> >    critical information exchanged during the discovery process SHOULD
> be  
> >    limited.  
> 
> More like discovery should be treated as a hint, and reverified at a
> higher layer before accepting as valid. Is the actual requirement that
> the PAA  must authenticate itself to the client, to prevent spoofing
> during the discovery process?
> 
No. It tries to say that the discovery is just a hint and don't assume that everything
is true. You can't do much about it anyway because you don't have a trust relationship
with the node (PAA) you are talking to.  So, the PANA protocol MUST not assume that the
channel is protected during discovery. Hence, PAA should not include anything that is
sensitive as the PaC has no way of believing it. The other way is to reverify the contents
once you are successfully authenticated so that you know whether you are fooled or not.
If you are fooled, you have to start the process again and this go on forever if the malicious
node can spoof the information. If you never include it in the discovery and include only
when it is safe i.e., after successful authentication protected by MAC, it would be better.
On unshared links, you can trust the information coming from the other end and hence you
may include sensitive information. But, i am not sure whether it is worth it.

> 
> >        o All the PaCs may be authenticated to the access network at  
> >           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
> >           association with layer 2 authentication agent (e.g., 802.11
> 
> >           [IEEE-802.11] Access point), but still do not trust each  
> >           other.  
> 
> not sure I follow. In what  way do they not trust each other? What are
> the implications, and what does PANA have to do with this?
> 
To clarify, it says that the PaC's don't trust each other as in a trusted environment
like the office. This means it is a hostile environment to start with. Any node can
act like PAA, any node can spoof packets like you, any node can eavesdrop on you etc.
On such links, PANA should be designed such a way that only the "good" nodes are
authenticated and PaC's authenticate only to the "good" PAA. 

> Nits:
> 
> title needs to expand PANA
> 
> >    T6.1.1: A malicious node can pretend to be a PAA by sending a
> spoofed  
> >    advertisement.  
> 
> subsubsection headings seem off (all have T in front, and are indented
> like normal text)
> 
I was merely meant it as a way to number it. I can try and indent the following lines
if that would make it look better.

> 
> >    In the following discussion, any reference to link that is not
> shared  
> 
> s/to/to a/
> 
> >      2) PAA and EP: PAA and EP belong to the same administrative
> domain.  
> 
> s/PAA/The PAA/
> 
> >      3) PaC and AS: PaC and AS belong to the same administrative
> domain  
> 
> s/PaC/The PaC/
> 
> NOte: there are multiple places where terms like PAA are used where
> you need to use "the PAA", or "a PAA", etc.
> 
> >    Some authentication protocols e.g., EAP, has a special message to  
> 
> s/has/have/
> 
> >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> 
> 
> s/e.g./, e.g.,/ (do this throughout probably)
> 
> 
Ok.

-mohan

> Thomas
> 
> 
> _______________________________________________
> 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 May 22 00:46:42 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27151
	for <pana-archive@lists.ietf.org>; Sat, 22 May 2004 00:46:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROKf-0006p8-Hd; Sat, 22 May 2004 00:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROGv-00061b-MZ
	for pana@optimus.ietf.org; Sat, 22 May 2004 00:38:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26243
	for <pana@ietf.org>; Sat, 22 May 2004 00:38:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROGs-0004Ie-Lt
	for pana@ietf.org; Sat, 22 May 2004 00:38:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROGK-0004Cj-00
	for pana@ietf.org; Sat, 22 May 2004 00:37:33 -0400
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROF9-00044F-00
	for pana@ietf.org; Sat, 22 May 2004 00:36:19 -0400
Received: from piuha.net (p2.piuha.net [131.160.192.2])
	by p2.piuha.net (Postfix) with ESMTP
	id 88E4189881; Sat, 22 May 2004 07:36:13 +0300 (EEST)
Message-ID: <40AED7E0.8070905@piuha.net>
Date: Sat, 22 May 2004 07:32:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Carlson <james.d.carlson@sun.com>
Cc: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
        Thomas Narten <narten@us.ibm.com>
Subject: Re: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com> <16558.30597.335081.536774@gargle.gargle.HOWL>
In-Reply-To: <16558.30597.335081.536774@gargle.gargle.HOWL>
Content-Type: text/plain; charset=us-ascii; format=flowed
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=AWL 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

James Carlson wrote:
> Alper Yegin (actually Thomas Narten) writes:
> 
>>>   The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>>>   natural way to encapsulate many different authentication methods.
>>>   Among the various types of link-layers, only IEEE 802 defines how
>>
>>to
>>
>>>   carry EAP on the link-layer [802.1X].  Other link-layers resort to
>>>   using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
>>>   carrying EAP. The ungainly insertion of this extra layer incurs
>>>   additional round-trips at connection time, generates overhead of
>>
>>PPP
>>
>>>   processing even for subsequent data packets, and forces the network
>>>   topology into a point-to-point model. EAP could achieve greater
>>>   applicability if it could be carried directly over IP. That way,
>>
>>the
>>
>>>   resulting IP packets could be carried over any link technology
>>>   without incurring additional cost or limitation on the
>>
>>architectures.
>>
>>would a PPP person agree with this characterization? (need to check)
> 
> 
> As a lurking PPP person, I can say that I would not quite agree with
> the characterization, and that it does seem like it needs some
> wordsmithing.
> 
> PPP is a link layer protocol.  When you use EAP on PPP, you are using
> EAP atop a link layer protocol, just as intended.  It's simply untrue
> that only IEEE 802 is a link layer protocol.
> 
> The issue, of course, is that some folks seem to feel the need to run
> one link layer atop another (e.g., PPP atop Ethernet) to achieve a
> high level of overhead.  I do agree with the characterization of this
> construct (particularly when done via PPPoE) as "ungainly."
> 
> A simple rewrite:
> 
>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods
>    over many different link layers, including IEEE 802 [802.1X] and
>    PPP.
> 
>    Some implementations have layered PPP (itself a link layer) atop
>    other link layers (such as IEEE 802) as a method of carrying EAP.
>    Since EAP runs over IEEE 802, this is unnecessary and
>    counterproductive.

I agree with James' comments, but I would add that there's
always some overhead and roundtrips in the mechanisms used to
carry EAP and subsequent per-packet cryptographic protection.
Even PANA has it, although its certainly much better than with
PPP. Also, the original text seemed to be saying that with PPP
you are forced into a point-to-point model. That's true, but
isn't the same also true of PANA? I mean you will establish
a shared key between the client and the agent (or the EP). To
me this looks like a point-to-point model and I'm not sure you
can directly talk to the other nodes on the link. But James'
text avoids these problems, so if you'll just that you're fine.

--Jari

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


From exim@www1.ietf.org  Sat May 22 00:53:15 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27613
	for <pana-archive@odin.ietf.org>; Sat, 22 May 2004 00:53:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROUG-0000fj-BK
	for pana-archive@odin.ietf.org; Sat, 22 May 2004 00:51:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M4puE3002578
	for pana-archive@odin.ietf.org; Sat, 22 May 2004 00:51:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROQV-0008Gj-Ed
	for pana-web-archive@optimus.ietf.org; Sat, 22 May 2004 00:48:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27220
	for <pana-web-archive@ietf.org>; Sat, 22 May 2004 00:47:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROQS-0005we-Bu
	for pana-web-archive@ietf.org; Sat, 22 May 2004 00:48:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROPZ-0005ov-00
	for pana-web-archive@ietf.org; Sat, 22 May 2004 00:47:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROOj-0005i8-00
	for pana-web-archive@ietf.org; Sat, 22 May 2004 00:46:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROKf-0006p8-Hd; Sat, 22 May 2004 00:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROGv-00061b-MZ
	for pana@optimus.ietf.org; Sat, 22 May 2004 00:38:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26243
	for <pana@ietf.org>; Sat, 22 May 2004 00:38:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROGs-0004Ie-Lt
	for pana@ietf.org; Sat, 22 May 2004 00:38:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROGK-0004Cj-00
	for pana@ietf.org; Sat, 22 May 2004 00:37:33 -0400
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROF9-00044F-00
	for pana@ietf.org; Sat, 22 May 2004 00:36:19 -0400
Received: from piuha.net (p2.piuha.net [131.160.192.2])
	by p2.piuha.net (Postfix) with ESMTP
	id 88E4189881; Sat, 22 May 2004 07:36:13 +0300 (EEST)
Message-ID: <40AED7E0.8070905@piuha.net>
Date: Sat, 22 May 2004 07:32:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Carlson <james.d.carlson@sun.com>
Cc: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
        Thomas Narten <narten@us.ibm.com>
Subject: Re: [Pana] FW: AD Review comments on draft-ietf-pana-usage-scenarios-06.txt
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com> <16558.30597.335081.536774@gargle.gargle.HOWL>
In-Reply-To: <16558.30597.335081.536774@gargle.gargle.HOWL>
Content-Type: text/plain; charset=us-ascii; format=flowed
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

James Carlson wrote:
> Alper Yegin (actually Thomas Narten) writes:
> 
>>>   The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>>>   natural way to encapsulate many different authentication methods.
>>>   Among the various types of link-layers, only IEEE 802 defines how
>>
>>to
>>
>>>   carry EAP on the link-layer [802.1X].  Other link-layers resort to
>>>   using PPP/PPPoE [RFC1661,RFC2516] as a link-layer agnostic way of
>>>   carrying EAP. The ungainly insertion of this extra layer incurs
>>>   additional round-trips at connection time, generates overhead of
>>
>>PPP
>>
>>>   processing even for subsequent data packets, and forces the network
>>>   topology into a point-to-point model. EAP could achieve greater
>>>   applicability if it could be carried directly over IP. That way,
>>
>>the
>>
>>>   resulting IP packets could be carried over any link technology
>>>   without incurring additional cost or limitation on the
>>
>>architectures.
>>
>>would a PPP person agree with this characterization? (need to check)
> 
> 
> As a lurking PPP person, I can say that I would not quite agree with
> the characterization, and that it does seem like it needs some
> wordsmithing.
> 
> PPP is a link layer protocol.  When you use EAP on PPP, you are using
> EAP atop a link layer protocol, just as intended.  It's simply untrue
> that only IEEE 802 is a link layer protocol.
> 
> The issue, of course, is that some folks seem to feel the need to run
> one link layer atop another (e.g., PPP atop Ethernet) to achieve a
> high level of overhead.  I do agree with the characterization of this
> construct (particularly when done via PPPoE) as "ungainly."
> 
> A simple rewrite:
> 
>    The Extensible Authentication Protocol (EAP) [RFC2284bis] offers a
>    natural way to encapsulate many different authentication methods
>    over many different link layers, including IEEE 802 [802.1X] and
>    PPP.
> 
>    Some implementations have layered PPP (itself a link layer) atop
>    other link layers (such as IEEE 802) as a method of carrying EAP.
>    Since EAP runs over IEEE 802, this is unnecessary and
>    counterproductive.

I agree with James' comments, but I would add that there's
always some overhead and roundtrips in the mechanisms used to
carry EAP and subsequent per-packet cryptographic protection.
Even PANA has it, although its certainly much better than with
PPP. Also, the original text seemed to be saying that with PPP
you are forced into a point-to-point model. That's true, but
isn't the same also true of PANA? I mean you will establish
a shared key between the client and the agent (or the EP). To
me this looks like a point-to-point model and I'm not sure you
can directly talk to the other nodes on the link. But James'
text avoids these problems, so if you'll just that you're fine.

--Jari

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



From pana-admin@ietf.org  Sun May 23 13:12:05 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25649
	for <pana-archive@lists.ietf.org>; Sun, 23 May 2004 13:12:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwRB-00033E-Gi; Sun, 23 May 2004 13:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwNq-0002WK-T2
	for pana@optimus.ietf.org; Sun, 23 May 2004 13:03:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25112
	for <pana@ietf.org>; Sun, 23 May 2004 13:03:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRwNp-0005Nr-2m
	for pana@ietf.org; Sun, 23 May 2004 13:03:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRwMo-000549-00
	for pana@ietf.org; Sun, 23 May 2004 13:02:31 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRwLq-0004nE-00
	for pana@ietf.org; Sun, 23 May 2004 13:01:30 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4NH1SgH029650;
	Mon, 24 May 2004 02:01:28 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4NH1S1r024786;
	Mon, 24 May 2004 02:01:28 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA24783 ; Mon, 24 May 2004 02:01:28 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA14060; Mon, 24 May 2004 02:01:27 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA24107; Mon, 24 May 2004 02:01:27 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4NH1QCR018121;
	Mon, 24 May 2004 02:01:26 +0900 (JST)
Received: from steelhead (iVPN01-088.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 <0HY6004KDFADYO@tsbpo1.po.toshiba.co.jp>; Mon,
 24 May 2004 02:01:26 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BRwLa-0007ne-00; Sun, 23 May 2004 10:01:14 -0700
Date: Sun, 23 May 2004 10:01:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <40AED7E0.8070905@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: James Carlson <james.d.carlson@sun.com>,
        Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
        Thomas Narten <narten@us.ibm.com>
Message-id: <20040523170114.GD29015@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Jari Arkko <jari.arkko@piuha.net>,
 James Carlson <james.d.carlson@sun.com>,
 Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
 Thomas Narten <narten@us.ibm.com>
User-Agent: Mutt/1.5.6i
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
 <16558.30597.335081.536774@gargle.gargle.HOWL> <40AED7E0.8070905@piuha.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Sat, May 22, 2004 at 07:32:32AM +0300, Jari Arkko wrote:
> 
> I agree with James' comments, but I would add that there's
> always some overhead and roundtrips in the mechanisms used to
> carry EAP and subsequent per-packet cryptographic protection.
> Even PANA has it, although its certainly much better than with
> PPP. Also, the original text seemed to be saying that with PPP
> you are forced into a point-to-point model. That's true, but
> isn't the same also true of PANA? I mean you will establish
> a shared key between the client and the agent (or the EP). To
> me this looks like a point-to-point model and I'm not sure you
> can directly talk to the other nodes on the link. But James'
> text avoids these problems, so if you'll just that you're fine.

ARP as well as other direct communications among the nodes on the same
link works without passing through EP when PANA runs over a
multi-access link (this could be true even when EP is co-located with
access point, if the link-layer defines some sort of "side-channel").
In that sence PANA does not force a point-to-point model in
multi-access network unlike PPPoE.  However, the real issue might be
how to secure those direct communications and bootstrap the necessary
security associations for them when lower-layer is not secured, which
is out of the scope of the current PANA framework.

Yoshihiro Ohba

> 
> --Jari
> 
> _______________________________________________
> 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  Sun May 23 13:21:20 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25888
	for <pana-archive@odin.ietf.org>; Sun, 23 May 2004 13:21:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwZV-0004xV-0y
	for pana-archive@odin.ietf.org; Sun, 23 May 2004 13:15:38 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4NHFa24019057
	for pana-archive@odin.ietf.org; Sun, 23 May 2004 13:15:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwYV-0004ly-Hw
	for pana-web-archive@optimus.ietf.org; Sun, 23 May 2004 13:14:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25707
	for <pana-web-archive@ietf.org>; Sun, 23 May 2004 13:14:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRwYT-0000Yw-Dq
	for pana-web-archive@ietf.org; Sun, 23 May 2004 13:14:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRwXV-0000Cg-00
	for pana-web-archive@ietf.org; Sun, 23 May 2004 13:13:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRwVb-0007Z3-00
	for pana-web-archive@ietf.org; Sun, 23 May 2004 13:11:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwRB-00033E-Gi; Sun, 23 May 2004 13:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRwNq-0002WK-T2
	for pana@optimus.ietf.org; Sun, 23 May 2004 13:03:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25112
	for <pana@ietf.org>; Sun, 23 May 2004 13:03:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRwNp-0005Nr-2m
	for pana@ietf.org; Sun, 23 May 2004 13:03:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRwMo-000549-00
	for pana@ietf.org; Sun, 23 May 2004 13:02:31 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRwLq-0004nE-00
	for pana@ietf.org; Sun, 23 May 2004 13:01:30 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4NH1SgH029650;
	Mon, 24 May 2004 02:01:28 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4NH1S1r024786;
	Mon, 24 May 2004 02:01:28 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA24783 ; Mon, 24 May 2004 02:01:28 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA14060; Mon, 24 May 2004 02:01:27 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA24107; Mon, 24 May 2004 02:01:27 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4NH1QCR018121;
	Mon, 24 May 2004 02:01:26 +0900 (JST)
Received: from steelhead (iVPN01-088.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 <0HY6004KDFADYO@tsbpo1.po.toshiba.co.jp>; Mon,
 24 May 2004 02:01:26 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BRwLa-0007ne-00; Sun, 23 May 2004 10:01:14 -0700
Date: Sun, 23 May 2004 10:01:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <40AED7E0.8070905@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: James Carlson <james.d.carlson@sun.com>,
        Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
        Thomas Narten <narten@us.ibm.com>
Message-id: <20040523170114.GD29015@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Jari Arkko <jari.arkko@piuha.net>,
 James Carlson <james.d.carlson@sun.com>,
 Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org,
 Thomas Narten <narten@us.ibm.com>
User-Agent: Mutt/1.5.6i
References: <005d01c43f74$d1c71d20$c64ca143@sisa.samsung.com>
 <16558.30597.335081.536774@gargle.gargle.HOWL> <40AED7E0.8070905@piuha.net>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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.1 required=5.0 tests=AWL autolearn=no version=2.60

On Sat, May 22, 2004 at 07:32:32AM +0300, Jari Arkko wrote:
> 
> I agree with James' comments, but I would add that there's
> always some overhead and roundtrips in the mechanisms used to
> carry EAP and subsequent per-packet cryptographic protection.
> Even PANA has it, although its certainly much better than with
> PPP. Also, the original text seemed to be saying that with PPP
> you are forced into a point-to-point model. That's true, but
> isn't the same also true of PANA? I mean you will establish
> a shared key between the client and the agent (or the EP). To
> me this looks like a point-to-point model and I'm not sure you
> can directly talk to the other nodes on the link. But James'
> text avoids these problems, so if you'll just that you're fine.

ARP as well as other direct communications among the nodes on the same
link works without passing through EP when PANA runs over a
multi-access link (this could be true even when EP is co-located with
access point, if the link-layer defines some sort of "side-channel").
In that sence PANA does not force a point-to-point model in
multi-access network unlike PPPoE.  However, the real issue might be
how to secure those direct communications and bootstrap the necessary
security associations for them when lower-layer is not secured, which
is out of the scope of the current PANA framework.

Yoshihiro Ohba

> 
> --Jari
> 
> _______________________________________________
> 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 May 23 19:14:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13691
	for <pana-archive@lists.ietf.org>; Sun, 23 May 2004 19:14:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS28N-0005a0-O8; Sun, 23 May 2004 19:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS27F-0005O8-WA
	for pana@optimus.ietf.org; Sun, 23 May 2004 19:10:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13179
	for <pana@ietf.org>; Sun, 23 May 2004 19:10:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS27C-0000M7-KE
	for pana@ietf.org; Sun, 23 May 2004 19:10:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS26B-0007ik-00
	for pana@ietf.org; Sun, 23 May 2004 19:09:44 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS24d-0007Gm-00
	for pana@ietf.org; Sun, 23 May 2004 19:08:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4NN7tgH008911;
	Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4NN7tf8018071;
	Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id JAA18070 ; Mon, 24 May 2004 08:07:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA29084; Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA18249; Mon, 24 May 2004 08:07:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4NN7rCR024149;
	Mon, 24 May 2004 08:07:53 +0900 (JST)
Received: from steelhead (iVPN01-033.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 <0HY600D6QW94JW@tsbpo1.po.toshiba.co.jp>; Mon,
 24 May 2004 08:07:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BS23K-0000K7-00; Sun, 23 May 2004 16:06:46 -0700
Date: Sun, 23 May 2004 16:06:46 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <006a01c43f7f$cea96160$c64ca143@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'James Carlson'" <james.d.carlson@sun.com>, pana@ietf.org,
        "'Thomas Narten'" <narten@us.ibm.com>
Message-id: <20040523230646.GA852@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'James Carlson' <james.d.carlson@sun.com>, pana@ietf.org,
 'Thomas Narten' <narten@us.ibm.com>
User-Agent: Mutt/1.5.6i
References: <16558.30597.335081.536774@gargle.gargle.HOWL>
 <006a01c43f7f$cea96160$c64ca143@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL 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 Fri, May 21, 2004 at 03:05:59PM -0700, Alper Yegin wrote:
> 
> Aside from the IEEE 802 and PPPoE context, there is also PPP over ATM,
> and PPP over cdma2000 networks. 
> 
> Btw, even in IEEE 802-based DSL networks, using 802.1X would have issues
> if it has to go through bridges (e.g., CPE modem, DSLAM).

Just to be fair, there is ongoing work, i.e., 802.1AE (MACsec) and
802.1AF (KeySec), in IEEE 802.1 Working Group to develop an
architecture and protocols in order to provide link-layer security
that work across IEEE 802 bridges (i.e., MACsec).  However,
considering maturity level of the work, I think PANA has more reality
in DSL environment (or PANA may be used even for bootstrapping MACsec
and KeySec in a future.)

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  Sun May 23 19:23:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13983
	for <pana-archive@odin.ietf.org>; Sun, 23 May 2004 19:23:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS2Ia-00079D-Id
	for pana-archive@odin.ietf.org; Sun, 23 May 2004 19:22:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4NNMWd0027447
	for pana-archive@odin.ietf.org; Sun, 23 May 2004 19:22:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS2C7-0006ES-GO
	for pana-web-archive@optimus.ietf.org; Sun, 23 May 2004 19:15:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13765
	for <pana-web-archive@ietf.org>; Sun, 23 May 2004 19:15:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS2C5-0001pS-KV
	for pana-web-archive@ietf.org; Sun, 23 May 2004 19:15:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS2B8-0001YX-00
	for pana-web-archive@ietf.org; Sun, 23 May 2004 19:14:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS2AF-0001IE-00
	for pana-web-archive@ietf.org; Sun, 23 May 2004 19:13:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS28N-0005a0-O8; Sun, 23 May 2004 19:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS27F-0005O8-WA
	for pana@optimus.ietf.org; Sun, 23 May 2004 19:10:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13179
	for <pana@ietf.org>; Sun, 23 May 2004 19:10:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS27C-0000M7-KE
	for pana@ietf.org; Sun, 23 May 2004 19:10:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS26B-0007ik-00
	for pana@ietf.org; Sun, 23 May 2004 19:09:44 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS24d-0007Gm-00
	for pana@ietf.org; Sun, 23 May 2004 19:08:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i4NN7tgH008911;
	Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id i4NN7tf8018071;
	Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id JAA18070 ; Mon, 24 May 2004 08:07:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA29084; Mon, 24 May 2004 08:07:55 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA18249; Mon, 24 May 2004 08:07:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i4NN7rCR024149;
	Mon, 24 May 2004 08:07:53 +0900 (JST)
Received: from steelhead (iVPN01-033.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 <0HY600D6QW94JW@tsbpo1.po.toshiba.co.jp>; Mon,
 24 May 2004 08:07:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1BS23K-0000K7-00; Sun, 23 May 2004 16:06:46 -0700
Date: Sun, 23 May 2004 16:06:46 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] FW: AD Review comments on
 draft-ietf-pana-usage-scenarios-06.txt
In-reply-to: <006a01c43f7f$cea96160$c64ca143@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Cc: "'James Carlson'" <james.d.carlson@sun.com>, pana@ietf.org,
        "'Thomas Narten'" <narten@us.ibm.com>
Message-id: <20040523230646.GA852@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
 'James Carlson' <james.d.carlson@sun.com>, pana@ietf.org,
 'Thomas Narten' <narten@us.ibm.com>
User-Agent: Mutt/1.5.6i
References: <16558.30597.335081.536774@gargle.gargle.HOWL>
 <006a01c43f7f$cea96160$c64ca143@sisa.samsung.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

On Fri, May 21, 2004 at 03:05:59PM -0700, Alper Yegin wrote:
> 
> Aside from the IEEE 802 and PPPoE context, there is also PPP over ATM,
> and PPP over cdma2000 networks. 
> 
> Btw, even in IEEE 802-based DSL networks, using 802.1X would have issues
> if it has to go through bridges (e.g., CPE modem, DSLAM).

Just to be fair, there is ongoing work, i.e., 802.1AE (MACsec) and
802.1AF (KeySec), in IEEE 802.1 Working Group to develop an
architecture and protocols in order to provide link-layer security
that work across IEEE 802 bridges (i.e., MACsec).  However,
considering maturity level of the work, I think PANA has more reality
in DSL environment (or PANA may be used even for bootstrapping MACsec
and KeySec in a future.)

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 May 24 12:53:45 2004
Received: from optimus.ietf.org ([132.151.1.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18879
	for <pana-archive@lists.ietf.org>; Mon, 24 May 2004 12:53:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSIRh-0007k2-Gr; Mon, 24 May 2004 12:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSIHZ-0005bd-1L
	for pana@optimus.ietf.org; Mon, 24 May 2004 12:26:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17959
	for <pana@ietf.org>; Mon, 24 May 2004 12:26:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSIHX-0004Vw-HP
	for pana@ietf.org; Mon, 24 May 2004 12:26:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSIGY-0004Ql-00
	for pana@ietf.org; Mon, 24 May 2004 12:25:31 -0400
Received: from e5.ny.us.ibm.com ([32.97.182.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSIGI-0004M1-00
	for pana@ietf.org; Mon, 24 May 2004 12:25:14 -0400
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i4OGOhYd103928;
	Mon, 24 May 2004 12:24:43 -0400
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i4OGPO8d115618;
	Mon, 24 May 2004 12:25:24 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i4OGOkdP019541;
	Mon, 24 May 2004 12:24:46 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id i4OGOdJ9019537;
	Mon, 24 May 2004 12:24:40 -0400
Message-Id: <200405241624.i4OGOdJ9019537@rotala.raleigh.ibm.com>
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
cc: "Alper Yegin" <alper.yegin@samsung.com>, pana@ietf.org
Subject: Re: [Pana] FW: AD review comments on draft-ietf-pana-threats-eval-04.txt 
In-Reply-To: Message from mohanp@sbcglobal.net
   of "Fri, 21 May 2004 17:00:00 PDT." <027801c43f8f$ba0799b0$861167c0@adithya> 
Date: Mon, 24 May 2004 12:24:39 -0400
From: Thomas Narten <narten@us.ibm.com>
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=AWL 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>

"Mohan Parthasarathy" <mohanp@sbcglobal.net> writes:

>  My responses for the ones that has questions or clarifications below :

> > 
> > >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> > 
> > >    shared links, it is sufficient to provide access control
> > information  
> > >    like IP address, MAC address, etc., to EP, which in turn can
> > prevent  
> > >    unauthorized users from gaining access to the network by policing
> > the  
> > >    packets for matching addresses. In the case of shared links, this  
> > >    information is not sufficient to prevent service theft. PANA MUST
> > be  
> > >    able to bootstrap a shared secret between the PaC and PAA which can
> > 
> > >    be further used to setup a security association (e.g., IPsec)
> > between  
> > >    PaC and EP to prevent service theft on shared links.   
> > 
> > Seems wrong. Even in unshared links, if the authorized client
> > disconnects, and an intruder gets on the link, it can continue using
> > the DIs.
> >

> When an authorized client disconnects, the filters at the
> enforcement point should be reset appropriately so that any one
> using the same DI is not allowed access.  Are you saying that the
> client was disconnected without the access network (EP/PAA) knowing
> ? Could you clarify ?

Yes. You seem to assume that a disconnection is detectable in a secure
manner. I'm not sure that is always the case. 

> > >    In environments where the link is shared, this threat is present as
> > 
> > >    any node can pretend to be a PAA. Even if the nodes are
> > authenticated  
> > >    at layer 2, this threat is present. It is difficult to protect the
> > 
> > >    discovery process, as there is no a priori trust relationship
> > between  
> > >    PAA and PaC. It might be possible for the EP to filter out the  
> > >    packets coming from PaC that resembles PAA packets and hence this  
> > >    threat can be prevented in such environments.  

> > I don't follow. on a shared LAN, its not clear traffic has to go
> > through the EP. Are there some assumptions going on here?
> >

> EP is the policy enforcement point. All data has to go through
> it. In 802.11, it could be the AP. In regular LAN, it could be the
> switch or the router. Perhaps, it is not explicitly stated. From the
> requirements document,

> Enforcement Point (EP) 
>     
>         A node on the access network where per-packet enforcement  
>         policies (i.e., filters) are applied on the inbound  
>         and outbound traffic of client devices. Information such as DI  
>         and (optionally) cryptographic keys are provided by PAA per  
>         client for constructing filters on the EP. 

> Do you think we need explicit clarification that EP sees all packets
>  or some such thing ?

Yes. Also, not all networks can be assumed to have this property
(e.g., ad hoc mode). That is, one may not be able to protect the
shared access link. So I don't really think the document can just
assume this is the case and that having an EP solves all
problems. That wouldn't be completely accurate.


> > >    Requirement 1  
> > >      
> > >    PANA MUST not assume that the discovery process is protected.
> > Since,  
> > >    it is difficult to protect the discovery process, the security-  
> > >    critical information exchanged during the discovery process SHOULD
> > be  
> > >    limited.  
> > 
> > More like discovery should be treated as a hint, and reverified at a
> > higher layer before accepting as valid. Is the actual requirement that
> > the PAA  must authenticate itself to the client, to prevent spoofing
> > during the discovery process?
> >

> No. It tries to say that the discovery is just a hint and don't
> assume that everything is true. You can't do much about it anyway
> because you don't have a trust relationship with the node (PAA) you
> are talking to.  So, the PANA protocol MUST not assume that the
> channel is protected during discovery. Hence, PAA should not include
> anything that is sensitive as the PaC has no way of believing
> it. The other way is to reverify the contents once you are
> successfully authenticated so that you know whether you are fooled
> or not.  If you are fooled, you have to start the process again and
> this go on forever if the malicious node can spoof the
> information. If you never include it in the discovery and include
> only when it is safe i.e., after successful authentication protected
> by MAC, it would be better.  On unshared links, you can trust the
> information coming from the other end and hence you may include
> sensitive information. But, i am not sure whether it is worth it.

I think you need to be more clear about what is meant by "sensitive"
information. Sensitive in what sense? That it be provided to a client
that shouldn't get it? That a PaC might be lead astray in a bad way if
it is spoofed?  And what are the dangers if it is misused or
something? I.e., you need to explain what information might be
considered sensitive and why.

> > >        o All the PaCs may be authenticated to the access network at  
> > >           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
> > >           association with layer 2 authentication agent (e.g., 802.11
> > 
> > >           [IEEE-802.11] Access point), but still do not trust each  
> > >           other.  
> > 
> > not sure I follow. In what  way do they not trust each other? What are
> > the implications, and what does PANA have to do with this?
> > 
> To clarify, it says that the PaC's don't trust each other as in a trusted environment
> like the office. This means it is a hostile environment to start with. Any node can
> act like PAA, any node can spoof packets like you, any node can eavesdrop on you etc.
> On such links, PANA should be designed such a way that only the "good" nodes are
> authenticated and PaC's authenticate only to the "good" PAA. 

It would be good to expand on this in the document just a bit.

> > Nits:
> > 
> > title needs to expand PANA
> > 
> > >    T6.1.1: A malicious node can pretend to be a PAA by sending a
> > spoofed  
> > >    advertisement.  
> > 
> > subsubsection headings seem off (all have T in front, and are indented
> > like normal text)
> > 
> I was merely meant it as a way to number it. I can try and indent the following lines
> if that would make it look better.

It's probably best to use consistent number/indentation.

Thomas

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


From pana-bounces@ietf.org  Mon May 24 16:49:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27552
	for <pana-archive@lists.ietf.org>; Mon, 24 May 2004 16:49:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSMNI-0001ty-8U; Mon, 24 May 2004 16:48:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSMNH-0001to-2t
	for pana@megatron.ietf.org; Mon, 24 May 2004 16:48:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27434
	for <pana@ietf.org>; Mon, 24 May 2004 16:48:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSMNF-0004Xv-PW
	for pana@ietf.org; Mon, 24 May 2004 16:48:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSM1K-00019A-00
	for pana@ietf.org; Mon, 24 May 2004 16:26:05 -0400
Received: from smtp809.mail.sc5.yahoo.com ([66.163.168.188])
	by ietf-mx with smtp (Exim 4.12) id 1BSJCZ-0006pj-00
	for pana@ietf.org; Mon, 24 May 2004 13:25:27 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.56.37 with
	login)
	by smtp809.mail.sc5.yahoo.com with SMTP; 24 May 2004 17:22:03 -0000
Message-ID: <006d01c441b3$a308f080$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Thomas Narten" <narten@us.ibm.com>
References: <200405241624.i4OGOdJ9019537@rotala.raleigh.ibm.com>
Subject: Re: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt 
Date: Mon, 24 May 2004 10:22:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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
Cc: Alper Yegin <alper.yegin@samsung.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
Content-Transfer-Encoding: 7bit

 > > > 
> > > >    PANA MUST be able to prevent service theft. In some cases e.g. non-
> > > 
> > > >    shared links, it is sufficient to provide access control
> > > information  
> > > >    like IP address, MAC address, etc., to EP, which in turn can
> > > prevent  
> > > >    unauthorized users from gaining access to the network by policing
> > > the  
> > > >    packets for matching addresses. In the case of shared links, this  
> > > >    information is not sufficient to prevent service theft. PANA MUST
> > > be  
> > > >    able to bootstrap a shared secret between the PaC and PAA which can
> > > 
> > > >    be further used to setup a security association (e.g., IPsec)
> > > between  
> > > >    PaC and EP to prevent service theft on shared links.   
> > > 
> > > Seems wrong. Even in unshared links, if the authorized client
> > > disconnects, and an intruder gets on the link, it can continue using
> > > the DIs.
> > >
> 
> > When an authorized client disconnects, the filters at the
> > enforcement point should be reset appropriately so that any one
> > using the same DI is not allowed access.  Are you saying that the
> > client was disconnected without the access network (EP/PAA) knowing
> > ? Could you clarify ?
> 
> Yes. You seem to assume that a disconnection is detectable in a secure
> manner. I'm not sure that is always the case. 
> 
I am not sure i understood the last sentence. On unshared links, as long as
the disconnect is seen *always*, secure or insecure, the filters will be cleared
so that no nodes can access the network using the same DI. (If it is insecure,
the node that is still connected cannot access it anymore, but this is a different
threat that is later discussed in the document). So, per-packet protection is required
on unshared links only if  the disconnect may not be heard by PAA/EP at all. Is there
a real world scenario where this is possible ?

> > > >    In environments where the link is shared, this threat is present as
> > > 
> > > >    any node can pretend to be a PAA. Even if the nodes are
> > > authenticated  
> > > >    at layer 2, this threat is present. It is difficult to protect the
> > > 
> > > >    discovery process, as there is no a priori trust relationship
> > > between  
> > > >    PAA and PaC. It might be possible for the EP to filter out the  
> > > >    packets coming from PaC that resembles PAA packets and hence this  
> > > >    threat can be prevented in such environments.  
> 
> > > I don't follow. on a shared LAN, its not clear traffic has to go
> > > through the EP. Are there some assumptions going on here?
> > >
> 
> > EP is the policy enforcement point. All data has to go through
> > it. In 802.11, it could be the AP. In regular LAN, it could be the
> > switch or the router. Perhaps, it is not explicitly stated. From the
> > requirements document,
> 
> > Enforcement Point (EP) 
> >     
> >         A node on the access network where per-packet enforcement  
> >         policies (i.e., filters) are applied on the inbound  
> >         and outbound traffic of client devices. Information such as DI  
> >         and (optionally) cryptographic keys are provided by PAA per  
> >         client for constructing filters on the EP. 
> 
> > Do you think we need explicit clarification that EP sees all packets
> >  or some such thing ?
> 
> Yes. Also, not all networks can be assumed to have this property
> (e.g., ad hoc mode). That is, one may not be able to protect the
> shared access link. So I don't really think the document can just
> assume this is the case and that having an EP solves all
> problems. That wouldn't be completely accurate.
> 
But this document may not be the right place. PANA assumes that EP
sees all the packets and anything else e.g. ad hoc mode is outside the scope
of PANA. I hope someone else can confirm this.

> 
> > > >    Requirement 1  
> > > >      
> > > >    PANA MUST not assume that the discovery process is protected.
> > > Since,  
> > > >    it is difficult to protect the discovery process, the security-  
> > > >    critical information exchanged during the discovery process SHOULD
> > > be  
> > > >    limited.  
> > > 
> > > More like discovery should be treated as a hint, and reverified at a
> > > higher layer before accepting as valid. Is the actual requirement that
> > > the PAA  must authenticate itself to the client, to prevent spoofing
> > > during the discovery process?
> > >
> 
> > No. It tries to say that the discovery is just a hint and don't
> > assume that everything is true. You can't do much about it anyway
> > because you don't have a trust relationship with the node (PAA) you
> > are talking to.  So, the PANA protocol MUST not assume that the
> > channel is protected during discovery. Hence, PAA should not include
> > anything that is sensitive as the PaC has no way of believing
> > it. The other way is to reverify the contents once you are
> > successfully authenticated so that you know whether you are fooled
> > or not.  If you are fooled, you have to start the process again and
> > this go on forever if the malicious node can spoof the
> > information. If you never include it in the discovery and include
> > only when it is safe i.e., after successful authentication protected
> > by MAC, it would be better.  On unshared links, you can trust the
> > information coming from the other end and hence you may include
> > sensitive information. But, i am not sure whether it is worth it.
> 
> I think you need to be more clear about what is meant by "sensitive"
> information. Sensitive in what sense? That it be provided to a client
> that shouldn't get it? That a PaC might be lead astray in a bad way if
> it is spoofed?  And what are the dangers if it is misused or
> something? I.e., you need to explain what information might be
> considered sensitive and why.
> 
There was one example given in the section about how if you include "authentication
algorithms supported", there might be a possibility of downgrade attack where the
client can end up negotiating a weak one. Isn't that sufficient ? The draft does not
use the word sensitive. It uses "security-related" e.g. authentication methods.


> > > >        o All the PaCs may be authenticated to the access network at  
> > > >           layer 2 (e.g., 3GPP2 CDMA network) and share a security  
> > > >           association with layer 2 authentication agent (e.g., 802.11
> > > 
> > > >           [IEEE-802.11] Access point), but still do not trust each  
> > > >           other.  
> > > 
> > > not sure I follow. In what  way do they not trust each other? What are
> > > the implications, and what does PANA have to do with this?
> > > 
> > To clarify, it says that the PaC's don't trust each other as in a trusted environment
> > like the office. This means it is a hostile environment to start with. Any node can
> > act like PAA, any node can spoof packets like you, any node can eavesdrop on you etc.
> > On such links, PANA should be designed such a way that only the "good" nodes are
> > authenticated and PaC's authenticate only to the "good" PAA. 
> 
> It would be good to expand on this in the document just a bit.
> 
Ok.

> > > Nits:
> > > 
> > > title needs to expand PANA
> > > 
> > > >    T6.1.1: A malicious node can pretend to be a PAA by sending a
> > > spoofed  
> > > >    advertisement.  
> > > 
> > > subsubsection headings seem off (all have T in front, and are indented
> > > like normal text)
> > > 
> > I was merely meant it as a way to number it. I can try and indent the following lines
> > if that would make it look better.
> 
> It's probably best to use consistent number/indentation.
> 
Ok, i will keep the text indented.

thanks
mohan

> Thomas

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


From pana-bounces@ietf.org  Mon May 24 16:50:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27950
	for <pana-archive@lists.ietf.org>; Mon, 24 May 2004 16:50:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSMOs-0002Ac-Ta; Mon, 24 May 2004 16:50:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSMOr-0002AR-Mw
	for pana@megatron.ietf.org; Mon, 24 May 2004 16:50:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27836
	for <pana@ietf.org>; Mon, 24 May 2004 16:50:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSMOq-0004kZ-IA
	for pana@ietf.org; Mon, 24 May 2004 16:50:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSM3Z-0001Ud-00
	for pana@ietf.org; Mon, 24 May 2004 16:28:24 -0400
Received: from e1.ny.us.ibm.com ([32.97.182.101])
	by ietf-mx with esmtp (Exim 4.12) id 1BSJUD-0006ux-00
	for pana@ietf.org; Mon, 24 May 2004 13:43:41 -0400
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com
	[9.56.224.206])
	by e1.ny.us.ibm.com (8.12.10/NS PXFA) with ESMTP id i4OHhBll422286;
	Mon, 24 May 2004 13:43:11 -0400
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	i4OHhhpP062770; Mon, 24 May 2004 13:43:43 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i4OHh9dP019830; 
	Mon, 24 May 2004 13:43:09 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id
	i4OHh7QR019826; Mon, 24 May 2004 13:43:07 -0400
Message-Id: <200405241743.i4OHh7QR019826@rotala.raleigh.ibm.com>
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
Subject: Re: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt 
In-Reply-To: Message from mohanp@sbcglobal.net of "Mon,
	24 May 2004 10:22:05 PDT." <006d01c441b3$a308f080$6401a8c0@adithya> 
Date: Mon, 24 May 2004 13:43:07 -0400
From: Thomas Narten <narten@us.ibm.com>
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=AWL autolearn=no version=2.60
Cc: Alper Yegin <alper.yegin@samsung.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

> > Yes. You seem to assume that a disconnection is detectable in a secure
> > manner. I'm not sure that is always the case. 
> > 

> I am not sure i understood the last sentence. On unshared links, as
> long as the disconnect is seen *always*, secure or insecure, the
> filters will be cleared so that no nodes can access the network
> using the same DI.

Can one assume that such disconnections are _always_ seen? Reliably?
There are cases where one can unplug a mode from one machine to
another and the modem doesn't detect this and drop carrier. In such a
case, the EP wouldn't necessarily detect the switch.

> (If it is insecure, the node that is still connected cannot access
> it anymore, but this is a different threat that is later discussed
> in the document). So, per-packet protection is required on unshared
> links only if the disconnect may not be heard by PAA/EP at all. Is
> there a real world scenario where this is possible ?

This document seems to assume that all of a client's traffic _always_
can be forced through an EP, and thus, if there are filters on the EP,
theft of service and other things can be prevented. I challenge that
assumption. There are shared access links that do not require all
traffic to go through the EP. so service on the local access link can
be "stolen". 

I don't think this changes anything that PANA does. It's more about
being precise and correct in the document in terms of making claims.

> > Yes. Also, not all networks can be assumed to have this property
> > (e.g., ad hoc mode). That is, one may not be able to protect the
> > shared access link. So I don't really think the document can just
> > assume this is the case and that having an EP solves all
> > problems. That wouldn't be completely accurate.
> > 
> But this document may not be the right place. PANA assumes that EP
> sees all the packets and anything else e.g. ad hoc mode is outside the scope
> of PANA. I hope someone else can confirm this.

I would assert this is an improper assumption on PANA's part in terms
of evaluating risks and making claims about what PANA can protect
against. 

> > I think you need to be more clear about what is meant by "sensitive"
> > information. Sensitive in what sense? That it be provided to a client
> > that shouldn't get it? That a PaC might be lead astray in a bad way if
> > it is spoofed?  And what are the dangers if it is misused or
> > something? I.e., you need to explain what information might be
> > considered sensitive and why.

> There was one example given in the section about how if you include
> "authentication algorithms supported", there might be a possibility
> of downgrade attack where the client can end up negotiating a weak
> one. Isn't that sufficient ? The draft does not use the word
> sensitive. It uses "security-related" e.g. authentication methods.

Going back and rereading the section (and your responses), I am still
unclear on what the stated requirement really should be. Currently, it
says:

>    Requirement 1  
>      
>    PANA MUST not assume that the discovery process is protected. Since,  
>    it is difficult to protect the discovery process, the security-  
>    critical information exchanged during the discovery process SHOULD be  
>    limited.  

I agree with the first part. But the second part (which is a SHOULD)
I'm still unclear about. A fairly general statement is being made
which is hard to understand the implications of. What
"security-critical" information should not be included? and if it is
not, is that a problem for the discovery process?

Thomas

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


From pana-bounces@ietf.org  Mon May 24 17:37:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05315
	for <pana-archive@lists.ietf.org>; Mon, 24 May 2004 17:37:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSN8Q-0008RA-LT; Mon, 24 May 2004 17:37:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSN8O-0008Qn-Hk
	for pana@megatron.ietf.org; Mon, 24 May 2004 17:37:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05251
	for <pana@ietf.org>; Mon, 24 May 2004 17:37:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSN8N-0003X3-7Z
	for pana@ietf.org; Mon, 24 May 2004 17:37:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSMsJ-0000WG-00
	for pana@ietf.org; Mon, 24 May 2004 17:20:52 -0400
Received: from smtp810.mail.sc5.yahoo.com ([66.163.170.80])
	by ietf-mx with smtp (Exim 4.12) id 1BSMYV-0005l0-00
	for pana@ietf.org; Mon, 24 May 2004 17:00:19 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.56.37 with
	login)
	by smtp810.mail.sc5.yahoo.com with SMTP; 24 May 2004 20:48:40 -0000
Message-ID: <011901c441d0$7ecb1d20$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Thomas Narten" <narten@us.ibm.com>
References: <200405241743.i4OHh7QR019826@rotala.raleigh.ibm.com>
Subject: Re: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt 
Date: Mon, 24 May 2004 13:48:40 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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
Cc: Alper Yegin <alper.yegin@samsung.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
Content-Transfer-Encoding: 7bit


 
> > > Yes. You seem to assume that a disconnection is detectable in a secure
> > > manner. I'm not sure that is always the case. 
> > > 
> 
> > I am not sure i understood the last sentence. On unshared links, as
> > long as the disconnect is seen *always*, secure or insecure, the
> > filters will be cleared so that no nodes can access the network
> > using the same DI.
> 
> Can one assume that such disconnections are _always_ seen? Reliably?
> There are cases where one can unplug a mode from one machine to
> another and the modem doesn't detect this and drop carrier. In such a
> case, the EP wouldn't necessarily detect the switch.
> 
Oops! This is T6.3.3 in section 6.3. I have not read this draft
in a long time :-) Section 6.3 discussed about disconnect notification.
Here the attacker is using that to gain access to the unshared link.

> > (If it is insecure, the node that is still connected cannot access
> > it anymore, but this is a different threat that is later discussed
> > in the document). So, per-packet protection is required on unshared
> > links only if the disconnect may not be heard by PAA/EP at all. Is
> > there a real world scenario where this is possible ?
> 
> This document seems to assume that all of a client's traffic _always_
> can be forced through an EP, and thus, if there are filters on the EP,
> theft of service and other things can be prevented. I challenge that
> assumption. There are shared access links that do not require all
> traffic to go through the EP. so service on the local access link can
> be "stolen". 
> 
> I don't think this changes anything that PANA does. It's more about
> being precise and correct in the document in terms of making claims.
> 
>From here, i understand that stating the assumptions would make
it clearer e.g., This document does not discuss about the threats
that arise from direct communication between PaCs. etc. But below,
i am seeing something different..
 
> > > Yes. Also, not all networks can be assumed to have this property
> > > (e.g., ad hoc mode). That is, one may not be able to protect the
> > > shared access link. So I don't really think the document can just
> > > assume this is the case and that having an EP solves all
> > > problems. That wouldn't be completely accurate.
> > > 
> > But this document may not be the right place. PANA assumes that EP
> > sees all the packets and anything else e.g. ad hoc mode is outside the scope
> > of PANA. I hope someone else can confirm this.
> 
> I would assert this is an improper assumption on PANA's part in terms
> of evaluating risks and making claims about what PANA can protect
> against. 
> 
Here, i read it differently. You authenticate to the network before accessing
the network. The service theft is about how to provide access only to
authorized clients ? If the deployment allows for direct communication between
nodes where the network does not have a chance to police the packets,
how can the threat be prevented ? Why should PANA even care about this condition?
It just needs to provide a mechanism so that if used appropriately, the threat
can be prevented. Here, we are only saying that such a bootstrap mechanism
is provided. Depending on how you enforce it you may allow all traffic to
go through the EP e.g. infrastructure mode in 802.11 or police only the traffic
for which you will be billed by the access network etc. So, i am still not understanding
this issue.

> > > I think you need to be more clear about what is meant by "sensitive"
> > > information. Sensitive in what sense? That it be provided to a client
> > > that shouldn't get it? That a PaC might be lead astray in a bad way if
> > > it is spoofed?  And what are the dangers if it is misused or
> > > something? I.e., you need to explain what information might be
> > > considered sensitive and why.
> 
> > There was one example given in the section about how if you include
> > "authentication algorithms supported", there might be a possibility
> > of downgrade attack where the client can end up negotiating a weak
> > one. Isn't that sufficient ? The draft does not use the word
> > sensitive. It uses "security-related" e.g. authentication methods.
> 
> Going back and rereading the section (and your responses), I am still
> unclear on what the stated requirement really should be. Currently, it
> says:
> 
> >    Requirement 1  
> >      
> >    PANA MUST not assume that the discovery process is protected. Since,  
> >    it is difficult to protect the discovery process, the security-  
> >    critical information exchanged during the discovery process SHOULD be  
> >    limited.  
> 
> I agree with the first part. But the second part (which is a SHOULD)
> I'm still unclear about. A fairly general statement is being made
> which is hard to understand the implications of. What
> "security-critical" information should not be included? and if it is
> not, is that a problem for the discovery process?
> 
Ok, i can see your concerns.

The main concern is about downgrade attacks where the attacker can
include a different set of information in the advertisement making the client
choose the "weak" element in the set. Having recently discussed this in
the context of PANA, there are several ways this can be approached

1) Include the information only in unshared links where you know it can't be spoofed.

2) Include it in shared links too but verify later whether the information is correct. In this
    approach, it is quite possible that the attacker can always keep feeding the incorrect
    information creating a DoS attack. Also, for you to verify, you need to use an EAP method
    that derives keys so that the information can be protected using MAC.

3) Include it only when it is safe e.g. when it can be protected using MAC. But this
    approach may not be possible always i.e you may have to include at least some information
    in the beginning.

So, perhaps we should leave it to the protocol to decide how this can be done and not
have a requirement. I can add some clarification along the above lines and remove the
requirement. Would that make sense ?

thanks
mohan


> Thomas

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


From pana-bounces@ietf.org  Tue May 25 11:10:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17453
	for <pana-archive@lists.ietf.org>; Tue, 25 May 2004 11:10:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSdJL-0006La-UC; Tue, 25 May 2004 10:53:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSd2S-0003Go-4Z
	for pana@megatron.ietf.org; Tue, 25 May 2004 10:36:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15877
	for <pana@ietf.org>; Tue, 25 May 2004 10:35:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSd26-0006oH-2s
	for pana@ietf.org; Tue, 25 May 2004 10:35:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSd15-0006ms-00
	for pana@ietf.org; Tue, 25 May 2004 10:34:56 -0400
Received: from e35.co.us.ibm.com ([32.97.110.133])
	by ietf-mx with esmtp (Exim 4.12) id 1BSd0b-0006ju-00
	for pana@ietf.org; Tue, 25 May 2004 10:34:25 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com
	[9.17.195.11])
	by e35.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i4PEXnqF590410;
	Tue, 25 May 2004 10:33:49 -0400
Received: from rotala.raleigh.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	i4PEXdU5321802; Tue, 25 May 2004 08:33:39 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i4PEXgdP025343; 
	Tue, 25 May 2004 10:33:42 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id
	i4PEXdt6025339; Tue, 25 May 2004 10:33:40 -0400
Message-Id: <200405251433.i4PEXdt6025339@rotala.raleigh.ibm.com>
To: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
Subject: Re: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt 
In-Reply-To: Message from mohanp@sbcglobal.net of "Mon,
	24 May 2004 13:48:40 PDT." <011901c441d0$7ecb1d20$6401a8c0@adithya> 
Date: Tue, 25 May 2004 10:33:39 -0400
From: Thomas Narten <narten@us.ibm.com>
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
Cc: Alper Yegin <alper.yegin@samsung.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

> Here, i read it differently. You authenticate to the network before
> accessing the network.

Um, this is not the way I understand it. PANA is supposed to be used
aso in cases where one doesn't authenticate with "the network", e.g.,
at L2.

> The service theft is about how to provide access only to authorized
> clients ? If the deployment allows for direct communication between
> nodes where the network does not have a chance to police the
> packets, how can the threat be prevented ?

It can't (I think we agree on this!) But the threats document should
be honest about that. A general issue I have is that it is not
reasonable to only talk about all traffic going throught the EP and
not discussing the other threats.

> Why should PANA even care
> about this condition?  It just needs to provide a mechanism so that
> if used appropriately, the threat can be prevented. Here, we are
> only saying that such a bootstrap mechanism is provided. Depending
> on how you enforce it you may allow all traffic to go through the EP
> e.g. infrastructure mode in 802.11 or police only the traffic for
> which you will be billed by the access network etc. So, i am still
> not understanding this issue.

> Ok, i can see your concerns.

> The main concern is about downgrade attacks where the attacker can
> include a different set of information in the advertisement making
> the client choose the "weak" element in the set. Having recently
> discussed this in the context of PANA, there are several ways this
> can be approached

> 1) Include the information only in unshared links where you know it
> can't be spoofed.

> 2) Include it in shared links too but verify later whether the
> information is correct. In this approach, it is quite possible that
> the attacker can always keep feeding the incorrect information
> creating a DoS attack. Also, for you to verify, you need to use an
> EAP method that derives keys so that the information can be
> protected using MAC.

> 3) Include it only when it is safe e.g. when it can be protected
> using MAC. But this approach may not be possible always i.e you may
> have to include at least some information in the beginning.

> So, perhaps we should leave it to the protocol to decide how this
> can be done and not have a requirement. I can add some clarification
> along the above lines and remove the requirement. Would that make
> sense ?

Yes. Maybe the requirment should be that PANA needs to assume the
discovery process is unreliable and subject to vulnerabilities, and
that PANA itself needs to take approriate steps to mitigate these
concerns?

Thomas

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


From pana-bounces@ietf.org  Tue May 25 14:05:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04205
	for <pana-archive@lists.ietf.org>; Tue, 25 May 2004 14:05:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSgAP-00011G-Fc; Tue, 25 May 2004 13:56:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSftR-0004w6-8h
	for pana@megatron.ietf.org; Tue, 25 May 2004 13:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02569
	for <pana@ietf.org>; Tue, 25 May 2004 13:39:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSftP-00033Z-FV
	for pana@ietf.org; Tue, 25 May 2004 13:39:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSfsS-0002yv-00
	for pana@ietf.org; Tue, 25 May 2004 13:38:13 -0400
Received: from smtp802.mail.sc5.yahoo.com ([66.163.168.181])
	by ietf-mx with smtp (Exim 4.12) id 1BSfrw-0002uW-00
	for pana@ietf.org; Tue, 25 May 2004 13:37:40 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.57.242 with
	login)
	by smtp802.mail.sc5.yahoo.com with SMTP; 25 May 2004 17:37:39 -0000
Message-ID: <006b01c4427e$fb8311c0$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Thomas Narten" <narten@us.ibm.com>
References: <200405251433.i4PEXdt6025339@rotala.raleigh.ibm.com>
Subject: Re: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt 
Date: Tue, 25 May 2004 10:37:42 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
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
Cc: Alper Yegin <alper.yegin@samsung.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
Content-Transfer-Encoding: 7bit

 
> > Here, i read it differently. You authenticate to the network before
> > accessing the network.
> 
> Um, this is not the way I understand it. PANA is supposed to be used
> aso in cases where one doesn't authenticate with "the network", e.g.,
> at L2.
> 
I meant to say "You authenticate to the network using PANA before accessing
the network".

> > The service theft is about how to provide access only to authorized
> > clients ? If the deployment allows for direct communication between
> > nodes where the network does not have a chance to police the
> > packets, how can the threat be prevented ?
> 
> It can't (I think we agree on this!) But the threats document should
> be honest about that. 

Ok, we can clarify this in the document.

>A general issue I have is that it is not
> reasonable to only talk about all traffic going throught the EP and
> not discussing the other threats.
> 
But we are talking about threats that relate to PANA protocol itself.
Service theft is post-PANA that has some requirements on PANA itself
and that's why it has been documented. In the miscellaneous attacks sections,
it does talk about some general attacks. Could you be specific about what
else can be documented ?

> > Why should PANA even care
> > about this condition?  It just needs to provide a mechanism so that
> > if used appropriately, the threat can be prevented. Here, we are
> > only saying that such a bootstrap mechanism is provided. Depending
> > on how you enforce it you may allow all traffic to go through the EP
> > e.g. infrastructure mode in 802.11 or police only the traffic for
> > which you will be billed by the access network etc. So, i am still
> > not understanding this issue.
> 
> > Ok, i can see your concerns.
> 
> > The main concern is about downgrade attacks where the attacker can
> > include a different set of information in the advertisement making
> > the client choose the "weak" element in the set. Having recently
> > discussed this in the context of PANA, there are several ways this
> > can be approached
> 
> > 1) Include the information only in unshared links where you know it
> > can't be spoofed.
> 
> > 2) Include it in shared links too but verify later whether the
> > information is correct. In this approach, it is quite possible that
> > the attacker can always keep feeding the incorrect information
> > creating a DoS attack. Also, for you to verify, you need to use an
> > EAP method that derives keys so that the information can be
> > protected using MAC.
> 
> > 3) Include it only when it is safe e.g. when it can be protected
> > using MAC. But this approach may not be possible always i.e you may
> > have to include at least some information in the beginning.
> 
> > So, perhaps we should leave it to the protocol to decide how this
> > can be done and not have a requirement. I can add some clarification
> > along the above lines and remove the requirement. Would that make
> > sense ?
> 
> Yes. Maybe the requirment should be that PANA needs to assume the
> discovery process is unreliable and subject to vulnerabilities, and
> that PANA itself needs to take approriate steps to mitigate these
> concerns?
> 
Ok, i will add this to the requirement.

thanks
mohan

> Thomas

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


From pana-bounces@ietf.org  Fri May 28 02:08:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00257
	for <pana-archive@lists.ietf.org>; Fri, 28 May 2004 02:08:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTaT8-0006cl-9o; Fri, 28 May 2004 02:03:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTaMv-0004Dp-CY
	for pana@megatron.ietf.org; Fri, 28 May 2004 01:57:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21556
	for <pana@ietf.org>; Fri, 28 May 2004 01:57:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTaMs-00063v-Ql
	for pana@ietf.org; Fri, 28 May 2004 01:57:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTaLr-0005k0-00
	for pana@ietf.org; Fri, 28 May 2004 01:56:19 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BTaKn-00057z-00
	for pana@ietf.org; Fri, 28 May 2004 01:55:13 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0HYE00KB4TR66P@mailout2.samsung.com> for pana@ietf.org; Fri,
	28 May 2004 14:54:42 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0HYE00MELTNJKJ@mailout2.samsung.com> for pana@ietf.org;
	Fri, 28 May 2004 14:52:31 +0900 (KST)
Received: from Alperyegin ([105.253.155.2])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0HYE00I31TNGB9@mmp1.samsung.com> for
	pana@ietf.org; Fri, 28 May 2004 14:52:31 +0900 (KST)
Date: Thu, 27 May 2004 22:52:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt
To: "'Thomas Narten'" <narten@us.ibm.com>,
        "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>
Message-id: <000001c44477$f6819160$6601a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > > >    at layer 2, this threat is present. It is difficult to 
> > > > protect
> the
> > >
> > > >    discovery process, as there is no a priori trust relationship
> > > between
> > > >    PAA and PaC. It might be possible for the EP to filter out
the
> > > >    packets coming from PaC that resembles PAA packets and hence
this
> > > >    threat can be prevented in such environments.
> 
> > > I don't follow. on a shared LAN, its not clear traffic has to go 
> > > through the EP. Are there some assumptions going on here?

This text just acknowledges discovery may not be protected. By placing
the EP on a choke-point, unauthorized messages can be filtered. It is
not assuming this is always possible, hence it says "it might be
possible for the EP to filter..."

I think we can spell this out, and have some text on location of EP,
what it can and cannot do depending on its location in the topology. 

The access control of the operator depends on where the EPs can be
placed. If there are no EP between the PaCs, they can freely send
packets among themselves. 

Alper






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


From pana-bounces@ietf.org  Fri May 28 02:25:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06595
	for <pana-archive@lists.ietf.org>; Fri, 28 May 2004 02:25:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTaeC-0002TL-S6; Fri, 28 May 2004 02:15:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTaVd-0008FI-Ev
	for pana@megatron.ietf.org; Fri, 28 May 2004 02:06:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28081
	for <pana@ietf.org>; Fri, 28 May 2004 02:06:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTaVa-0001Rl-IJ
	for pana@ietf.org; Fri, 28 May 2004 02:06:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTaUa-000176-00
	for pana@ietf.org; Fri, 28 May 2004 02:05:21 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BTaTb-0000Qi-00
	for pana@ietf.org; Fri, 28 May 2004 02:04:19 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0HYE00KJ2U6AEY@mailout2.samsung.com> for pana@ietf.org; Fri,
	28 May 2004 15:03:46 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0HYE0011TU13OF@mailout2.samsung.com> for pana@ietf.org;
	Fri, 28 May 2004 15:00:39 +0900 (KST)
Received: from Alperyegin ([105.253.155.2])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0HYE00MWHU0ZEA@mmp2.samsung.com> for
	pana@ietf.org; Fri, 28 May 2004 15:00:39 +0900 (KST)
Date: Thu, 27 May 2004 23:00:34 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] FW: AD review comments on
	draft-ietf-pana-threats-eval-04.txt
In-reply-to: <027801c43f8f$ba0799b0$861167c0@adithya>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, pana@ietf.org
Message-id: <000101c44479$1949e020$6601a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: "'Thomas Narten'" <narten@us.ibm.com>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > >    PANA MUST be able to prevent service theft. In some cases e.g.
non-
> >
> > >    shared links, it is sufficient to provide access control
> > information
> > >    like IP address, MAC address, etc., to EP, which in turn can
> > prevent
> > >    unauthorized users from gaining access to the network by
policing
> > the
> > >    packets for matching addresses. In the case of shared links,
this
> > >    information is not sufficient to prevent service theft. PANA
MUST
> > be
> > >    able to bootstrap a shared secret between the PaC and PAA which
can
> >
> > >    be further used to setup a security association (e.g., IPsec)
> > between
> > >    PaC and EP to prevent service theft on shared links.
> >
> > Seems wrong. Even in unshared links, if the authorized client
> > disconnects, and an intruder gets on the link, it can continue using
> > the DIs.

To be on the safe side, I think we should also cover the case where
disconnection may not be detected. Let's not limit the cryptographic
protection case (e.g., IPsec) to only shared links. Unshared (e.g.,
point-to-point physically secured) links can also resort to using
per-packet ciphering if there is a chance that an already authorized
client is somehow replaced by an unauthenticated client.

Alper
 



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


From pana-bounces@ietf.org  Mon May 31 05:54:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09752
	for <pana-archive@lists.ietf.org>; Mon, 31 May 2004 05:54:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUjSx-00009X-VL; Mon, 31 May 2004 05:52:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUjKf-0007jZ-Ii
	for pana@megatron.ietf.org; Mon, 31 May 2004 05:43:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09402
	for <pana@ietf.org>; Mon, 31 May 2004 05:43:47 -0400 (EDT)
From: Pasi.Eronen@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUjKd-0003bV-4w
	for pana@ietf.org; Mon, 31 May 2004 05:43:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUjJb-0003HH-00
	for pana@ietf.org; Mon, 31 May 2004 05:42:43 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12) id 1BUjIW-0002tu-00
	for pana@ietf.org; Mon, 31 May 2004 05:41:36 -0400
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i4V9fbo16705
	for <pana@ietf.org>; Mon, 31 May 2004 12:41:37 +0300 (EET DST)
X-Scanned: Mon, 31 May 2004 12:41:29 +0300 Nokia Message Protector V1.3.30
	2004040916 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i4V9fTk7019675
	for <pana@ietf.org>; Mon, 31 May 2004 12:41:29 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 00NMXBPX; Mon, 31 May 2004 12:41:28 EEST
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i4V9fIH14293
	for <pana@ietf.org>; Mon, 31 May 2004 12:41:18 +0300 (EET DST)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 31 May 2004 12:41:18 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by
	esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 31 May 2004 12:41:17 +0300
x-mimeole: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 31 May 2004 12:41:17 +0300
Message-ID: <052E0C61B69C3741AFA5FE88ACC775A6122422@esebe023.ntc.nokia.com>
Thread-Topic: Some comments about PANA drafts
Thread-Index: AcRG82xzl9AC39n4RBGNCUfx05ik3g==
To: <pana@ietf.org>
X-OriginalArrivalTime: 31 May 2004 09:41:17.0996 (UTC)
	FILETIME=[6C3A16C0:01C446F3]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Some comments about PANA drafts
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


Hi,

Here are some comments about PANA drafts based on a=20
quick review. (I haven't followed the PANA mailing list=20
for  some time, so my apologies if some of these issues=20
have already been discussed here.)

Best regards,
Pasi





Comments about draft-ietf-pana-framework-00:

Section 10.2.2: First, let's say that I have some doubts about
whether anyone will actually implement this. It also seems that
there are not enough details about e.g. PANA would actually work
together with 802.11 and .11i state machines and procedures, but
maybe this isn't necessary in a "framework" document. (BTW, the
4-way handshake is started by the AP; bullet 4 in 10.2.2.2 seems
to assume otherwise.)


Comments draft-ietf-pana-pana-04:

The document would probably benefit from explaining the "big
picture" first, e.g. what PANA messages are sent in a typical
situation (something like Section 4.6), and only then specific
details such as contents of PANA SA, calculation of MAC AVP and
processing of the S-flag.

Section 4.1.5: Key derivation seems to assume that the integrity
protection algorithm needs at most 160 bit key (so if some new
algorithm later needs more, also the key derivation needs to be
updated).

Section 4.2: HMAC-SHA1 takes two parameters, not one

Section 6.3: Diameter uses SMI enterprise numbers for Vendor-Id;
does PANA use that also, or does it define its own number space?

Section 6.5.5 (Protection-Capability): Is it assumed that only a
single L2 mechanism can exist? Or that if multiple L2 mechanisms
are possible, the correct one can be determined from some L2
messages?

Section 6.5.13 (Provider-Identifier): What the client is
supposed to do with this information? (And usually the
enterprise numbers are used to identify vendors, not network
operators--but of course a network operator could get an
enterprise number as well...)

Section 7: The retransmission behavior seems quite complicated;
IMHO it would have been simpler to have one end (probably PaC)
to be responsible for all timer-based retransmissions.

Section 9: Overall, this section is quite heavy reading, and
it's not clear that someone not very familiar with PANA, EAP,
etc. can actually get a very accurate picture of the relevant
security properties of PANA. So this section would certainly
benefit from some editorial work.

Part a (discovery message exchange) should probably explain that
if including Protection-Capability and PPAC AVPs in PSR is not
recommended, why are they allowed at all (especially since it
seems the client won't actually need the information until PBR
anyway).

This section should also mention that any information in PANA
messages before PBR/PBA (such as ISP-Information) can be
spoofed, and the implications of that. (BTW, perhaps it would
have been a good idea to integrity protect all previous PANA
messages in PBR/PBA.)

It should be clarified what exactly is meant when it's said that
a network is already "secure" before PANA is run. E.g. it seems
that such networks should have reasonably reliable disconnect
indications? What about ppreventing IP address spoofing?

References: Some of the normative references should probably be
informative (e.g. EAP-TLS).


Comments about draft-ietf-pana-ipsec-03:

Section 5: What happens if there were two EAP authentications,
resulting in two AAA-Keys?

Section 8: The special rule for PANA_PORT should be included=20
in Section 8.1 and 8.2, rather than described separately.
Also, inbound SPD/SAD entries don't contain outer IP addresses.


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


