IETF Logo Mail Archive

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

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> Tue, 02 December 2003 23:16 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22008 for <seamoby-archive@odin.ietf.org>; Tue, 2 Dec 2003 18:16:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJkz-00087K-6D for seamoby-archive@odin.ietf.org; Tue, 02 Dec 2003 18:16:38 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2NGbAu031196 for seamoby-archive@odin.ietf.org; Tue, 2 Dec 2003 18:16:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJkz-000875-2a for seamoby-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 18:16:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21949 for <seamoby-web-archive@ietf.org>; Tue, 2 Dec 2003 18:16:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJkw-0004xL-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:16:34 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1ARJe3-0004pj-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:09:27 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1ARJRA-0008Ra-TO for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 17:56:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJR3-0006lL-US; Tue, 02 Dec 2003 17:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJQx-0006km-2V for seamoby@optimus.ietf.org; Tue, 02 Dec 2003 17:55:56 -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 RAA20199 for <seamoby@ietf.org>; Tue, 2 Dec 2003 17:55:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJQt-0004gh-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:55:51 -0500
Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 1ARJQi-0004ga-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:55:50 -0500
Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by motgate.mot.com (Motorola/Motgate) with ESMTP id hB2MtUgd010004 for <seamoby@ietf.org>; Tue, 2 Dec 2003 15:55:33 -0700 (MST)
Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id hB2MqA58006953 for <seamoby@ietf.org>; Tue, 2 Dec 2003 16:52:11 -0600
Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id <XJ5BJCCX>; Tue, 2 Dec 2003 16:52:11 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB239138@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: 'Seamoby CTP Issues' <ctp_issues@danforsberg.info>, seamoby@ietf.org
Subject: RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n?
Date: Tue, 02 Dec 2003 16:52:10 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-Type: text/plain; charset="UTF-8"
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>

John,

Are you soliciting opinions on these alternatives as well?

Madjid

-----Original Message-----
From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of
John Loughney SEAMOBY-Issues
Sent: Friday, November 21, 2003 2:55 AM
To: seamoby@ietf.org
Subject: [Seamoby] [issue30] How to handle bad MN's authorization Token?



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.

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

v2.23.0 | Report a Bug | By Email