[mif] Fwd: Manual Post Requested for draft-mglt-ipsec-mm-requirements

Daniel Migault <mglt.ietf@gmail.com> Thu, 24 September 2009 09:42 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 228933A689C for <mif@core3.amsl.com>; Thu, 24 Sep 2009 02:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXSGfUQh9yhG for <mif@core3.amsl.com>; Thu, 24 Sep 2009 02:42:12 -0700 (PDT)
Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 51BE93A67D2 for <mif@ietf.org>; Thu, 24 Sep 2009 02:42:10 -0700 (PDT)
Received: by fxm27 with SMTP id 27so1193913fxm.42 for <mif@ietf.org>; Thu, 24 Sep 2009 02:43:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=ik3YkPLt5xJf+zpA78mpNmBapnEem0n9n3FZgmtqC4M=; b=ByRq8mUM3xcMevANJK2qQzvDz3jI0IqJOO3GCCTy/ERPF/CeBUQAzigbe+N14DHE5I IETIq7Bv+KQ3ug0LueeXqjiognaz5zu9lL75XRoALS6SJW+yYDmIGVLIetOTGSf/MqEN cFvSi/P9yjhawgF/nbgnYPTVcUbXTQdyp8TAI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=o736n+MpgMiha333TBMciDZNzRjjbR/smXhz1KBix4CsdvdC4U8Xi23ROn7MSiQ3sJ MtxF+IsI/LOcyZokvSXlOORVCbB5sieJhUmWuLAcHcZuRmovZA62rmJ+Mvgc+ThfaWAK jMH85uMbkapqcK3O82K+vxGdgtYg4JqhmZUUo=
MIME-Version: 1.0
Received: by 10.239.141.155 with SMTP id c27mr320847hba.48.1253785394873; Thu, 24 Sep 2009 02:43:14 -0700 (PDT)
In-Reply-To: <20090924093200.B5F233A6950@core3.amsl.com>
References: <20090924093200.B5F233A6950@core3.amsl.com>
Date: Thu, 24 Sep 2009 11:43:14 +0200
Message-ID: <51eafbcb0909240243nb649495x13b65538ef80fe71@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: mif@ietf.org
Content-Type: multipart/alternative; boundary="001485f6c76a16053704744fa91c"
Subject: [mif] Fwd: Manual Post Requested for draft-mglt-ipsec-mm-requirements
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 09:42:15 -0000

Hi,
I have just posted a draft on IPsec requirements for mobility and
multihoming. Here multihoming is considered with multiple interfaces.
The draft provides scenarios from which are derived the requirements.

Feel free to make comments.

Regards,
Daniel

---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: Thu, Sep 24, 2009 at 11:32 AM
Subject: Manual Post Requested for draft-mglt-ipsec-mm-requirements
To: internet-drafts@ietf.org
Cc: mglt.ietf@gmail.com


Manual Posting Requested for following Internet-Draft:

I-D Submission Tool URL:
https://datatracker.ietf.org/idst/status.cgi?submission_id=18051


Filename:          draft-mglt-ipsec-mm-requirements
Version:           00
Staging URL:
http://www.ietf.org/staging/draft-mglt-ipsec-mm-requirements-00.txt
Title:             IPsec mobility and multihoming requirements : Problem
statement
Creation_date:     2009-09-24
WG ID:             Indvidual Submission
Number_of_pages: 32
Abstract:
Currently IPsec mobility is the purpose of MOBIKE [RFC4555] which is
the IKEv2 multihoming and mobility extension.  More specifically,
MOBIKE mobility support provides the ability to change the outer IP
address of a tunnel mode Security Association.  On the other hand
MOBIKE multihoming support provides the ability of a peer to inform
its correspondent that alternate IP addresses may be used if the
current IP address does not work any more.  This draft presents
requirements to extend mobility and multihoming facilities.  This
includes the use of simultaneous IP addresses as well as other IPsec
mode like transport mode.

Submitter: Daniel Migault (mglt.ietf@gmail.com)

Author(s):
Daniel Migault, mglt.ietf@gmail.com

-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58