[netlmm] Multiple HNP options (draft-ietf-netlmm-proxymip6-18)

"Tero Kauppinen" <tero.kauppinen@ericsson.com> Tue, 29 July 2008 11:16 UTC

Return-Path: <netlmm-bounces@ietf.org>
X-Original-To: netlmm-archive@optimus.ietf.org
Delivered-To: ietfarch-netlmm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E93F13A697B; Tue, 29 Jul 2008 04:16:10 -0700 (PDT)
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B01793A68A4 for <netlmm@core3.amsl.com>; Tue, 29 Jul 2008 04:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGBK4emP15Z4 for <netlmm@core3.amsl.com>; Tue, 29 Jul 2008 04:15:11 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id A13B13A6849 for <netlmm@ietf.org>; Tue, 29 Jul 2008 04:15:11 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id B5A45208B1 for <netlmm@ietf.org>; Tue, 29 Jul 2008 13:15:17 +0200 (CEST)
X-AuditID: c1b4fb3c-ae89cbb00000193b-92-488efbc5a32b
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9C8B3203E9 for <netlmm@ietf.org>; Tue, 29 Jul 2008 13:15:17 +0200 (CEST)
Received: from esealmw114.eemea.ericsson.se ([153.88.200.5]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 Jul 2008 13:15:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 29 Jul 2008 13:15:16 +0200
Message-ID: <D34CB2979BAB35448AB0A5FBAC56778D044D05CD@esealmw114.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Multiple HNP options (draft-ietf-netlmm-proxymip6-18)
Thread-Index: AcjxbGEybErnNECGTtSyiaEaqlGQVw==
From: Tero Kauppinen <tero.kauppinen@ericsson.com>
To: netlmm@ietf.org
X-OriginalArrivalTime: 29 Jul 2008 11:15:17.0376 (UTC) FILETIME=[61733000:01C8F16C]
X-Brightmail-Tracker: AAAAAA==
Subject: [netlmm] Multiple HNP options (draft-ietf-netlmm-proxymip6-18)
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: netlmm-bounces@ietf.org
Errors-To: netlmm-bounces@ietf.org

6.9.1.1.

3. The Home Network Prefix option(s) MUST be present in the Proxy
   Binding Update message.  If the mobile access gateway learns the
   mobile node's home network prefix(es) either from its policy
   store or from other means, the mobile access gateway MAY choose
   to request the local mobility anchor to allocate the requested
   prefix(es) by including a Home Network Prefix option for each of
   those requested prefixes.  The mobile access gateway MAY also
   choose to include just one Home Network Prefix option with the
   prefix value of ALL_ZERO, for requesting the local mobility
   anchor to do the prefix assignment.  However, when including a
   Home Network Prefix option with the prefix value of ALL_ZERO,
   then there MUST be only one instance of the Home Network prefix
   option in the request.

==> I read this: either there are multiple HNP options with the prefix
value of NON_ZERO or there is only one HNP option with the prefix value
of ALL_ZERO.

5.3.2. 

1. If there is at least one instance of Home Network Prefix option
   present in the Proxy Binding Update message with the prefix value
   set to ALL_ZERO, the local mobility anchor MUST allocate one or
   more home network prefix(es) to the mobile node and assign it to
   the new mobility session created for the mobile node. (snip)

==> This doesn't exclude the case if there are multiple HNP options with
the prefix value set to ALL_ZERO. What should LMA do then, drop the
packet or...?

/Tero
_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www.ietf.org/mailman/listinfo/netlmm