[Iptel] Re: WGLC of draft-ietf-iptel-trip-mib-05.txt
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Fri, 06 June 2003 14:56 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27170 for <iptel-archive@odin.ietf.org>; Fri, 6 Jun 2003 10:56:57 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h56EuX330297 for iptel-archive@odin.ietf.org; Fri, 6 Jun 2003 10:56:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56EuXB30294 for <iptel-web-archive@optimus.ietf.org>; Fri, 6 Jun 2003 10:56:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27104 for <iptel-web-archive@ietf.org>; Fri, 6 Jun 2003 10:56:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OIby-0002mO-00 for iptel-web-archive@ietf.org; Fri, 06 Jun 2003 10:54:34 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OIbx-0002mK-00 for iptel-web-archive@ietf.org; Fri, 06 Jun 2003 10:54:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56Eu4B30243; Fri, 6 Jun 2003 10:56:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56ErCB30050 for <iptel@optimus.ietf.org>; Fri, 6 Jun 2003 10:53:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26881 for <iptel@ietf.org>; Fri, 6 Jun 2003 10:53:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OIYj-0002jk-00 for iptel@ietf.org; Fri, 06 Jun 2003 10:51:13 -0400
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19OIYi-0002ja-00 for iptel@ietf.org; Fri, 06 Jun 2003 10:51:12 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h56EqXg04940 for <iptel@ietf.org>; Fri, 6 Jun 2003 09:52:33 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10PZDM>; Fri, 6 Jun 2003 16:52:31 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15501BC2973@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: David Zinman <dzinman@somanetworks.com>, iptel@ietf.org
Cc: bwijnen@lucent.com, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib-05.txt
Sender: iptel-admin@ietf.org
Errors-To: iptel-admin@ietf.org
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Id: IP Telephony <iptel.ietf.org>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
List-Archive: <https://www.ietf.org/pipermail/iptel/>
Date: Fri, 06 Jun 2003 16:52:21 +0200
So where are we with this? David promised (offline) to get us a a response somewhere around may 21st. It is now Jun 6th, and I have not seen any. I must admit that I am not on iptel WG list, so if you guys are discussing it there, then just tell me and I will go look in the archives. I suspect we need at least a revision before the doc can progress any further. Thanks, Bert > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: dinsdag 29 april 2003 18:57 > To: iptel@ietf.org > Cc: bwijnen@lucent.com > Subject: FW: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib-05.txt > > > > Romascanu, Dan (Dan) wrote: > > >Here are my comments concerning > draft-ietf-iptel-trip-mib-05.txt. The good news is that most > if not all are editorial and documentation problems. The bad > news is that IMO they need to be corrected before the WG can > forward this document to the IESG. > > > >1. See http://www.ops.ietf.org/mib-boilerplate.html for > updated formatted boilerplates for the SNMP Management > Framework, and Reference Sections. The good news is that they > are shorter, and there are less references to include, but > you must conform to the latest version. > >2. In several places you use 'This MIB provides...', 'This > MIB utilizes...', etc. The more accepted version is 'This MIB > module...' > >3. The Security section needs to be more detailed and > specific. You need to list explicitly all read-write and > read-create objects, as well as the read-only objects that > may contain sensitive information. You need to detail the > security risks that may result if the values of these objects > are changed or exposed. > >4. The readability of the document would be much improved if > an abbreviation section would be included. Some of the > abbreviations are not detailed, some other are explained only > after a few occurrences in the text (LS, ITAD) > >5. TriId TC DESCRIPTION should explain (or refer to an > explanation) how an IPv4 address maps into an Unsigned32 > >6. The keywords convention is not use in a consistent > manner. For example the 'should' in the DESCRIPTION clause of > tripCfgtable should be a SHOULD :-) > >7. DESCRIPTION clauses of tripCfgmaxPurgeTime and > tripCfgDisableTime - 'Indicates' instead of 'Indicate' > >8. Why do you need all the text in the DESCRIPTION of > tripCfgStorage? The StorageType TC defines how to use this > object. If you meant to restrict to a subset of values, this > is not clear. The last phrase seems to contradict the > requirement in the DESCRIPTION clause of the table. > >9. What does value 0 mean for tripPeerHoldTimeConfigured? > >10. 'location server' in the DESCRIPTION clause of > tripPeerOutUpdates is inconsistent with the other clauses in > the same table where it is abbreviated. > >11. There is no need for a DEFVAL of tripRouteTRIBMask, > which is a read-only object > >12. You should explain and maybe provide an example of how > tripRouteAdvertismentPath and tripRouteRoutedPath are encoded > in OCTET STRINGS > >13. Same for tripRouteUnknown > >14. DESCRIPTION clauses of tripNotiPeerAddrInetType and > tripNotifPeerAddr should mention that these object contain > the values of tripPeerRemoteAddrInettype and > tripPeerRemoteAddr (if I got these well) > >15. It is not clear what notification is used to transmit an > error code of 'cease'. Maybe I missed it? > >16. What are the error subcodes for FSM? > tripNotifPeerErrSubcode shows up in the OBJECTS list of the tripFSM > >17. RFC 3291 should be added to the references list > > > >I hope this helps. > > > >Dan > > > > > >-----Original Message----- > >From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] > >Sent: maandag 21 april 2003 22:34 > >To: Cullen Jennings > >Cc: iptel@ietf.org > >Subject: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib-05.txt > > > > > > > > > >Cullen Jennings wrote: > > > > > >>This is a SIMPLE working group Last Call for comments on the > >>draft-ietf-iptel-trip-mib-05 draft. > >> > >> > > > >Minor correction - this is an IPTEL last call ;) > > > >-Jonathan R. > > > > > > > >>This WGLC ends May 5, 2003. > >> > >>The draft is available at > >>http://www.ietf.org/internet-drafts/draft-ietf-iptel-trip-mib-05.txt > >> > >> > >>------------------------------------------------------------------- > >> > >> > >>A New Internet-Draft is available from the on-line Internet-Drafts > >>directories. > >>This draft is a work item of the IP Telephony Working Group > of the IETF. > >> > >> Title : Management Information Base for > Telephony Routing over > >> IP (TRIP) > >> Author(s) : D. Zinman, D. Walker, J. Jiang > >> Filename : draft-ietf-iptel-trip-mib-05.txt > >> Pages : 45 > >> Date : 2003-2-27 > >> > >>This memo defines a portion of the MIB (Management Information Base) > >>for use with network management protocols in the Internet community. > >>In particular, it describes a set of managed objects that are used > >>to manage for TRIP (Telephony Routing over IP) devices. > >> > >>A URL for this Internet-Draft is: > >>http://www.ietf.org/internet-drafts/draft-ietf-iptel-trip-mib-05.txt > >> > >>To remove yourself from the IETF Announcement list, send a > message to > >>ietf-announce-request with the word unsubscribe in the body > of the message. > >> > >>Internet-Drafts are also available by anonymous FTP. Login > with the username > >>"anonymous" and a password of your e-mail address. After logging in, > >>type "cd internet-drafts" and then > >> "get draft-ietf-iptel-trip-mib-05.txt". > >> > >>A list of Internet-Drafts directories can be found in > >>http://www.ietf.org/shadow.html > >>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >> > >> > >>Internet-Drafts can also be obtained by e-mail. > >> > >>Send a message to: > >> mailserv@ietf.org. > >>In the body type: > >> "FILE /internet-drafts/draft-ietf-iptel-trip-mib-05.txt". > >> > >>NOTE: The mail server at ietf.org can return the document in > >> MIME-encoded form by using the "mpack" utility. To use this > >> feature, insert the command "ENCODING mime" before the "FILE" > >> command. To decode the response(s), you will need "munpack" or > >> a MIME-compliant mail reader. Different MIME-compliant > mail readers > >> exhibit different behavior, especially when dealing with > >> "multipart" MIME messages (i.e. documents which have been split > >> up into multiple messages), so check your local documentation on > >> how to manipulate these messages. > >> > >> > >> > >> > > > > > > > > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel
- [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib-05.… Wijnen, Bert (Bert)
- Re: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib… Cullen Jennings
- Re: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib… David Zinman
- Re: [Iptel] Re: WGLC of draft-ietf-iptel-trip-mib… David Zinman