[netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-09.txt]

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Fri, 13 June 2014 17:16 UTC

Return-Path: <cjbc@it.uc3m.es>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 6004E1A0203 for <netext@ietfa.amsl.com>; Fri, 13 Jun 2014 10:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id F_DStsvlZCTN for <netext@ietfa.amsl.com>; Fri, 13 Jun 2014 10:16:26 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A9EE1B29B9 for <netext@ietf.org>; Fri, 13 Jun 2014 10:16:25 -0700 (PDT)
Received: from smtp02.uc3m.es (localhost []) by localhost.uc3m.es (Postfix) with ESMTP id 20FC37ED6 for <netext@ietf.org>; Fri, 13 Jun 2014 19:16:24 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [] (acorde.it.uc3m.es []) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp02.uc3m.es) by smtp02.uc3m.es (Postfix) with ESMTPSA id 14A137BF2 for <netext@ietf.org>; Fri, 13 Jun 2014 19:16:24 +0200 (CEST)
Message-ID: <1402679783.4063.11.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: netext@ietf.org
Date: Fri, 13 Jun 2014 19:16:23 +0200
Organization: Universidad Carlos III de Madrid
Content-Type: multipart/mixed; boundary="=-6xdYOAYoOJfMFCVKauF/"
X-Mailer: Evolution 3.8.5-2+b3
Mime-Version: 1.0
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--18.146-7.0-31-1
X-imss-scan-details: No--18.146-7.0-31-1
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/rTZ-WCLJzGfbeXghjQY6UZqMeJE
Subject: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-09.txt]
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext/>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 17:16:29 -0000


As agreed in London, I've updated the flow mobility draft to include
also the FMI/FMA signaling option (in addition to the use of Update
Notifications). The draft also includes a mechanism to allow selecting
which one of the two signaling mechanisms to use.

In my personal opinion, it'd be much cleaner and simpler to just specify
one signaling mechanism, but this is up to the WG to decide.

Comments, reviews and discussion on this new revision would be welcome.
Hopefully we could get at least a new revision before Toronto.


--- Begin Message ---
A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Network-Based Mobility Extensions Working Group of the IETF.

        Title           : Proxy Mobile IPv6 Extensions to Support Flow Mobility
        Author          : Carlos J. Bernardos
	Filename        : draft-ietf-netext-pmipv6-flowmob-09.txt
	Pages           : 24
	Date            : 2014-06-13

   Proxy Mobile IPv6 allows a mobile node to connect to the same Proxy
   Mobile IPv6 domain through different interfaces.  This document
   describes extensions to the Proxy Mobile IPv6 protocol that are
   required to support network based flow mobility over multiple
   physical interfaces.

   The extensions described in this document consist on the operations
   performed by the local mobility anchor and the mobile access gateway
   to manage the prefixes assigned to the different interfaces of the
   mobile node, as well as how the forwarding policies are handled by
   the network to ensure consistent flow mobility management.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

netext mailing list
--- End Message ---