Re: [multipathtcp] New Version Notification for draft-mglt-mif-security-requirements-02.txt

Daniel Migault <mglt.ietf@gmail.com> Wed, 01 August 2012 17:25 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F10211E822A; Wed, 1 Aug 2012 10:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.538
X-Spam-Level:
X-Spam-Status: No, score=-1.538 tagged_above=-999 required=5 tests=[AWL=2.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJSmAF7m4uXQ; Wed, 1 Aug 2012 10:25:18 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B52F111E818B; Wed, 1 Aug 2012 10:25:00 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so14271091obb.31 for <multiple recipients>; Wed, 01 Aug 2012 10:25:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jLMMtU6WhcaOoO+Otul4G8z59xVgMdiZ8DJyXOgWBkw=; b=Bq2lwCSq92DdDNju0xY09Oskb50YgDjZhY5bSfNN838z5HL9BLTPPUxkRmS8Bj63JI 3g6yjD76SA7+vDQRHO8g3YOvdIKt7xfUPYoMCe34zeXTvs5lAxNswPX30Pk+9TVwEmuW abTIdb7OblVyCWdDYnF0Va/BG9UZCBlcaELnR0BepWCegyA1gbHV/i8zYdB+I0N9cDJt vfvJFZHscbVWjyIQF0R8SMdYPFus90twTbTkcbbNrF9xhvmreggAsMQ9E1AkTbZ4FfOx IrsAgbkmA0D6O1HinyPapj/dxNnl+iXUNurGPhEyB8FKS9DrCYNMz0hMtm0lIxUEwXZ6 PwlQ==
MIME-Version: 1.0
Received: by 10.182.2.233 with SMTP id 9mr30111943obx.11.1343841900346; Wed, 01 Aug 2012 10:25:00 -0700 (PDT)
Received: by 10.182.111.34 with HTTP; Wed, 1 Aug 2012 10:25:00 -0700 (PDT)
In-Reply-To: <CADZyTkmGjU+APTA+YJN4jJP9t4zyzg4g=C7=w643jGBpRyFnYA@mail.gmail.com>
References: <20120730045037.978.65071.idtracker@ietfa.amsl.com> <CADZyTkmGjU+APTA+YJN4jJP9t4zyzg4g=C7=w643jGBpRyFnYA@mail.gmail.com>
Date: Wed, 01 Aug 2012 19:25:00 +0200
Message-ID: <CADZyTkk5jNcOudKaChBDMb3PVuMPhK5f0R48VNL2G7SwP85U6Q@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: mif@ietf.org, ipsec@ietf.org, multipathtcp@ietf.org
Content-Type: multipart/alternative; boundary="f46d0444ea811abf3a04c6379351"
Subject: Re: [multipathtcp] New Version Notification for draft-mglt-mif-security-requirements-02.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:25:20 -0000

Hi,

We will be presenting MIF security requirements for IPsec at the mif
meeting at 1pm. If you have free time, we would appreciate you come and
participate in the discussion.

BR,
Daniel

On Mon, Jul 30, 2012 at 6:59 AM, Daniel Migault <mglt.ietf@gmail.com> wrote:

> Please find the new version of IPsec security requirements with Multiple
> Interfaces.
>
> Comments and suggestions are welcome
>
> BR
>
> Daniel
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Mon, Jul 30, 2012 at 6:50 AM
> Subject: New Version Notification for
> draft-mglt-mif-security-requirements-02.txt
> To: mglt.ietf@gmail.com
> Cc: carlw@mcsr-labs.org
>
>
>
> A new version of I-D, draft-mglt-mif-security-requirements-02.txt
> has been successfully submitted by Daniel Migault and posted to the
> IETF repository.
>
> Filename:        draft-mglt-mif-security-requirements
> Revision:        02
> Title:           IPsec Multiple Interfaces Requirements
> Creation date:   2012-07-30
> WG ID:           Individual Submission
> Number of pages: 16
> URL:
> http://www.ietf.org/internet-drafts/draft-mglt-mif-security-requirements-02.txt
> Status:
> http://datatracker.ietf.org/doc/draft-mglt-mif-security-requirements
> Htmlized:
> http://tools.ietf.org/html/draft-mglt-mif-security-requirements-02
> Diff:
> http://tools.ietf.org/rfcdiff?url2=draft-mglt-mif-security-requirements-02
>
> Abstract:
>    Multiple Interface Nodes (MIF Nodes) may use their Multiple
>    Interfaces to perform Mobility, Multihoming.  Then, these MIF Nodes
>    may also manage traffic between these Multiple Interfaces.  Because
>    IPsec has not been designed for Multiple Interfaces, MIF Nodes have
>    difficulties to benefit from MIF features with IPsec protected
>    communications.
>
>    This document provides use cases where IPsec protected communications
>    would take advantage of MIF features.  From these uses cases, we
>    identify the different IPsec features MIF Nodes would require.  Then,
>    we expose the limitations of the IPsec related protocols IKEv2 and
>    MOBIKE regarding to these MIF features before listing the MIF IPsec
>    Security Requirements that should be address by a extension of IKEv2
>    or MOBIKE.
>
>
>
>
> The IETF Secretariat
>
>
>
> --
> Daniel Migault
> Orange Labs -- Security
> +33 6 70 72 69 58
>



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