Re: [MEXT] One question on draft-ietf-mext-nemo-mib
Jari Arkko <jari.arkko@piuha.net> Tue, 13 January 2009 21:43 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F10528C190; Tue, 13 Jan 2009 13:43:36 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8527728C190 for <mext@core3.amsl.com>; Tue, 13 Jan 2009 13:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599]
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 6uSI8HYR9BP8 for <mext@core3.amsl.com>; Tue, 13 Jan 2009 13:43:26 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id AE18B28C181 for <mext@ietf.org>; Tue, 13 Jan 2009 13:43:26 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id A4E3A19871D; Tue, 13 Jan 2009 23:43:11 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 4EB5B198670; Tue, 13 Jan 2009 23:43:11 +0200 (EET)
Message-ID: <496D0AB8.2080006@piuha.net>
Date: Tue, 13 Jan 2009 23:42:16 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <496D0284.7070000@piuha.net> <Pine.GSO.4.63.0901131331590.24676@irp-view13.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0901131331590.24676@irp-view13.cisco.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: draft-ietf-mext-nemo-mib@tools.ietf.org, "mext@ietf.org" <mext@ietf.org>
Subject: Re: [MEXT] One question on draft-ietf-mext-nemo-mib
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Ok. Maybe this could be made clearer in the next revision. Jari Sri Gundavelli wrote: > Hi Jari, > > nemoMrPrefixRegMode is a RW object, for controlling the > registration mode. The other object is in the BUL entry, > reflecting the requested mode in a given registration. > > > Thanks > Sri > > > > On Tue, 13 Jan 2009, Jari Arkko wrote: > >> There was one question on this draft when I re-reviewed it: >> >> Why is the mode needed twice below: >> >> nemoMrRegistrationGroup OBJECT-GROUP >> OBJECTS { >> nemoMrBLMode, >> ... >> nemoMrPrefixRegMode, >> ... >> >> Is this a mistake, or am I missing something? >> >> In any case, I have sent the draft forward to IETF Last Call. >> >> Jari >> >> _______________________________________________ >> MEXT mailing list >> MEXT@ietf.org >> https://www.ietf.org/mailman/listinfo/mext >> > > _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] One question on draft-ietf-mext-nemo-mib Jari Arkko
- Re: [MEXT] One question on draft-ietf-mext-nemo-m… Sri Gundavelli
- Re: [MEXT] One question on draft-ietf-mext-nemo-m… Jari Arkko
- Re: [MEXT] One question on draft-ietf-mext-nemo-m… Sri Gundavelli