Re: [netext] LMA initiated flow mobility scenario in I-D draft-bernardos-netext-pmipv6-flowmob

Stefano Faccin <> Tue, 16 August 2011 18:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAE4921F8BEE for <>; Tue, 16 Aug 2011 11:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_AVOID=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UMjQGQa7YJxv for <>; Tue, 16 Aug 2011 11:13:49 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AE66A21F8BEC for <>; Tue, 16 Aug 2011 11:13:49 -0700 (PDT)
X-AuditID: 0a412830-b7b0aae000007e14-2e-4e4ab3856ad4
Received: from ( []) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by (SBG) with SMTP id CA.5F.32276.583BA4E4; Tue, 16 Aug 2011 18:14:29 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 16 Aug 2011 14:14:37 -0400
Received: from ([fe80::cce5:67de:a150:3c3b]) by ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.01.0289.001; Tue, 16 Aug 2011 13:14:36 -0500
From: Stefano Faccin <>
To: "" <>, "" <>
Thread-Topic: [netext] LMA initiated flow mobility scenario in I-D draft-bernardos-netext-pmipv6-flowmob
Thread-Index: AQHMXCeI4KodSZYTPEqA8A8VWvP+JJUfyEog
Date: Tue, 16 Aug 2011 18:14:35 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-CA, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEKsWRmVeSWpSXmKPExsXC5Shmqtu62cvPYP5uSYuW9d1sFtd+PmV3 YPJYsuQnk8fdW5eYApiiGhhtEvPy8ksSS1IVUlKLk22VfFLTE3MUAooyyxKTKxVcMouTcxIz c1OLlBQyU2yVTJQUCnISk1NzU/NKbJUSCwpS81KU7LgUMIANUFlmnkJqXnJ+SmZeuq2SZ7C/ roWFqaWuoZKdLhJI+MedceriEeaCDvGKGwuPMTUw7hHrYuTkkBAwkfh4cw4jhC0mceHeejYQ W0igh0li7Q9jCHspo8Sjk9FdjFxA9lZGiWcLJzODJNgE1CSWPF8LZosIJEncebUNzBYWyJTY 9XY3VDxL4uKPKSwQtpHE1HcTwRawCKhKXPj9nwnE5hVwk9i0fiY7xDIzibVfX4DZnALmEluu ngDrZRSQldh99jpYPbOAuMStJ/OZII4WkFiy5zwzhC0q8fLxP9YuRg4gW1Hi9ek6EJNZQFNi /S59iE5FiSndD9khtgpKnJz5hAViq4zExMeLWSYwis9CsmAWQvcsJN2zkHQvYGRZxSiYm1Fs YGaYnJesV5SZq5eXWrKJEZw4NAx2ME7Yq3WIUYCDUYmH9+UaLz8h1sSy4srcQ4wSHMxKIryM aUAh3pTEyqrUovz4otKc1OJDjBbA4JnILMWdnA9Mankl8cYGBigcJXHeMGkDPyGBdGCKyk5N LUgtgmll4uCUamDMYAlt3V4nY/n7aKMWZ/a3D6w7rPx5f97zsqjie7RsrkNg8anZsiKfQm4k Jfz6wzT92xMl4bfu0wvu7jl6fn3e1PO9Lt0OwgeWzvXbKNfVJMx7a+vRPp9PXK9vz5uUsKRB J8V5xda1Qs03Z33llz8vFSUbs18ia4lxMOuEM9LcFw1XW+xLTJmkxFKckWioxVxUnAgAHgtf WTUDAAA=
Subject: Re: [netext] LMA initiated flow mobility scenario in I-D draft-bernardos-netext-pmipv6-flowmob
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Aug 2011 18:13:50 -0000

This sounds like a sensible approach and I fully support it.
Stefano Faccin

Standards Manager
Research In Motion Corporation 
5000 Riverside Drive 
Building 6, Brazos East, Ste. 100
Irving, Texas 75039 USA 
Note: located in PST

Office: (972) 910 3451  
Internal: 820.63451
Mobile : (510) 230 8422; 

 Consider the environment before printing.

-----Original Message-----
From: [] On Behalf Of
Sent: Tuesday, August 16, 2011 8:17 AM
Subject: [netext] LMA initiated flow mobility scenario in I-D draft-bernardos-netext-pmipv6-flowmob


One of the issues that has been raised (by Julien) is about the capability
that allows an LMA to initiate flow switching.
The I-D states:
   A second possible scenario is the following.  A multi-interfaced
   mobile node is attached to a PMIPv6-Domain and the LMA, at a given
   moment, decides to move a flow.  The LMA can decide to move a flow as
   a result of a policy change or upon receiving a trigger either based
   on network status or based on an event detected at the mobile node
   and transported via old or new MAG.  How this decision is taken is
   out of scope of this specification.


One of the possible consequences of such an action would be packets being
sent into a void because the MN may be no longer attached to that MAG
through the specific interface. There has not been a good solution that
has been presented to the WG. This issue has been considered as being a
fundamental flaw.

In view of the criticality of this flaw, I would recommend that the LMA
initiated flow mobility capability be removed from the I-D prior to it
being accepted as the WG doc. If WG members feel strongly about having
this feature, it can be included at a later time when a reasonable
solution to address the above concern has been presented and accepted.


netext mailing list

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.