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

Julien Bournelle <Julien.Bournelle@int-evry.fr> Tue, 16 December 2003 11:02 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10690 for <seamoby-archive@odin.ietf.org>; Tue, 16 Dec 2003 06:02:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxo-0004dp-Ki for seamoby-archive@odin.ietf.org; Tue, 16 Dec 2003 06:02:05 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGB24Bt017835 for seamoby-archive@odin.ietf.org; Tue, 16 Dec 2003 06:02:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxo-0004da-5L for seamoby-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 06:02:04 -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 GAA10674 for <seamoby-web-archive@ietf.org>; Tue, 16 Dec 2003 06:02:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxk-0004h1-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:02:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWCxj-0004gt-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:01:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AWCxj-0004gq-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:01:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxl-0004ct-ID; Tue, 16 Dec 2003 06:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxS-0004cc-HJ for seamoby@optimus.ietf.org; Tue, 16 Dec 2003 06:01:42 -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 GAA10668 for <seamoby@ietf.org>; Tue, 16 Dec 2003 06:01:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxO-0004gb-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWCxN-0004gU-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:38 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxN-0004eq-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:37 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20]) by herculanum.int-evry.fr (Postfix) with ESMTP id B7227340A3; Tue, 16 Dec 2003 12:01:08 +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 471CE3F45C; Tue, 16 Dec 2003 12:01:08 +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 M2003121612002408200 ; Tue, 16 Dec 2003 12:00:24 +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 597313F428; Tue, 16 Dec 2003 12:01:07 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AWCvh-000897-Ve; Tue, 16 Dec 2003 11:59:53 +0100
Date: Tue, 16 Dec 2003 11:59:53 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>, Seamoby CTP Issues <ctp_issues@danforsberg.info>, seamoby@ietf.org
Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token?
Message-ID: <20031216105953.GO16373@ipv6-5.int-evry.fr>
References: <EBF631554F9CD7118D0B00065BF34DCB239161@il27exm03.cig.mot.com> <3FDA56F5.8C43A449@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3FDA56F5.8C43A449@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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi 

On Fri, Dec 12, 2003 at 04:01:58PM -0800, Rajeev Koodli wrote:
> 
> Hi,
> 
> is your concern message tampering between pAR and nAR ?
> If so, that should apply to all contexts. I think we address that
> by saying the routers SHOULD have SAs.


I just wanted to note that the routers MUST have SAs. (ESP protection)

regards,

-- 
julien.bournelle@int-evry.fr

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby