[netext] #19: Issue in using BID from RFC 5648

"netext issue tracker" <trac+netext@trac.tools.ietf.org> Wed, 02 January 2013 19:53 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1B821F8890 for <netext@ietfa.amsl.com>; Wed, 2 Jan 2013 11:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.499
X-Spam-Level:
X-Spam-Status: No, score=-101.499 tagged_above=-999 required=5 tests=[AWL=1.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QczS3j9nWFRk for <netext@ietfa.amsl.com>; Wed, 2 Jan 2013 11:53:30 -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 6217121F888E for <netext@ietf.org>; Wed, 2 Jan 2013 11:53:30 -0800 (PST)
Received: from localhost ([127.0.0.1]:55985 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 1TqUNR-00041C-53; Wed, 02 Jan 2013 20:53:25 +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: Wed, 02 Jan 2013 19:53:25 -0000
X-URL: http://tools.ietf.org/netext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/netext/trac/ticket/19
Message-ID: <058.bcc117d55633f322db3cf82014276600@trac.tools.ietf.org>
X-Trac-Ticket-ID: 19
X-SA-Exim-Connect-IP: 127.0.0.1
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] #19: Issue in using BID from RFC 5648
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: Wed, 02 Jan 2013 19:53:31 -0000

#19: Issue in using BID from RFC 5648

 In the draft, BID is mentioned many times: Fig. 3 & Fig. 5 show BID values
 1 from MAG1 and 2 from MAG2.

 BID is mainly
    defined in RFC 5648 for multiple-interfaced mobile nodes with Mobile
 IPv6
    functionalities.  The BID is an identification number used to
    distinguish multiple bindings REGISTERED BY the MOBILE NODE.  Each
    BID is GENERATED and MANAGED by a MOBILE NODE in Mobile IPv6.

 In
    Proxy Mobile IPv6, MOBILITY MANAGEMENT of MOBILE NODES WITH
 MULTIPLE INTERFACES IS RUN in DIFFERENT INDEPENDENT MAGs.
 Each MAG sees only one interface.
 Because of all these reasons, BID
 loses its meaning.

 In the draft, Sec. 5.1, it says that BID is assigned and used by the local
 mobility anchor.
 It is not explained why LMA would need BID in searching the binding cache
 for flows? Remember that RFC 5648 is not about flow mobility, so RFC 5648
 assumes a single entry for each interface of MN in the binding cache.

-- 
--------------------------------+----------------------------------------
 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:  BID, PMIPv6, flow mobility
--------------------------------+----------------------------------------

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