RE: [Mip4] Re: MIB for NEMOv4?
"Kent Leung \(kleung\)" <kleung@cisco.com> Thu, 15 March 2007 17:30 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 1HRtmA-0005iR-GW; Thu, 15 Mar 2007 13:30:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRtm8-0005hg-OG for mip4@ietf.org; Thu, 15 Mar 2007 13:30:04 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HRtm3-0000t8-3K for mip4@ietf.org; Thu, 15 Mar 2007 13:30:04 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 15 Mar 2007 10:29:58 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l2FHTw0j009503; Thu, 15 Mar 2007 10:29:58 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2FHTmF2001577; Thu, 15 Mar 2007 17:29:56 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Mar 2007 10:29:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Re: MIB for NEMOv4?
Date: Thu, 15 Mar 2007 10:29:48 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52038578A7@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <45F957FF.1040707@ipunplugged.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mip4] Re: MIB for NEMOv4?
Thread-Index: AcdnDpvW/Z6AvClrRKKNbx3deHDsMwAF9x8g
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: Hans Sjostrand <hans@ipunplugged.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-OriginalArrivalTime: 15 Mar 2007 17:29:49.0494 (UTC) FILETIME=[8881C560:01C76727]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3568; t=1173979798; x=1174843798; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com> |Subject:=20RE=3A=20[Mip4]=20Re=3A=20MIB=20for=20NEMOv4? |Sender:=20; bh=H93lwyyDqKEOXwMg2rKDCN6yGWIcFFBABTD6LYChBh4=; b=MivtDNyZ4zx/aWXpkLE0A9vF34x1f4CojWCo3lfRyKj+SfmkpZEjqXmZGwDOihtpurn1jFdr w8f4RNP3wSwNKiyrVuwtPBppGsytCIHZM+B9ipiieiHsLzJEOv09mCH8;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
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>
Errors-To: mip4-bounces@ietf.org
I agree that NEMOv4 MIBs should be not be bundled into 2006bis and separation of MIBs is much more maintainable. Kent -----Original Message----- From: Hans Sjostrand [mailto:hans@ipunplugged.com] Sent: Thursday, March 15, 2007 7:28 AM To: Alexandru Petrescu Cc: Mobile IPv4 Mailing List Subject: [Mip4] Re: MIB for NEMOv4? Hi Alex, One of the things that we do in the 2006bis work is to create some mib framework so that no more than the core mip management functions are in the mobile ip mib. Basically to put the mipMIB OID under iana control. This makes it easy to extend mip with new management capabilities. Add ons, such as udp tunnelling should go into separate mibs. This is how all modern ietf mibs are done, see e.g. 15 mpls mibs under the ...mib-2.transmission.mplsStdMIB in http://www.iana.org/assignments/smi-numbers . I don't know the NEMO management need enough to say for sure, but I'm very reluctant to put in new stuff in 2006bis. Having a separate mib is a lot better, easier and more maintainable. The big monolithic 2006bis is really a bad idea, but there are a large set of legacy things that where traditionally in rfc2006 so we couldn't go the whole way. Looking forward to more mip mibs. /// Hasse On 2007-03-15 14:21, Alexandru Petrescu wrote: > 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). > > Alex > > Henrik Levkowetz wrote: >> Hi Alex, >> >> on 2007-03-15 12:03 Alexandru Petrescu said the following: >>> Hi MIP4, >>> >>> draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP >>> when NAT Traversal is used. As such contains knobs for keepalives, >>> force UDP, etc. I can comment on the draft in detail separately. >>> >>> But I wonder whether this is the only ongoing draft that configures >>> MIB knobs for Mobile IP? I am looking for a ongoing draft that >>> could eventually discuss NEMOv4 MIB knobs. Or maybe in >>> draft-sjostrand too (provided scope changes), I don't know. >>> >>> A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. >> >> Going to the mip4 status page (http://tools.ietf.org/wg/mip4/) shows >> you the 2006bis document among the active mip4 WG documents. >> >> Going to the draft and rfc search page >> (http://tools.ietf.org/search/) produces one hit, which is also the correct document. >> >> >> Regards, >> >> Henrik >> > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > -- 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/ -- 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/
- [Mip4] Other-than-NAT in draft-sjostrand-mip4-udp… Alexandru Petrescu
- Re: [Mip4] Other-than-NAT in draft-sjostrand-mip4… Henrik Levkowetz
- Re: MIB for NEMOv4? (was: [Mip4] Other-than-NAT i… Alexandru Petrescu
- [Mip4] Re: MIB for NEMOv4? Hans Sjostrand
- [Mip4] Re: MIB for NEMOv4? Henrik Levkowetz
- RE: [Mip4] Re: MIB for NEMOv4? Kent Leung (kleung)