IETF Logo Mail Archive

[Mip4] Re: MIB for NEMOv4?

Henrik Levkowetz <henrik@levkowetz.com> Thu, 15 March 2007 14:29 UTC

Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqxV-0000ku-Tk; Thu, 15 Mar 2007 10:29:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqxV-0000hn-3W for mip4@ietf.org; Thu, 15 Mar 2007 10:29:37 -0400
Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRqxT-0008MH-IU for mip4@ietf.org; Thu, 15 Mar 2007 10:29:37 -0400
Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502) id F07583859A; Thu, 15 Mar 2007 15:29:34 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id DD9EA3800D; Thu, 15 Mar 2007 15:29:34 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id C687237E46; Thu, 15 Mar 2007 15:29:34 +0100 (CET)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from <henrik@levkowetz.com>) id 1HRqxS-0007VP-DY; Thu, 15 Mar 2007 15:29:34 +0100
Message-ID: <45F9583D.1060607@levkowetz.com>
Date: Thu, 15 Mar 2007 15:29:17 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <45F927F0.3080304@gmail.com> <45F93CD4.6020708@levkowetz.com> <45F94843.7050603@gmail.com>
In-Reply-To: <45F94843.7050603@gmail.com>
X-Enigmail-Version: 0.94.2.0
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: alexandru.petrescu@gmail.com, mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] Re: MIB for NEMOv4?
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1371448638=="
Errors-To: mip4-bounces@ietf.org

Hi Alex,

on 2007-03-15 14:21 Alexandru Petrescu said the following:
> Thanks Henrik,
> 
> I was wondering whether this is a good time to discuss about NEMOv4 
> (draft-ietf-mip4-nemo-v4-base-00.txt) features in MIB 
> (draft-ietf-mip4-rfc2006bis-03.txt).
> 
> Basically, there are few things that would be nice to be reflected in 
> the MIB:
> -Prefix Table (at HA).
> -Mobile Network Prefixes (at MN).
> -maybe others.
> 
> So, the initial comment is whether it makes any sense to do these 
> NEMOv4-related additions to Mobile IPv4 MIB?  (because it may be 
> considered that the MIB done for NEMOv6, draft-ietf-nemo-mib-02.txt in 
> NEMO WG, could treat IPv4 as well) (or because any other reason I miss).

For the NAT traversal, we made the decision to not include that in the
update of the original MIPv4 MIB, but instead create a separate MIB for
the NAT traversal functionality.

I believe the same approach would be best for a MIPv4 NEMO MIB, but some
of the MIB authors may have additional thoughts.


	Henrik


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

v2.23.0 | Report a Bug | By Email