IETF Logo Mail Archive

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

Rajeev Koodli <rajeev@iprg.nokia.com> Sat, 13 December 2003 00:05 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04400 for <seamoby-archive@odin.ietf.org>; Fri, 12 Dec 2003 19:05:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHP-00084S-AC for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:05:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBD056eJ030999 for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:05:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHO-000835-7G for seamoby-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 19:05:06 -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 TAA04374 for <seamoby-web-archive@ietf.org>; Fri, 12 Dec 2003 19:05:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxHK-0004tj-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:05:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUxHK-0004tg-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:05:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHM-00080E-L1; Fri, 12 Dec 2003 19:05:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxGd-0007x0-LT for seamoby@optimus.ietf.org; Fri, 12 Dec 2003 19:04:19 -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 TAA04307 for <seamoby@ietf.org>; Fri, 12 Dec 2003 19:04:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxGa-0004qf-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:04:16 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AUxGZ-0004pp-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:04:15 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hBD03fE25949; Fri, 12 Dec 2003 16:03:41 -0800
X-mProtect: <200312130003> 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 smtpdHorgWy; Fri, 12 Dec 2003 16:03:39 PST
Message-ID: <3FDA574E.C4D5907D@iprg.nokia.com>
Date: Fri, 12 Dec 2003 16:03:26 -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: Julien Bournelle <Julien.Bournelle@int-evry.fr>
CC: Seamoby CTP Issues <ctp_issues@danforsberg.info>, seamoby@ietf.org
Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?
References: <1069404882.47.0.767706199792.issue30@danforsberg.info> <3FD4CD6E.2075B826@iprg.nokia.com> <20031209085533.GA2605@ipv6-5.int-evry.fr>
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

Julien Bournelle wrote:

> > >
> >
> > 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 ?
>

This should be supplied in CTD. We don't need another
message particularly for carrying the error.

Regards,

-Rajeev


>
> 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

v2.23.0 | Report a Bug | By Email