From malloc-admin@ietf.org Tue Aug 14 17:30:27 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15483 for ; Tue, 14 Aug 2001 17:30:26 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06346; Tue, 14 Aug 2001 17:28:21 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06317 for ; Tue, 14 Aug 2001 17:28:20 -0400 (EDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15456 for ; Tue, 14 Aug 2001 17:27:06 -0400 (EDT) Received: from sunlabs.East.Sun.COM ([129.148.75.250]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00760; Tue, 14 Aug 2001 14:28:18 -0700 (PDT) Received: from sun.com (dhcp75-167 [129.148.75.167]) by sunlabs.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA07144; Tue, 14 Aug 2001 17:28:17 -0400 (EDT) Message-ID: <3B7997CF.3953B907@sun.com> Date: Tue, 14 Aug 2001 17:27:43 -0400 From: Steve Hanna Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Thaler CC: malloc@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Malloc] MALLOC MIB comments Sender: malloc-admin@ietf.org Errors-To: malloc-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Multicast-Address Allocation X-BeenThere: malloc@ietf.org Content-Transfer-Encoding: 7bit Dave, Here are my comments on the latest version of the MALLOC MIB (draft-ietf-malloc-mib-04.txt). I don't know very much about SNMP and MIBs, so many of these comments may not be useful. But I think I may have caught a few errors, so it's probably worth your time to review them. Thanks, Steve ----------- Comments on draft-ietf-malloc-mib-04.txt 1) Some objects seems to have incorrect MAX-ACCESS values. This is more likely due to my misunderstanding of how this value is used, but here are my concerns: mallocScopeFirstAddress and mallocScopeFirstAddressType are marked as not-accessible. I think they should be read-create, so that you can read their values and create new entries in the Scope table (if allowed). mallocAllocRangeFirstAddress and mallocAllocRangeFirstAddressType are also marked as not-accessible. I would expect these to be read-create. 2) The description of mallocAllocRangeAdvertisable says "The default value is true if the scope is divisible, and is false otherwise." What do you mean by default? Do you mean that some program will set the value to these values unless overridden by a human being? I suspect you just mean that most people will want to set the value to true when the scope is divisible and false otherwise. If that's what you mean, you should say that. 3) The description of mallocAllocRangeTotalRequestedAddrs says "The approximate number of addresses in the range which there is potential demand for among MAASs, as determined by a Prefix Coordinator." I think that would be more grammatically correct if it read "The approximate number of addresses in the range for which there is potential demand among MAASs, as determined by a Prefix Coordinator." 4) In the mallocServerGroup, there are several objects missing that I would expect to find there. mallocScopeFirstAddress and mallocScopeFirstAddressType are missing, as are mallocAllocRangeFirstAddress and mallocAllocRangeFirstAddressType and mallocScopeExclusionFirstAddress and mallocScopeExclusionFirstAddressType and mallocScopeNameLangName. I suspect that these are not errors, but due to some strange MIB feature that automatically includes them because they're indexes of their tables and other elements of the tables are included in this group. I dunno. mallocScopeLastAddressType is missing, but mallocScopeLastAddress is there. I suspect that's an error. 5) In the mallocClientScopeGroup, mallocScopeSSM seems to be missing. 6) The description of mallocPrefixCoordinatorGroup says that it is a "collection of notifications". I think it's just a "collection of objects". Isn't that right? 7) In the IANA-MALLOC-MIB, IANAmallocRangeSource still includes an aap value. I don't think that's needed, since development of AAP has been abandoned. If it is later resuscitated, we can always ask IANA to assign an IANAmallocRangeSource value to it. _______________________________________________ Malloc mailing list Malloc@ietf.org http://www1.ietf.org/mailman/listinfo/malloc From malloc-admin@ietf.org Mon Aug 20 02:27:53 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07710 for ; Mon, 20 Aug 2001 02:27:48 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA17518; Mon, 20 Aug 2001 02:21:35 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA17489 for ; Mon, 20 Aug 2001 02:21:34 -0400 (EDT) Received: from deimos.campus.luth.se (deimos.campus.luth.se [130.240.195.143]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07057 for ; Mon, 20 Aug 2001 02:20:16 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by deimos.campus.luth.se (8.11.2/8.11.2) id f7K6HgR30773 for malloc@ietf.org; Mon, 20 Aug 2001 08:17:42 +0200 Message-Id: <200108200617.f7K6HgR30773@deimos.campus.luth.se> Content-Type: text/plain; charset="iso-8859-1" From: Fredrik Pettersson To: malloc@ietf.org Date: Mon, 20 Aug 2001 08:17:42 +0200 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [Malloc] MALLOC Implementation Sender: malloc-admin@ietf.org Errors-To: malloc-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Multicast-Address Allocation X-BeenThere: malloc@ietf.org Content-Transfer-Encoding: 8bit Hi! During the period from january to may 2001 a project to implement parts of the MALLOC architecture was performed at Luleå University of Technology. The project was performed by 6 computer science students as a part of the final year of education, and the task was to implement the MADCAP protocol and to integrate this with a partial implementation from 2000. Telia Research AB sponsored the project. The result was a client-side MADCAP library which implements parts of the abstract API defined in RFC2771, and a MAAS server program which can communicate with MADCAP clients. The server contains AAP code developed in a similar project during 2000. The code from the project is now released under the GPL, and can be downloaded from the original project homepage at http://deimos.campus.luth.se/malloc/index.shtml, where all the documentation from the project may also be found. In order to create a more permanent site for the download of the code, there is also a project at SourceForge where the code is available. The address is http://sourceforge.net/projects/malloc/. I am listed as the project admin there, but I am currently unable to be active in any further development of the code since I am working on my Masters Thesis. If anyone would like to continue the development using the facilities provided by SourceForge, contact me and I can add you as a developer. All the original developers can be contacted at malloc@deimos.campus.luth.se. //Fredrik Pettersson _______________________________________________ Malloc mailing list Malloc@ietf.org http://www1.ietf.org/mailman/listinfo/malloc From malloc-admin@ietf.org Mon Aug 20 19:30:57 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07303 for ; Mon, 20 Aug 2001 19:30:57 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21722; Mon, 20 Aug 2001 19:31:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21694 for ; Mon, 20 Aug 2001 19:31:20 -0400 (EDT) Received: from inet-vrs-04.redmond.corp.microsoft.com (mail4.microsoft.com [131.107.3.122]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA07286 for ; Mon, 20 Aug 2001 19:30:04 -0400 (EDT) Received: from 157.54.7.67 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 20 Aug 2001 16:30:48 -0700 Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-imc-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 20 Aug 2001 16:30:48 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 20 Aug 2001 16:30:47 -0700 Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 20 Aug 2001 16:30:34 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.5701.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 20 Aug 2001 16:30:34 -0700 Message-ID: <2E33960095B58E40A4D3345AB9F65EC1B58150@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> Thread-Topic: MALLOC MIB comments thread-index: AcElCCR05wunqiAKRKqAfW6QVRdIOwExkewg From: "Dave Thaler" To: "Steve Hanna" Cc: X-OriginalArrivalTime: 20 Aug 2001 23:30:34.0685 (UTC) FILETIME=[1C3E0ED0:01C129D0] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id TAA21695 Subject: [Malloc] RE: MALLOC MIB comments Sender: malloc-admin@ietf.org Errors-To: malloc-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Multicast-Address Allocation X-BeenThere: malloc@ietf.org Content-Transfer-Encoding: 8bit Steve, thanks for reviewing! > Comments on draft-ietf-malloc-mib-04.txt > > 1) Some objects seems to have incorrect MAX-ACCESS values. > This is more likely due to my misunderstanding of how > this value is used, but here are my concerns: > > mallocScopeFirstAddress and mallocScopeFirstAddressType > are marked as not-accessible. I think they should be > read-create, so that you can read their values and create > new entries in the Scope table (if allowed). Any objects that appear in the INDEX clause of the table are not-accessible, since one can read their values by reading any other object in the table, since their value comes back in the OID of the object read. Hence, the status is correct (but thanks for asking). > mallocAllocRangeFirstAddress and mallocAllocRangeFirstAddressType > are also marked as not-accessible. I would expect these > to be read-create. Same reason. > 2) The description of mallocAllocRangeAdvertisable says > "The default value is true if the scope is divisible, > and is false otherwise." What do you mean by default? If you create a new row in the table via SNMP and don't specify a value for this object. > Do you mean that some program will set the value > to these values unless overridden by a human being? Yes. > I suspect you just mean that most people will want to > set the value to true when the scope is divisible and > false otherwise. If that's what you mean, you should > say that. It's not what I meant. In MIBs, there's a DEFVAL clause that you can put in the default value to be used during row creation (it's just informative to humans, the clause isn't used by the management station to do anything differently). Here, we can't use a DEFVAL clause since there's not a single default value for all cases, and hence the DESCRIPTION specifies the default instead. > 3) The description of mallocAllocRangeTotalRequestedAddrs > says "The approximate number of addresses in the range > which there is potential demand for among MAASs, as > determined by a Prefix Coordinator." I think that would > be more grammatically correct if it read "The approximate > number of addresses in the range for which there is > potential demand among MAASs, as determined by a Prefix > Coordinator." Agree. > 4) In the mallocServerGroup, there are several objects > missing that I would expect to find there. > > mallocScopeFirstAddress and mallocScopeFirstAddressType > are missing, as are mallocAllocRangeFirstAddress and > mallocAllocRangeFirstAddressType and > mallocScopeExclusionFirstAddress and > mallocScopeExclusionFirstAddressType and > mallocScopeNameLangName. I suspect that these are not > errors, but due to some strange MIB feature that > automatically includes them because they're indexes > of their tables and other elements of the tables are > included in this group. I dunno. Yep, that's exactly right. Objects which are not-accessible don't appear in conformance groups. > mallocScopeLastAddressType is missing, but > mallocScopeLastAddress is there. I suspect that's an > error. I think you're right. Will fix. > 5) In the mallocClientScopeGroup, mallocScopeSSM seems to > be missing. Yep, will fix. > 6) The description of mallocPrefixCoordinatorGroup says > that it is a "collection of notifications". I think > it's just a "collection of objects". Isn't that right? Yep, will fix. > 7) In the IANA-MALLOC-MIB, IANAmallocRangeSource still > includes an aap value. I don't think that's needed, > since development of AAP has been abandoned. If it is > later resuscitated, we can always ask IANA to assign > an IANAmallocRangeSource value to it. Sounds reasonable. Thanks again! -Dave _______________________________________________ Malloc mailing list Malloc@ietf.org http://www1.ietf.org/mailman/listinfo/malloc From malloc-admin@ietf.org Fri Aug 24 14:53:17 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12416 for ; Fri, 24 Aug 2001 14:53:17 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10318; Fri, 24 Aug 2001 14:49:26 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10289 for ; Fri, 24 Aug 2001 14:49:25 -0400 (EDT) Received: from inet-vrs-02.redmond.corp.microsoft.com (mail2.microsoft.com [131.107.3.124]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12325 for ; Fri, 24 Aug 2001 14:48:04 -0400 (EDT) Received: from 157.54.1.52 by inet-vrs-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 24 Aug 2001 11:47:48 -0700 Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-06.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 24 Aug 2001 11:47:45 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 24 Aug 2001 11:47:43 -0700 Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 24 Aug 2001 11:47:28 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.5716.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 24 Aug 2001 11:47:27 -0700 Message-ID: <2E33960095B58E40A4D3345AB9F65EC10290E608@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> Thread-Topic: Follow-up from last call of MALLOC MIB Thread-Index: AcEpQHesEZ6BIcDUQkK1wx6Gf3tTTwDjJXpw From: "Dave Thaler" To: X-OriginalArrivalTime: 24 Aug 2001 18:47:28.0203 (UTC) FILETIME=[392999B0:01C12CCD] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA10290 Subject: [Malloc] Follow-up from last call of MALLOC MIB Sender: malloc-admin@ietf.org Errors-To: malloc-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Multicast-Address Allocation X-BeenThere: malloc@ietf.org Content-Transfer-Encoding: 8bit During WG last call, comments were received from Steve Hanna, Bill Fenner, and Brian Haberman. I will be acting on their comments and will submit an updated draft shortly. -Dave _______________________________________________ Malloc mailing list Malloc@ietf.org http://www1.ietf.org/mailman/listinfo/malloc