RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n?

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> Tue, 09 December 2003 20:49 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16190 for <seamoby-archive@odin.ietf.org>; Tue, 9 Dec 2003 15:49:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATon4-0000e8-GQ for seamoby-archive@odin.ietf.org; Tue, 09 Dec 2003 15:49:09 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9Kn6fx002478 for seamoby-archive@odin.ietf.org; Tue, 9 Dec 2003 15:49:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATon3-0000ds-Mw for seamoby-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 15:49:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16080 for <seamoby-web-archive@ietf.org>; Tue, 9 Dec 2003 15:48:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATon2-0000Me-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 15:49:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATon1-0000MZ-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 15:49:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATomz-0000dX-E4; Tue, 09 Dec 2003 15:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATom0-0000a3-1m for seamoby@optimus.ietf.org; Tue, 09 Dec 2003 15:48:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15945 for <seamoby@ietf.org>; Tue, 9 Dec 2003 15:47:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AToly-0000Ix-00 for seamoby@ietf.org; Tue, 09 Dec 2003 15:47:58 -0500
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1ATolx-0000Ib-00 for seamoby@ietf.org; Tue, 09 Dec 2003 15:47:58 -0500
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id hB9KluP1001710 for <seamoby@ietf.org>; Tue, 9 Dec 2003 13:47:56 -0700 (MST)
Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id hB9KlKPx021910 for <seamoby@ietf.org>; Tue, 9 Dec 2003 14:47:34 -0600
Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id <XJ5BRADJ>; Tue, 9 Dec 2003 14:47:20 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB239161@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: 'Rajeev Koodli' <rajeev@iprg.nokia.com>, Seamoby CTP Issues <ctp_issues@danforsberg.info>
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n?
Date: Tue, 09 Dec 2003 14:46:58 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-Type: text/plain
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>

Rajeev, 

I don't recall whether there was a message authentication procedure between
the pAR and nAR, if there is none, and the pAR can't verify the authorization
token, then we may open the door to DoS attacks on the pAR. So responding to 
nAR may have bad consequences...
If there is no message authentication between nAR and pAR, while you are expecting
the MN to authenticate itself to pAR (to me this is half way solution), then the 
pAR should ignore the request.

Madjid

-----Original Message-----
From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of
Rajeev Koodli
Sent: Monday, December 08, 2003 1:14 PM
To: Seamoby CTP Issues
Cc: seamoby@ietf.org
Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization
Token?


John Loughney SEAMOBY-Issues wrote:

> New submission from John Loughney <john.loughney@nokia.com>:
>
> In case nAR requests the transfer by a CTR message, the pAR must verify
> the MN's authorization token. If this token is unvalid, what do we do ?
>
> Possible solutions:
>
>  - nothing ? the pAR does not answer to nAR.
>  - pAR indicates the error to nAR:
>         * In the CTD message.
>         * In a error message which could carry error information.
>

pAR MUST respond to nAR with an appropriate error.
nAR SHOULD convey the result to the MN.

-Rajeev


>
> others ?
>
> ----------
> category: Editorial
> document: draft-ietf-seamoby-ctp-05.txt
> messages: 39
> nosy: jloughney
> priority: Should Fix
> status: No Discussion
> title: How to handle bad MN's authorization Token?
> _____________________________________________________________
> Seamoby CTP Issues <ctp_issues@danforsberg.info>
> <http://danforsberg.info:8080/draft-ietf-seamoby-ctp/issue30>
> _____________________________________________________________
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby


_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby