[multipathtcp] Fwd: New Version Notification for draft-mglt-mif-security-requirements-01.txt
Daniel Migault <mglt.ietf@gmail.com> Thu, 29 March 2012 15:20 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 6BF6821F8847; Thu, 29 Mar 2012 08:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level:
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.124, 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 FDv1VaGnx-lB; Thu, 29 Mar 2012 08:20:42 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 39D0321F883F; Thu, 29 Mar 2012 08:20:42 -0700 (PDT)
Received: by yenm5 with SMTP id m5so1705809yen.31 for <multiple recipients>; Thu, 29 Mar 2012 08:20:41 -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=XSj4mm6v+u2cHtSm/zEtKifghznIUo7kXhDJszeIKbA=; b=sT2dYiAMqyxaskqkJedG43QI+aEj/Nh+51GQslY4pfy0Ub0CBI/L4I/iHjIkfZEG2U TWrz0h0xB0XJSISoWF+RY0lSxIK691wR4hYyJ/1jQzfyGxEi3K+kXQiCfQcjLK8NIUdq 263a/v9zdZyIE5oTptrSimXn4a3qm+bPWwnRhe3CLWFgnhqg8jdmfUenX9mtUT05iQOG eK0sjW6M7kWFSSFtaK/3h1WXHnn/k6PluXncWY2DHU6LyQyFvwdNupszz2y4hMNTDl3N LGqs/Qs5Ab0PmoZ7K1cN9o+pxIFXwd/zZhLMGxiRkguPJ16kWv/Zlj6uu5OhdRm+pffZ ZMMg==
MIME-Version: 1.0
Received: by 10.68.125.195 with SMTP id ms3mr745941pbb.62.1333034441316; Thu, 29 Mar 2012 08:20:41 -0700 (PDT)
Received: by 10.142.133.19 with HTTP; Thu, 29 Mar 2012 08:20:41 -0700 (PDT)
In-Reply-To: <20120329151424.12323.65627.idtracker@ietfa.amsl.com>
References: <20120329151424.12323.65627.idtracker@ietfa.amsl.com>
Date: Thu, 29 Mar 2012 17:20:41 +0200
Message-ID: <CADZyTknBvq1JZVJ5GbwPxCgfg40wk1iBLeC10=N7kQEQa++bwA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: mif@ietf.org, "multipathtcp@ietf.org Mailing List" <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b2e4cdc5918cf04bc634450"
Subject: [multipathtcp] Fwd: New Version Notification for draft-mglt-mif-security-requirements-01.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: Thu, 29 Mar 2012 15:20:43 -0000
Hi, Please find the version 01 of draft-mglt-mif-security-requirements-01.txt. Feel free to make comments on it. We would like to thank those who provided comments for version 00. They were very useful for us. Regards, Daniel ---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: Thu, Mar 29, 2012 at 5:14 PM Subject: New Version Notification for draft-mglt-mif-security-requirements-01.txt To: mglt.ietf@gmail.com Cc: carlw@mcsr-labs.org A new version of I-D, draft-mglt-mif-security-requirements-01.txt has been successfully submitted by Daniel Migault and posted to the IETF repository. Filename: draft-mglt-mif-security-requirements Revision: 01 Title: Multiple Interfaces IPsec Security Requirements Creation date: 2012-03-29 WG ID: Individual Submission Number of pages: 11 Abstract: ISPs wants to take advantage of MIF Transport protocols like SCTP, MPTCP to enhance their End User's experience when the End User has been offloaded on WLAN. In addition, WLAN are untrusted so ISPs MUST Secure at least some of their End Users's communications. For various reasons IPsec is the protocol they choose to secure the communications. Currently, IPsec is not adapted to Multiple Interfaces Environment. IPsec can hardly be configured in a proper way which may result in breaking End Users' communications. At least, it makes it very hard for the End Users to combine Security with MIF enhancements. MOBIKE partly address the problem for a single Interface. This draft provides the problem statement and defines the IPsec Security Requirements for MIF. The IETF Secretariat -- Daniel Migault Orange Labs -- Security +33 6 70 72 69 58
- [multipathtcp] Fwd: New Version Notification for … Daniel Migault