[netext] #18: Interface marking is needed

"netext issue tracker" <trac+netext@trac.tools.ietf.org> Mon, 26 November 2012 23:32 UTC

Return-Path: <trac+netext@trac.tools.ietf.org>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id AA10021F84DD for <netext@ietfa.amsl.com>; Mon, 26 Nov 2012 15:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.4
X-Spam-Status: No, score=-100.4 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_SOMA2=2.199, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id i3rZFdit0maT for <netext@ietfa.amsl.com>; Mon, 26 Nov 2012 15:32:57 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 2754921F841C for <netext@ietf.org>; Mon, 26 Nov 2012 15:32:56 -0800 (PST)
Received: from localhost ([]:52908 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+netext@trac.tools.ietf.org>) id 1Td8AZ-00080j-5P; Tue, 27 Nov 2012 00:32:55 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: netext issue tracker <trac+netext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: sarikaya@ieee.org
X-Trac-Project: netext
Date: Mon, 26 Nov 2012 23:32:55 -0000
X-URL: http://tools.ietf.org/netext/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/netext/trac/ticket/18
Message-ID: <058.1ea82dc2a6722fa4b8df6e5bd9ca98e8@trac.tools.ietf.org>
X-Trac-Ticket-ID: 18
X-SA-Exim-Rcpt-To: sarikaya@ieee.org, netext@ietf.org
X-SA-Exim-Mail-From: trac+netext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: netext@ietf.org
Subject: [netext] #18: Interface marking is needed
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 26 Nov 2012 23:32:57 -0000

#18: Interface marking is needed

 Sec. 5.1 on Multiple Proxy Care-of Address Registration needs to have a
 major revision. In RFC 6089, MN can register mcoa's because MN knows it
 has multiple interfaces. In PMIPv6, MAG sends PBU and MAG is connected to
 only one interface of MN not multiple so MAG can not make mcoa's or
 multiple proxy registrations.

 Solution: LMA after receiving PBU from the second MAG for an MN with an
 existing binding cache entry must mark this interface as visiting
 interface to distinguish it from the first "home" interface and LMA must
 indicate this marking in PBA. This way the second MAG knows it has made
 multiple proxy registration.
 MAG can then initiate flow mobility.

 Reporter:  sarikaya@ieee.org   |      Owner:  sarikaya@ieee.org
     Type:  defect              |     Status:  new
 Priority:  major               |  Milestone:  milestone1
Component:  pmipv6-flowmob      |    Version:  2.0
 Severity:  Active WG Document  |   Keywords:  PMIP flow mobility

Ticket URL: <http://tools.ietf.org/wg/netext/trac/ticket/18>
netext <http://tools.ietf.org/netext/>