Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?
Julien Bournelle <Julien.Bournelle@int-evry.fr> Tue, 09 December 2003 09:01 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18724 for <seamoby-archive@odin.ietf.org>; Tue, 9 Dec 2003 04:01:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjs-0003zo-9l for seamoby-archive@odin.ietf.org; Tue, 09 Dec 2003 04:01:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9914EX015343 for seamoby-archive@odin.ietf.org; Tue, 9 Dec 2003 04:01:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjr-0003zH-Fu for seamoby-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 04:01:03 -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 EAA18695 for <seamoby-web-archive@ietf.org>; Tue, 9 Dec 2003 04:00:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjo-00045H-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 04:01:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATdjo-00045E-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 04:01:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjp-0003xx-4j; Tue, 09 Dec 2003 04:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjH-0003wr-1H for seamoby@optimus.ietf.org; Tue, 09 Dec 2003 04:00:27 -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 EAA18678 for <seamoby@ietf.org>; Tue, 9 Dec 2003 04:00:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjE-00044j-00 for seamoby@ietf.org; Tue, 09 Dec 2003 04:00:24 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjD-00044O-00 for seamoby@ietf.org; Tue, 09 Dec 2003 04:00:23 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20]) by herculanum.int-evry.fr (Postfix) with ESMTP id E6129356F0; Tue, 9 Dec 2003 09:56:38 +0100 (CET)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19]) by spartebis.int-evry.fr (Postfix) with SMTP id D34CE3F428; Tue, 9 Dec 2003 09:56:38 +0100 (CET)
Received: from sparte.int-evry.fr ([157.159.10.11]) by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003120909560816548 ; Tue, 09 Dec 2003 09:56:09 +0100
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 270CA3F428; Tue, 9 Dec 2003 09:56:38 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1ATdeX-0000gv-Oh; Tue, 09 Dec 2003 09:55:33 +0100
Date: Tue, 09 Dec 2003 09:55:33 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: Seamoby CTP Issues <ctp_issues@danforsberg.info>, seamoby@ietf.org
Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?
Message-ID: <20031209085533.GA2605@ipv6-5.int-evry.fr>
References: <1069404882.47.0.767706199792.issue30@danforsberg.info> <3FD4CD6E.2075B826@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3FD4CD6E.2075B826@iprg.nokia.com>
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>
Hi, On Mon, Dec 08, 2003 at 11:13:50AM -0800, Rajeev Koodli wrote: > 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. I agree with that but how to carry this error ? In the CTD message or do we create a new message to carry error ? thanks, > > -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 > -- julien.bournelle@int-evry.fr _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] [issue30] How to handle bad MN's author… John Loughney SEAMOBY-Issues
- Re: [Seamoby] [issue30] How to handle bad MN's au… Rajeev Koodli
- Re: [Seamoby] [issue30] How to handle bad MN's au… Julien Bournelle
- Re: [Seamoby] [issue30] How to handle bad MN's au… Rajeev Koodli