[Mipshop] Re: FMIPv6 Discuss

Russ Housley <housley@vigilsec.com> Mon, 27 September 2004 15:47 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08890 for <mipshop-web-archive@ietf.org>; Mon, 27 Sep 2004 11:47:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBxqS-0008TM-8I for mipshop-web-archive@ietf.org; Mon, 27 Sep 2004 11:55:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBxa9-0008GE-JJ; Mon, 27 Sep 2004 11:38:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAbbS-0004Hh-3d for mipshop@megatron.ietf.org; Thu, 23 Sep 2004 17:58:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27230 for <mipshop@ietf.org>; Thu, 23 Sep 2004 17:58:11 -0400 (EDT)
Received: from woodstock.binhost.com ([144.202.240.3]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CAbiI-0003HT-Sn for mipshop@ietf.org; Thu, 23 Sep 2004 18:05:20 -0400
Received: (qmail 15377 invoked by uid 0); 23 Sep 2004 21:58:04 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (141.156.221.121) by woodstock.binhost.com with SMTP; 23 Sep 2004 21:58:04 -0000
Message-Id: <6.1.2.0.2.20040923175902.05d7db80@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Thu, 23 Sep 2004 17:59:15 -0400
To: rajeev@iprg.nokia.com, gab@sun.com, mipshop@ietf.org
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <415344DD.EE9C832A@iprg.nokia.com>
References: <415344DD.EE9C832A@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Mon, 27 Sep 2004 11:38:28 -0400
Subject: [Mipshop] Re: FMIPv6 Discuss
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Sender: mipshop-bounces@ietf.org
Errors-To: mipshop-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

Works for me.

Russ

At 05:49 PM 9/23/2004, Rajeev Koodli wrote:

>Hi Russ,
>
>please find my comments to your review of
>draft-ietf-mipshop-fast-mipv6-02.txt
>
>
>Discuss:
>
>   Several places, the document refers to AH in SHOULD and MUST
>statements,
>   yet there is no corresponding normative reference.
>
>Rajeev:> Will add.
>
>
>Comment:
>
>   The Security Considerations say:
>   :
>   : ... However, the future work, either as part of this document or in
>a
>   : separate document, may specify this security establishment.
>   :
>   Obviously, future work cannot be part of this document.  A subsequent
>   update to this document is possible.  Also, please change "security
>   establishment" to "security association establishment."
>
>Rajeev:> Would "However, future work may specify this security
>  association establishment" be okay?
>
>Thanks,
>
>-Rajeev


_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop