IETF Logo Mail Archive

Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?

Rajeev Koodli <rajeev@iprg.nokia.com> Mon, 08 December 2003 19:15 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25361 for <seamoby-archive@odin.ietf.org>; Mon, 8 Dec 2003 14:15:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqZ-0000gU-Bk for seamoby-archive@odin.ietf.org; Mon, 08 Dec 2003 14:15:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8JF75m002624 for seamoby-archive@odin.ietf.org; Mon, 8 Dec 2003 14:15:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqZ-0000gF-8O for seamoby-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 14:15:07 -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 OAA25353 for <seamoby-web-archive@ietf.org>; Mon, 8 Dec 2003 14:14:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATQqW-00035i-00 for seamoby-web-archive@ietf.org; Mon, 08 Dec 2003 14:15:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATQqW-00035e-00 for seamoby-web-archive@ietf.org; Mon, 08 Dec 2003 14:15:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqV-0000fa-Kp; Mon, 08 Dec 2003 14:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqA-0000ez-9t for seamoby@optimus.ietf.org; Mon, 08 Dec 2003 14:14:45 -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 OAA25341 for <seamoby@ietf.org>; Mon, 8 Dec 2003 14:14:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATQq7-00035A-00 for seamoby@ietf.org; Mon, 08 Dec 2003 14:14:39 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ATQq7-00034g-00 for seamoby@ietf.org; Mon, 08 Dec 2003 14:14:39 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hB8JE1l30054; Mon, 8 Dec 2003 11:14:01 -0800
X-mProtect: <200312081914> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpd603SUy; Mon, 08 Dec 2003 11:14:00 PST
Message-ID: <3FD4CD6E.2075B826@iprg.nokia.com>
Date: Mon, 08 Dec 2003 11:13:50 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Seamoby CTP Issues <ctp_issues@danforsberg.info>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?
References: <1069404882.47.0.767706199792.issue30@danforsberg.info>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

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

v2.23.0 | Report a Bug | By Email