[Seamoby] [issue30] How to handle bad MN's authorization Token?
John Loughney SEAMOBY-Issues <ctp_issues@danforsberg.info> Fri, 21 November 2003 13:40 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13179 for <seamoby-archive@odin.ietf.org>; Fri, 21 Nov 2003 08:40:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW5-0006sG-VH for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:10 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALDe955026390 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW4-0006rF-QB for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 08:40:08 -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 IAA13139 for <seamoby-web-archive@ietf.org>; Fri, 21 Nov 2003 08:39:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANBW3-0002Hr-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANBW3-0002Ho-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW3-0006qK-I7; Fri, 21 Nov 2003 08:40:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN74T-0007I2-N6 for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 03:55:21 -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 DAA05804 for <seamoby@ietf.org>; Fri, 21 Nov 2003 03:55:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN74Q-0006Sa-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:18 -0500
Received: from media7.org ([194.100.13.106] helo=cafe-seed.net) by ietf-mx with smtp (Exim 4.12) id 1AN74Q-0006Ry-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:18 -0500
Received: (qmail 15118 invoked from network); 21 Nov 2003 08:54:42 -0000
Received: from unknown (HELO helsinki) (127.0.0.1) by localhost with SMTP; 21 Nov 2003 08:54:42 -0000
Content-Type: text/plain; charset="utf-8"
To: seamoby@ietf.org
From: John Loughney SEAMOBY-Issues <ctp_issues@danforsberg.info>
Reply-To: Seamoby CTP Issues <ctp_issues@danforsberg.info>
Date: Fri, 21 Nov 2003 08:54:42 +0000
MIME-Version: 1.0
Message-Id: <1069404882.47.0.767706199792.issue30@danforsberg.info>
X-Roundup-Name: Seamoby CTP Issues
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Seamoby] [issue30] How to handle bad MN's authorization Token?
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: quoted-printable
Content-Transfer-Encoding: quoted-printable
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] [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