From exim@www1.ietf.org Fri Aug 1 09:32:16 2003 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 JAA09697 for ; Fri, 1 Aug 2003 09:02:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iZXr-0002Gu-TL for iptel-archive@odin.ietf.org; Fri, 01 Aug 2003 09:02:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h71D27I2008721 for iptel-archive@odin.ietf.org; Fri, 1 Aug 2003 09:02:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iZXq-0002Eo-OJ for iptel-web-archive@optimus.ietf.org; Fri, 01 Aug 2003 09:02:07 -0400 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 JAA09449 for ; Fri, 1 Aug 2003 09:01:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iZXG-0001Jp-FH for iptel-web-archive@ietf.org; Fri, 01 Aug 2003 09:01:30 -0400 Date: Fri, 01 Aug 2003 09:01:30 -0400 Message-ID: <20030801130130.29120.48549.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: iptel-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, iptel-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for iptel-web-archive@ietf.org: List Password // URL ---- -------- iptel@ietf.org aroxgu https://www.ietf.org/mailman/options/iptel/iptel-web-archive%40ietf.org From exim@www1.ietf.org Fri Aug 1 15:29:52 2003 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 PAA07096 for ; Fri, 1 Aug 2003 15:29:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifaf-0001IE-Gg for iptel-archive@odin.ietf.org; Fri, 01 Aug 2003 15:29:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h71JTPdS004969 for iptel-archive@odin.ietf.org; Fri, 1 Aug 2003 15:29:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifaf-0001I4-D7 for iptel-web-archive@optimus.ietf.org; Fri, 01 Aug 2003 15:29:25 -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 PAA06944 for ; Fri, 1 Aug 2003 15:29:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ifae-0005SV-00 for iptel-web-archive@ietf.org; Fri, 01 Aug 2003 15:29:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ifad-0005SR-00 for iptel-web-archive@ietf.org; Fri, 01 Aug 2003 15:29:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifaL-000182-VL; Fri, 01 Aug 2003 15:29:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifZz-0000pR-2s for iptel@optimus.ietf.org; Fri, 01 Aug 2003 15:28:43 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06838; Fri, 1 Aug 2003 15:28:39 -0400 (EDT) Message-Id: <200308011928.PAA06838@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-cpl-07.txt,.ps 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 01 Aug 2003 15:28:39 -0400 --NextPart 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 : CPL: A Language for User Control of Internet Telephony Services Author(s) : J. Lennox, X. Wu, H. Schulzrinne Filename : draft-ietf-iptel-cpl-07.txt,.ps Pages : 76 Date : 2003-8-1 The Call Processing Language (CPL) is a language that can be used to describe and control Internet telephony services. It is designed to be implementable on either network servers or user agent servers. It is meant to be simple, extensible, easily edited by graphical clients, and independent of operating system or signalling protocol. It is suitable for running on a server where users may not be allowed to execute arbitrary programs, as it has no variables, loops, or ability to run external programs. This document is a product of the IP Telephony (IPTEL) working group of the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at iptel@lists.research.bell-labs.com and/or the authors. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-07.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-cpl-07.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-cpl-07.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. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-8-1153727.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-cpl-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-cpl-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-8-1153727.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 08:35:32 2003 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 IAA14204 for ; Mon, 11 Aug 2003 08:35:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mBtC-0000xi-6k for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 08:35:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BCZ6QX003694 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 08:35:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mBtC-0000xV-3E for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 08:35:06 -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 IAA14188 for ; Mon, 11 Aug 2003 08:35:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mBtA-0005QL-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 08:35:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mBtA-0005QH-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 08:35:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mBt7-0000vr-0F; Mon, 11 Aug 2003 08:35:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mBsB-0000tf-GU for iptel@optimus.ietf.org; Mon, 11 Aug 2003 08:34:03 -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 IAA14137 for ; Mon, 11 Aug 2003 08:33:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mBsA-0005Pp-00 for iptel@ietf.org; Mon, 11 Aug 2003 08:34:02 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 19mBs9-0005Pk-00 for iptel@ietf.org; Mon, 11 Aug 2003 08:34:01 -0400 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7BCWvCi024107 for ; Mon, 11 Aug 2003 07:32:57 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7BCWsCi024065 for ; Mon, 11 Aug 2003 07:32:55 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C36004.D4A08572" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Message-ID: Thread-Topic: Comments on draft-ietf-iptel-trip-mib-07.txt Thread-Index: AcNgBNSq/9BTvvuYS7+xX0R4dQFLdA== From: "Romascanu, Dan (Dan)" To: "list iptel" Cc: "David Zinman" , "Bert Wijnen (E-mail)" Subject: [Iptel] Comments on draft-ietf-iptel-trip-mib-07.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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 15:33:55 +0300 This is a multi-part message in MIME format. ------_=_NextPart_001_01C36004.D4A08572 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable The latest version addresses all major issues in my previous review, and = does not seem to have introduced new ones.=20 I am left with two editorial comments, which may be addressed down the = road: 1. The copyright year in the DESCRIPTION clauses of the two MIB modules = still says 2002. 2. One of the Area Directors was replaced since the previous = Internet-Draft publication (Section 14).=20 Thanks, Dan ------_=_NextPart_001_01C36004.D4A08572 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-ietf-iptel-trip-mib-07.txt

The latest version addresses = all major issues in my previous review, and does not seem to have = introduced new ones.

I am left with two editorial = comments, which may be addressed down the road:

1. The copyright year in the = DESCRIPTION clauses of the two MIB modules still says 2002.

2. One of the Area Directors = was replaced since the previous Internet-Draft publication (Section 14). =

Thanks,

Dan

------_=_NextPart_001_01C36004.D4A08572-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 09:21:26 2003 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 JAA15269 for ; Mon, 11 Aug 2003 09:21:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCbd-0002cM-B8 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:21:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BDL1DV010062 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCbd-0002cD-6m for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 09:21:01 -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 JAA15257 for ; Mon, 11 Aug 2003 09:20:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCbb-0005pv-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:20:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mCbb-0005ps-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:20:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCbc-0002bf-3h; Mon, 11 Aug 2003 09:21:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCbN-0002bE-BR for iptel@optimus.ietf.org; Mon, 11 Aug 2003 09:20:45 -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 JAA15243 for ; Mon, 11 Aug 2003 09:20:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCbL-0005pf-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:20:43 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19mCbK-0005pV-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:20:42 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7BDK8716197 for ; Mon, 11 Aug 2003 08:20:09 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Mon, 11 Aug 2003 15:20:07 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502257C49@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Romascanu, Dan (Dan)" , list iptel Cc: David Zinman , "Bert Wijnen (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 15:20:01 +0200 Thanks Dan for your review. I think the copyright-year will be addressed by RFC-Editor when it gets there. So unless there are othe reasons for a respin, I can live with it for now. But it seems anew rev may be wise because of my additional comments below I wonder why sect 14 is needed. I leave this up to TSV AD(s) on how to deal with it. From a MIB review perspective I have a few additional comments): - I think that RFC2788 needs to be added to normative references since this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 - TRIP-TC module does not have a REVISION clause, which we actually DO want to have. - I get these smilint warnings: .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row `tripRouteTypeEntry' can exceed OID size limit by 6 subidentifier(s) .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row `tripPeerEntry' can exceed OID size limit by 6 subidentifier(s) SMICng complains about the same. I see 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer as the first accessible object int tripRouteTypeEntry. So prefix is 11 subids index objects are 5 integer-based objects and a var size octet string. so we have 5 plus 1 (for lenght) plus number of octets as index part. So we have 6 fixed (5 integers plus length value) subids plus one for every octet in the octet string. So max size for OCTET STRING should be 111 octets, not 117. Similar calculation for tripPeerEntry seem to tell me max lenght can be 113 instead of 119. This makes me thin k that it is kind of strange to ha ve different size for InetAddress, is it not. Another way to solve these concerns is to add something to the DESCRIPTION clause that states the implementation issues w.r.t. 128 subids instad of setting arbitray size constrains in the SYNTAX field (that we may regret if the 128 subid limit ever gets removed). A good example of text for this would be in arcEntry in draft-ietf-disman-conditionmib-09.txt or sctpAssocLocalAddrEntry in draft-ietf-sigtran-sctp-mib-10.txt - smicng (strict checking) also complains: E: f(trip.mi2), (1629,33) Item "applRFC2788Group" should be IMPORTed it is not a MUST that you do import it. But as the mib-review-guidelines state, it would be good to do so to not cause confusion. From a generic review - Missing reference [BCP0014] - Ref [RFC2026] probably goes away when this becomes an RFC Thanks, Bert > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: maandag 11 augustus 2003 14:34 > To: list iptel > Cc: David Zinman; Bert Wijnen (E-mail) > Subject: Comments on draft-ietf-iptel-trip-mib-07.txt > > > The latest version addresses all major issues in my previous > review, and does not seem to have introduced new ones. > > I am left with two editorial comments, which may be addressed > down the road: > 1. The copyright year in the DESCRIPTION clauses of the two > MIB modules still says 2002. > 2. One of the Area Directors was replaced since the previous > Internet-Draft publication (Section 14). > > Thanks, > Dan > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 09:24:27 2003 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 JAA15319 for ; Mon, 11 Aug 2003 09:24:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCeY-0002jh-9M for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:24:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BDO27u010511 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:24:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCeY-0002jS-3N for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 09:24:02 -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 JAA15314 for ; Mon, 11 Aug 2003 09:23:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCeW-0005rR-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:24:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mCeV-0005rO-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:23:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCeW-0002hu-U1; Mon, 11 Aug 2003 09:24:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCdd-0002hB-81 for iptel@optimus.ietf.org; Mon, 11 Aug 2003 09:23:05 -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 JAA15304 for ; Mon, 11 Aug 2003 09:22:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCdb-0005qu-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:23:03 -0400 Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19mCda-0005qg-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:23:02 -0400 Received: from dynamicsoft.com ([63.113.46.98]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h7BDMV3m002701; Mon, 11 Aug 2003 09:22:31 -0400 (EDT) Message-ID: <3F379894.40100@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" CC: list iptel , David Zinman , "Bert Wijnen (E-mail)" Subject: Re: [Iptel] Comments on draft-ietf-iptel-trip-mib-07.txt References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 09:22:28 -0400 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dan, Thanks for all your help in reviewing this document! -Jonathan R. Romascanu, Dan (Dan) wrote: > The latest version addresses all major issues in my previous review, and > does not seem to have introduced new ones. > > I am left with two editorial comments, which may be addressed down the road: > > 1. The copyright year in the DESCRIPTION clauses of the two MIB modules > still says 2002. > > 2. One of the Area Directors was replaced since the previous > Internet-Draft publication (Section 14). > > Thanks, > > Dan > -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 09:32:27 2003 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 JAA15513 for ; Mon, 11 Aug 2003 09:32:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCmI-00032Z-Pf for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:32:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BDW2vW011681 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 09:32:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCmI-00032K-MZ for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 09:32:02 -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 JAA15501 for ; Mon, 11 Aug 2003 09:31:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCmG-0005tg-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:32:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mCmG-0005td-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 09:32:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCmH-00031s-Ge; Mon, 11 Aug 2003 09:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mCmG-00031d-5q for iptel@optimus.ietf.org; Mon, 11 Aug 2003 09:32:00 -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 JAA15498 for ; Mon, 11 Aug 2003 09:31:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mCmE-0005ta-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:31:58 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19mCmD-0005tW-00 for iptel@ietf.org; Mon, 11 Aug 2003 09:31:57 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7BDVOA11726 for ; Mon, 11 Aug 2003 08:31:24 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Mon, 11 Aug 2003 15:31:23 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502257C50@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Jonathan Rosenberg Cc: list iptel , "Dan Romascanu (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Iptel] FW: RE: Comments on draft-ietf-iptel-trip-mib-07.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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 15:31:16 +0200 Does this mean that David's address info needs to be updated as well??!! Thanks, Bert -----Original Message----- From: dzinman@somanetworks.com [mailto:dzinman@somanetworks.com] Sent: maandag 11 augustus 2003 15:20 To: bwijnen@lucent.com Subject: Re: RE: Comments on draft-ietf-iptel-trip-mib-07.txt Please be advised that David Zinman is no longer employed at SOMA Networks, Inc. For SOMA business matters requiring assistance, please contact Glenn McAllister at glenn@somanetworks.com. -------- Original Message -------- > Thanks Dan for your review. > > I think the copyright-year will be addressed by RFC-Editor when it gets there. > So unless there are othe reasons for a respin, I can live with it for now. > But it seems anew rev may be wise because of my additional comments below > > I wonder why sect 14 is needed. I leave this up to TSV AD(s) on how to deal > with it. > > From a MIB review perspective I have a few additional comments): > - I think that RFC2788 needs to be added to normative references since > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > - TRIP-TC module does not have a REVISION clause, which we actually DO > want to have. > - I get these smilint warnings: > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row `tripRouteTypeEntry' > can exceed OID size limit by 6 subidentifier(s) > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row `tripPeerEntry' can > exceed OID size limit by 6 subidentifier(s) > SMICng complains about the same. I see > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer > as the first accessible object int tripRouteTypeEntry. So prefix is 11 subids > index objects are 5 integer-based objects and a var size octet string. > so we have 5 plus 1 (for lenght) plus number of octets as index part. > So we have 6 fixed (5 integers plus length value) subids plus one for every > octet in the octet string. So max size for OCTET STRING should be > 111 octets, not 117. > Similar calculation for tripPeerEntry seem to tell me max lenght can be 113 > instead of 119. > This makes me thin k that it is kind of strange to ha ve different size for InetAddress, > is it not. Another way to solve these concerns is to add something to the DESCRIPTION > clause that states the implementation issues w.r.t. 128 subids instad of setting > arbitray size constrains in the SYNTAX field (that we may regret if the 128 subid > limit ever gets removed). A good example of text for this would be in > arcEntry in draft-ietf-disman-conditionmib-09.txt or sctpAssocLocalAddrEntry in > draft-ietf-sigtran-sctp-mib-10.txt > - smicng (strict checking) also complains: > E: f(trip.mi2), (1629,33) Item "applRFC2788Group" should be IMPORTed > it is not a MUST that you do import it. But as the mib-review-guidelines state, > it would be good to do so to not cause confusion. > > From a generic review > - Missing reference [BCP0014] > - Ref [RFC2026] probably goes away when this becomes an RFC > > Thanks, > Bert > > > -----Original Message----- > > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > > Sent: maandag 11 augustus 2003 14:34 > > To: list iptel > > Cc: David Zinman; Bert Wijnen (E-mail) > > Subject: Comments on draft-ietf-iptel-trip-mib-07.txt > > > > > > The latest version addresses all major issues in my previous > > review, and does not seem to have introduced new ones. > > > > I am left with two editorial comments, which may be addressed > > down the road: > > 1. The copyright year in the DESCRIPTION clauses of the two > > MIB modules still says 2002. > > 2. One of the Area Directors was replaced since the previous > > Internet-Draft publication (Section 14). > > > > Thanks, > > Dan > > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 12:58:29 2003 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 MAA22927 for ; Mon, 11 Aug 2003 12:58:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mFzh-0003R1-Hp for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 12:58:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BGw5RE013203 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 12:58:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mFzh-0003Qk-Da for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 12:58:05 -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 MAA22906 for ; Mon, 11 Aug 2003 12:57:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mFzf-0007BP-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 12:58:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mFze-0007BM-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 12:58:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mFzc-0003PU-82; Mon, 11 Aug 2003 12:58:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mFz1-0003PF-W6 for iptel@optimus.ietf.org; Mon, 11 Aug 2003 12:57:24 -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 MAA22883 for ; Mon, 11 Aug 2003 12:57:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mFz0-0007BI-00 for iptel@ietf.org; Mon, 11 Aug 2003 12:57:22 -0400 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 19mFyz-0007BF-00 for iptel@ietf.org; Mon, 11 Aug 2003 12:57:21 -0400 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7BGvFeE022439 for ; Mon, 11 Aug 2003 12:57:15 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7BGvCeE022395 for ; Mon, 11 Aug 2003 12:57:13 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Message-ID: Thread-Topic: Comments on draft-ietf-iptel-trip-mib-07.txt Thread-Index: AcNgC06hMO7V2N7sQ16WjcbvkepTpgAHageA From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "list iptel" Content-Transfer-Encoding: quoted-printable Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 19:57:17 +0300 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Bert is correct with respect to the OID size limit errors. I was using a = non-edited version of the MIB (with the root OID xxxx-ed) and did not = get the errors at compilation. These were rather major issues in my = previous review, and I suggest that you fix them before advancing the = document. I think that we talked about something similar the DESCRIPTION = text suggested by Bert on the corridors in Vienna. Regards, Dan =20 > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: 11 August, 2003 4:20 PM > To: Romascanu, Dan (Dan); list iptel > Cc: David Zinman; Bert Wijnen (E-mail) > Subject: RE: Comments on draft-ietf-iptel-trip-mib-07.txt >=20 >=20 > Thanks Dan for your review. >=20 > I think the copyright-year will be addressed by RFC-Editor=20 > when it gets there. > So unless there are othe reasons for a respin, I can live=20 > with it for now. > But it seems anew rev may be wise because of my additional=20 > comments below >=20 > I wonder why sect 14 is needed. I leave this up to TSV AD(s)=20 > on how to deal > with it. >=20 > From a MIB review perspective I have a few additional comments): > - I think that RFC2788 needs to be added to normative=20 > references since > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > - TRIP-TC module does not have a REVISION clause, which we actually DO > want to have. > - I get these smilint warnings: > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of=20 > row `tripRouteTypeEntry' > can exceed OID size limit by 6 subidentifier(s) > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of=20 > row `tripPeerEntry' can > exceed OID size limit by 6 subidentifier(s) > SMICng complains about the same. I see > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer=20 > as the first accessible object int tripRouteTypeEntry. So=20 > prefix is 11 subids > index objects are 5 integer-based objects and a var size=20 > octet string. > so we have 5 plus 1 (for lenght) plus number of octets as=20 > index part. > So we have 6 fixed (5 integers plus length value) subids=20 > plus one for every > octet in the octet string. So max size for OCTET STRING should be > 111 octets, not 117. > Similar calculation for tripPeerEntry seem to tell me max=20 > lenght can be 113 > instead of 119. > This makes me thin k that it is kind of strange to ha ve=20 > different size for InetAddress, > is it not. Another way to solve these concerns is to add=20 > something to the DESCRIPTION > clause that states the implementation issues w.r.t. 128=20 > subids instad of setting > arbitray size constrains in the SYNTAX field (that we may=20 > regret if the 128 subid > limit ever gets removed). A good example of text for this=20 > would be in > arcEntry in draft-ietf-disman-conditionmib-09.txt or=20 > sctpAssocLocalAddrEntry in > draft-ietf-sigtran-sctp-mib-10.txt > - smicng (strict checking) also complains: > E: f(trip.mi2), (1629,33) Item "applRFC2788Group"=20 > should be IMPORTed > it is not a MUST that you do import it. But as the=20 > mib-review-guidelines state, > it would be good to do so to not cause confusion. >=20 > From a generic review=20 > - Missing reference [BCP0014] > - Ref [RFC2026] probably goes away when this becomes an RFC >=20 > Thanks, > Bert=20 >=20 > > -----Original Message----- > > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > > Sent: maandag 11 augustus 2003 14:34 > > To: list iptel > > Cc: David Zinman; Bert Wijnen (E-mail) > > Subject: Comments on draft-ietf-iptel-trip-mib-07.txt > >=20 > >=20 > > The latest version addresses all major issues in my previous=20 > > review, and does not seem to have introduced new ones.=20 > >=20 > > I am left with two editorial comments, which may be addressed=20 > > down the road: > > 1. The copyright year in the DESCRIPTION clauses of the two=20 > > MIB modules still says 2002. > > 2. One of the Area Directors was replaced since the previous=20 > > Internet-Draft publication (Section 14).=20 > >=20 > > Thanks, > > Dan > >=20 >=20 _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 15:00:33 2003 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 PAA28320 for ; Mon, 11 Aug 2003 15:00:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mHto-00089h-Q4 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 15:00:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BJ0818031343 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 15:00:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mHto-00089S-3Q for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 15:00:08 -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 PAA28290 for ; Mon, 11 Aug 2003 15:00:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mHtk-0000d4-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 15:00:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mHtk-0000d1-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 15:00:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mHti-00088j-Rw; Mon, 11 Aug 2003 15:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mHta-00087o-Fm for iptel@optimus.ietf.org; Mon, 11 Aug 2003 14:59:54 -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 OAA28278 for ; Mon, 11 Aug 2003 14:59:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mHtX-0000cm-00 for iptel@ietf.org; Mon, 11 Aug 2003 14:59:51 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19mHtW-0000cd-00 for iptel@ietf.org; Mon, 11 Aug 2003 14:59:50 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7BIxIA18545 for ; Mon, 11 Aug 2003 13:59:18 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Mon, 11 Aug 2003 20:59:16 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502257CF0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: David Zinman , "Wijnen, Bert (Bert)" , "Romascanu, Dan (Dan)" , list iptel Cc: David Zinman , "Bert Wijnen (E-mail)" Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 20:59:05 +0200 Looks good. I understand that the warnings do not go away. But they are "warnings", and so we check if the DESCRIPTION clause has the proper instructions to implementers, and they now do. So it looks good to me. Thanks, Bert > -----Original Message----- > From: David Zinman [mailto:dzinman@rogers.com] > Sent: maandag 11 augustus 2003 20:07 > To: Wijnen, Bert (Bert); Romascanu, Dan (Dan); list iptel > Cc: David Zinman; Bert Wijnen (E-mail) > Subject: Re: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt > > > inline: > > ----- Original Message ----- > From: "Wijnen, Bert (Bert)" > To: "Romascanu, Dan (Dan)" ; "list iptel" > > Cc: "David Zinman" ; "Bert Wijnen (E-mail)" > > Sent: Monday, August 11, 2003 9:20 AM > Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt > > > > Thanks Dan for your review. > > > > I think the copyright-year will be addressed by RFC-Editor > when it gets > there. > > So unless there are othe reasons for a respin, I can live > with it for now. > > But it seems anew rev may be wise because of my additional > comments below > > > > I wonder why sect 14 is needed. I leave this up to TSV > AD(s) on how to > deal > > with it. > > > > I am leaving section 14 in for now. > > > From a MIB review perspective I have a few additional comments): > > - I think that RFC2788 needs to be added to normative > references since > > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > > - TRIP-TC module does not have a REVISION clause, which we > actually DO > > want to have. > > Added both the reference to RFC 2788 and the REVISION clause > in TRIP-TC > > > - I get these smilint warnings: > > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row > `tripRouteTypeEntry' > > can exceed OID size limit by 6 subidentifier(s) > > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row > `tripPeerEntry' can > > exceed OID size limit by 6 subidentifier(s) > > SMICng complains about the same. I see > > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer > > as the first accessible object int tripRouteTypeEntry. So > prefix is 11 > subids > > index objects are 5 integer-based objects and a var size > octet string. > > so we have 5 plus 1 (for lenght) plus number of octets as > index part. > > So we have 6 fixed (5 integers plus length value) subids > plus one for > every > > octet in the octet string. So max size for OCTET STRING should be > > 111 octets, not 117. > > Similar calculation for tripPeerEntry seem to tell me max > lenght can be > 113 > > instead of 119. > > This makes me thin k that it is kind of strange to ha ve > different size > for InetAddress, > > is it not. Another way to solve these concerns is to add > something to > the DESCRIPTION > > clause that states the implementation issues w.r.t. 128 > subids instad of > setting > > arbitray size constrains in the SYNTAX field (that we > may regret if the > 128 subid > > limit ever gets removed). A good example of text for this > would be in > > arcEntry in draft-ietf-disman-conditionmib-09.txt or > sctpAssocLocalAddrEntry in > > draft-ietf-sigtran-sctp-mib-10.txt > > - smicng (strict checking) also complains: > > I have removed the restriction on the index sizes, and included the > description > of the 128 limit. However this will not get rid of the warnings. > > > E: f(trip.mi2), (1629,33) Item "applRFC2788Group" > should be IMPORTed > > it is not a MUST that you do import it. But as the > mib-review-guidelines > state, > > it would be good to do so to not cause confusion. > > I have included the IMPORT > > > > From a generic review > > - Missing reference [BCP0014] > > Added reference to this BCP (RFC2119) > > > - Ref [RFC2026] probably goes away when this becomes an RFC > > I'm leaving this in for now. > > > > > Thanks, > > Bert > > > > I have also addressed Dan's concern about the copyright year > and the area > directors in section 14. > > I will submit the new draft (08) if there are no further comments. > > Cheers, > DZ > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Mon Aug 11 19:59:34 2003 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 TAA11360 for ; Mon, 11 Aug 2003 19:59:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mMZ8-0001a1-9G for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 19:59:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BNx6lw006067 for iptel-archive@odin.ietf.org; Mon, 11 Aug 2003 19:59:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mMZ8-0001Zh-3t for iptel-web-archive@optimus.ietf.org; Mon, 11 Aug 2003 19:59:06 -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 TAA11351 for ; Mon, 11 Aug 2003 19:59:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mMZ5-0003Gg-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 19:59:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mMZ4-0003Gd-00 for iptel-web-archive@ietf.org; Mon, 11 Aug 2003 19:59:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mMZ4-0001Z5-4I; Mon, 11 Aug 2003 19:59:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mMYu-0001Yo-MW for iptel@optimus.ietf.org; Mon, 11 Aug 2003 19:58:52 -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 TAA11342 for ; Mon, 11 Aug 2003 19:58:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mMYs-0003GU-00 for iptel@ietf.org; Mon, 11 Aug 2003 19:58:50 -0400 Received: from cypress.neustar.com ([209.173.57.84]) by ietf-mx with esmtp (Exim 4.12) id 19mMYs-0003Fe-00 for iptel@ietf.org; Mon, 11 Aug 2003 19:58:50 -0400 Received: from chiimc01.npac.com ([10.32.90.4]) by cypress.neustar.com (8.11.6/8.11.6) with ESMTP id h7BNwBG17580; Mon, 11 Aug 2003 23:58:11 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id ; Mon, 11 Aug 2003 19:00:58 -0500 Message-ID: From: "Peterson, Jon" To: "'Wijnen, Bert (Bert)'" , "Romascanu, Dan (Dan)" , list iptel Cc: David Zinman Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 11 Aug 2003 19:00:18 -0500 I don't really think we need Section 14 either. I would counsel the authors to remove it. Jon Peterson NeuStar, Inc. > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: Monday, August 11, 2003 6:20 AM > To: Romascanu, Dan (Dan); list iptel > Cc: David Zinman; Bert Wijnen (E-mail) > Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt ... > > I wonder why sect 14 is needed. I leave this up to TSV AD(s) on how to deal > with it. > ... _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Tue Aug 12 10:18:30 2003 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 KAA15392 for ; Tue, 12 Aug 2003 10:18:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mZyQ-0004Mm-3Q for iptel-archive@odin.ietf.org; Tue, 12 Aug 2003 10:18:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7CEI6d6016782 for iptel-archive@odin.ietf.org; Tue, 12 Aug 2003 10:18:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mZyQ-0004Mb-0Z for iptel-web-archive@optimus.ietf.org; Tue, 12 Aug 2003 10:18:06 -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 KAA15337 for ; Tue, 12 Aug 2003 10:17:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mZyN-0000m4-00 for iptel-web-archive@ietf.org; Tue, 12 Aug 2003 10:18:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mZyN-0000m0-00 for iptel-web-archive@ietf.org; Tue, 12 Aug 2003 10:18:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mZyL-0004Kt-6V; Tue, 12 Aug 2003 10:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mZxS-0004KG-Pt for iptel@optimus.ietf.org; Tue, 12 Aug 2003 10:17:06 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15152; Tue, 12 Aug 2003 10:16:59 -0400 (EDT) Message-Id: <200308121416.KAA15152@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-trip-mib-08.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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 12 Aug 2003 10:16:59 -0400 --NextPart 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-08.txt Pages : 45 Date : 2003-8-12 This memo defines a portion of the MIB (Management Information Base) module 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-08.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-08.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-08.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. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-8-12095342.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trip-mib-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-trip-mib-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-8-12095342.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Tue Aug 26 15:04:05 2003 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 PAA23121 for ; Tue, 26 Aug 2003 15:04:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rj6Q-0005xS-Pl for iptel-archive@odin.ietf.org; Tue, 26 Aug 2003 15:03:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QJ3cbO022898 for iptel-archive@odin.ietf.org; Tue, 26 Aug 2003 15:03:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rj6Q-0005xF-Gx for iptel-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 15:03:38 -0400 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 PAA22932 for ; Tue, 26 Aug 2003 15:03:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rj5r-0005qi-8n; Tue, 26 Aug 2003 15:03:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rOkS-0001q4-Me for iptel@optimus.ietf.org; Mon, 25 Aug 2003 17:19:37 -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 RAA16759 for ; Mon, 25 Aug 2003 17:19:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rOkQ-0007Ww-00 for iptel@ietf.org; Mon, 25 Aug 2003 17:19:34 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19rOkP-0007Wd-00 for iptel@ietf.org; Mon, 25 Aug 2003 17:19:33 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7PLIw727556 for ; Mon, 25 Aug 2003 16:19:00 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Mon, 25 Aug 2003 23:18:57 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550245BC36@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'David Zinman'" , "'Romascanu, Dan (Dan)'" , "'list iptel'" Cc: "'David Zinman'" , "'Bert Wijnen (E-mail)'" , "Jon Peterson (E-mail)" Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 25 Aug 2003 23:18:55 +0200 Seems all fine to me now. One remaining NIT, can be addressed during RFC-Editing phase as far as I am concerned: RFC2119 needs to be referenced NORMATIVELY. Jon, as far as I am concerned this one is ready for IETF Last Call and then IESG Agenda. I assume that the MIB Doctor (Dan Romascanu) agrees. Thanks, Bert > -----Original Message----- > From: Wijnen, Bert (Bert) > Sent: maandag 11 augustus 2003 20:59 > To: David Zinman; Wijnen, Bert (Bert); Romascanu, Dan (Dan); > list iptel > Cc: David Zinman; Bert Wijnen (E-mail) > Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt > > > Looks good. > I understand that the warnings do not go away. > But they are "warnings", and so we check if the DESCRIPTION > clause has the proper instructions to implementers, and they now > do. So it looks good to me. > > Thanks, > Bert > > > -----Original Message----- > > From: David Zinman [mailto:dzinman@rogers.com] > > Sent: maandag 11 augustus 2003 20:07 > > To: Wijnen, Bert (Bert); Romascanu, Dan (Dan); list iptel > > Cc: David Zinman; Bert Wijnen (E-mail) > > Subject: Re: [Iptel] RE: Comments on > draft-ietf-iptel-trip-mib-07.txt > > > > > > inline: > > > > ----- Original Message ----- > > From: "Wijnen, Bert (Bert)" > > To: "Romascanu, Dan (Dan)" ; "list iptel" > > > > Cc: "David Zinman" ; "Bert Wijnen > (E-mail)" > > > > Sent: Monday, August 11, 2003 9:20 AM > > Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt > > > > > > > Thanks Dan for your review. > > > > > > I think the copyright-year will be addressed by RFC-Editor > > when it gets > > there. > > > So unless there are othe reasons for a respin, I can live > > with it for now. > > > But it seems anew rev may be wise because of my additional > > comments below > > > > > > I wonder why sect 14 is needed. I leave this up to TSV > > AD(s) on how to > > deal > > > with it. > > > > > > > I am leaving section 14 in for now. > > > > > From a MIB review perspective I have a few additional comments): > > > - I think that RFC2788 needs to be added to normative > > references since > > > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > > > - TRIP-TC module does not have a REVISION clause, which we > > actually DO > > > want to have. > > > > Added both the reference to RFC 2788 and the REVISION clause > > in TRIP-TC > > > > > - I get these smilint warnings: > > > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row > > `tripRouteTypeEntry' > > > can exceed OID size limit by 6 subidentifier(s) > > > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row > > `tripPeerEntry' can > > > exceed OID size limit by 6 subidentifier(s) > > > SMICng complains about the same. I see > > > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer > > > as the first accessible object int tripRouteTypeEntry. So > > prefix is 11 > > subids > > > index objects are 5 integer-based objects and a var size > > octet string. > > > so we have 5 plus 1 (for lenght) plus number of octets as > > index part. > > > So we have 6 fixed (5 integers plus length value) subids > > plus one for > > every > > > octet in the octet string. So max size for OCTET STRING > should be > > > 111 octets, not 117. > > > Similar calculation for tripPeerEntry seem to tell me max > > lenght can be > > 113 > > > instead of 119. > > > This makes me thin k that it is kind of strange to ha ve > > different size > > for InetAddress, > > > is it not. Another way to solve these concerns is to add > > something to > > the DESCRIPTION > > > clause that states the implementation issues w.r.t. 128 > > subids instad of > > setting > > > arbitray size constrains in the SYNTAX field (that we > > may regret if the > > 128 subid > > > limit ever gets removed). A good example of text for this > > would be in > > > arcEntry in draft-ietf-disman-conditionmib-09.txt or > > sctpAssocLocalAddrEntry in > > > draft-ietf-sigtran-sctp-mib-10.txt > > > - smicng (strict checking) also complains: > > > > I have removed the restriction on the index sizes, and included the > > description > > of the 128 limit. However this will not get rid of the warnings. > > > > > E: f(trip.mi2), (1629,33) Item "applRFC2788Group" > > should be IMPORTed > > > it is not a MUST that you do import it. But as the > > mib-review-guidelines > > state, > > > it would be good to do so to not cause confusion. > > > > I have included the IMPORT > > > > > > From a generic review > > > - Missing reference [BCP0014] > > > > Added reference to this BCP (RFC2119) > > > > > - Ref [RFC2026] probably goes away when this becomes an RFC > > > > I'm leaving this in for now. > > > > > > > > Thanks, > > > Bert > > > > > > > I have also addressed Dan's concern about the copyright year > > and the area > > directors in section 14. > > > > I will submit the new draft (08) if there are no further comments. > > > > Cheers, > > DZ > > > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Wed Aug 27 03:42:37 2003 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 DAA02124 for ; Wed, 27 Aug 2003 03:42:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rtnN-0003VG-7w for iptel-archive@odin.ietf.org; Wed, 27 Aug 2003 02:28:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R6SdLX013465 for iptel-archive@odin.ietf.org; Wed, 27 Aug 2003 02:28:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rrzI-0003gl-Rl for iptel-web-archive@optimus.ietf.org; Wed, 27 Aug 2003 00:32:52 -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 AAA18871 for ; Wed, 27 Aug 2003 00:32:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rrzF-00042V-00 for iptel-web-archive@ietf.org; Wed, 27 Aug 2003 00:32:49 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rrzE-00042R-00 for iptel-web-archive@ietf.org; Wed, 27 Aug 2003 00:32:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmfi-0004j5-LX; Tue, 26 Aug 2003 18:52:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rajd-00064X-Da for iptel@optimus.ietf.org; Tue, 26 Aug 2003 06:07: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 GAA26259 for ; Tue, 26 Aug 2003 06:07:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rajZ-0006lw-00 for iptel@ietf.org; Tue, 26 Aug 2003 06:07:29 -0400 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 19rajZ-0006ls-00 for iptel@ietf.org; Tue, 26 Aug 2003 06:07:29 -0400 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7QA7K1B022925 for ; Tue, 26 Aug 2003 06:07:20 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h7QA7H1B022871 for ; Tue, 26 Aug 2003 06:07:18 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt Message-ID: Thread-Topic: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt Thread-Index: AcNrToP3dukAb1/ATzqKjRV7gxDYOQAVh85g From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "David Zinman" , "list iptel" Cc: "David Zinman" , "Jon Peterson (E-mail)" Content-Transfer-Encoding: quoted-printable 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 26 Aug 2003 13:07:25 +0300 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable The 'MIB Doctor' agrees.=20 Dan > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: 26 August, 2003 12:19 AM > To: 'David Zinman'; Romascanu, Dan (Dan); 'list iptel' > Cc: 'David Zinman'; 'Bert Wijnen (E-mail)'; Jon Peterson (E-mail) > Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt >=20 >=20 > Seems all fine to me now. >=20 > One remaining NIT, can be addressed during RFC-Editing phase=20 > as far as I am > concerned: >=20 > RFC2119 needs to be referenced NORMATIVELY. >=20 > Jon, as far as I am concerned this one is ready for IETF Last=20 > Call and then > IESG Agenda. I assume that the MIB Doctor (Dan Romascanu) agrees. >=20 > Thanks, > Bert=20 >=20 > > -----Original Message----- > > From: Wijnen, Bert (Bert)=20 > > Sent: maandag 11 augustus 2003 20:59 > > To: David Zinman; Wijnen, Bert (Bert); Romascanu, Dan (Dan);=20 > > list iptel > > Cc: David Zinman; Bert Wijnen (E-mail) > > Subject: RE: [Iptel] RE: Comments on=20 > draft-ietf-iptel-trip-mib-07.txt > >=20 > >=20 > > Looks good. > > I understand that the warnings do not go away. > > But they are "warnings", and so we check if the DESCRIPTION > > clause has the proper instructions to implementers, and they now > > do. So it looks good to me. > >=20 > > Thanks, > > Bert=20 > >=20 > > > -----Original Message----- > > > From: David Zinman [mailto:dzinman@rogers.com] > > > Sent: maandag 11 augustus 2003 20:07 > > > To: Wijnen, Bert (Bert); Romascanu, Dan (Dan); list iptel > > > Cc: David Zinman; Bert Wijnen (E-mail) > > > Subject: Re: [Iptel] RE: Comments on=20 > > draft-ietf-iptel-trip-mib-07.txt > > >=20 > > >=20 > > > inline: > > >=20 > > > ----- Original Message -----=20 > > > From: "Wijnen, Bert (Bert)" > > > To: "Romascanu, Dan (Dan)" ; "list iptel" > > > > > > Cc: "David Zinman" ; "Bert Wijnen=20 > > (E-mail)" > > > > > > Sent: Monday, August 11, 2003 9:20 AM > > > Subject: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-07.txt > > >=20 > > >=20 > > > > Thanks Dan for your review. > > > > > > > > I think the copyright-year will be addressed by RFC-Editor=20 > > > when it gets > > > there. > > > > So unless there are othe reasons for a respin, I can live=20 > > > with it for now. > > > > But it seems anew rev may be wise because of my additional=20 > > > comments below > > > > > > > > I wonder why sect 14 is needed. I leave this up to TSV=20 > > > AD(s) on how to > > > deal > > > > with it. > > > > > > >=20 > > > I am leaving section 14 in for now. > > >=20 > > > > From a MIB review perspective I have a few additional comments): > > > > - I think that RFC2788 needs to be added to normative=20 > > > references since > > > > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > > > > - TRIP-TC module does not have a REVISION clause, which we=20 > > > actually DO > > > > want to have. > > >=20 > > > Added both the reference to RFC 2788 and the REVISION clause=20 > > > in TRIP-TC > > >=20 > > > > - I get these smilint warnings: > > > > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row > > > `tripRouteTypeEntry' > > > > can exceed OID size limit by 6 subidentifier(s) > > > > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row > > > `tripPeerEntry' can > > > > exceed OID size limit by 6 subidentifier(s) > > > > SMICng complains about the same. I see > > > > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer > > > > as the first accessible object int tripRouteTypeEntry. So=20 > > > prefix is 11 > > > subids > > > > index objects are 5 integer-based objects and a var size=20 > > > octet string. > > > > so we have 5 plus 1 (for lenght) plus number of octets as=20 > > > index part. > > > > So we have 6 fixed (5 integers plus length value) subids=20 > > > plus one for > > > every > > > > octet in the octet string. So max size for OCTET STRING=20 > > should be > > > > 111 octets, not 117. > > > > Similar calculation for tripPeerEntry seem to tell me max=20 > > > lenght can be > > > 113 > > > > instead of 119. > > > > This makes me thin k that it is kind of strange to ha ve=20 > > > different size > > > for InetAddress, > > > > is it not. Another way to solve these concerns is to add=20 > > > something to > > > the DESCRIPTION > > > > clause that states the implementation issues w.r.t. 128=20 > > > subids instad of > > > setting > > > > arbitray size constrains in the SYNTAX field (that we=20 > > > may regret if the > > > 128 subid > > > > limit ever gets removed). A good example of text for this=20 > > > would be in > > > > arcEntry in draft-ietf-disman-conditionmib-09.txt or > > > sctpAssocLocalAddrEntry in > > > > draft-ietf-sigtran-sctp-mib-10.txt > > > > - smicng (strict checking) also complains: > > >=20 > > > I have removed the restriction on the index sizes, and=20 > included the > > > description > > > of the 128 limit. However this will not get rid of the warnings. > > >=20 > > > > E: f(trip.mi2), (1629,33) Item "applRFC2788Group"=20 > > > should be IMPORTed > > > > it is not a MUST that you do import it. But as the=20 > > > mib-review-guidelines > > > state, > > > > it would be good to do so to not cause confusion. > > >=20 > > > I have included the IMPORT > > > > > > > > From a generic review > > > > - Missing reference [BCP0014] > > >=20 > > > Added reference to this BCP (RFC2119) > > >=20 > > > > - Ref [RFC2026] probably goes away when this becomes an RFC > > >=20 > > > I'm leaving this in for now. > > >=20 > > > > > > > > Thanks, > > > > Bert > > > > > > >=20 > > > I have also addressed Dan's concern about the copyright year=20 > > > and the area > > > directors in section 14. > > >=20 > > > I will submit the new draft (08) if there are no further comments. > > >=20 > > > Cheers, > > > DZ > > >=20 > >=20 >=20 _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Wed Aug 27 09:45:27 2003 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 JAA27018 for ; Wed, 27 Aug 2003 09:45:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s0Pj-0003an-9p for iptel-archive@odin.ietf.org; Wed, 27 Aug 2003 09:32:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7RDWgqo013783 for iptel-archive@odin.ietf.org; Wed, 27 Aug 2003 09:32:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s04t-0002nE-8Z for iptel-web-archive@optimus.ietf.org; Wed, 27 Aug 2003 09:11:11 -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 JAA24291 for ; Wed, 27 Aug 2003 09:11:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19s04r-0005FM-00 for iptel-web-archive@ietf.org; Wed, 27 Aug 2003 09:11:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19s04q-0005FJ-00 for iptel-web-archive@ietf.org; Wed, 27 Aug 2003 09:11:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rzvW-0002KA-D7; Wed, 27 Aug 2003 09:01:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rtmE-0003Lj-RO for iptel@optimus.ietf.org; Wed, 27 Aug 2003 02:27:31 -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 CAA21601 for ; Wed, 27 Aug 2003 02:27:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rtmA-0006au-00 for iptel@ietf.org; Wed, 27 Aug 2003 02:27:26 -0400 Received: from pine.neustar.com ([209.173.57.70]) by ietf-mx with esmtp (Exim 4.12) id 19rtm9-0006aa-00 for iptel@ietf.org; Wed, 27 Aug 2003 02:27:25 -0400 Received: from chiimc01.npac.com ([10.32.90.4]) by pine.neustar.com (8.11.0/8.11.0) with ESMTP id h7R6Qio11694; Wed, 27 Aug 2003 06:26:44 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id ; Wed, 27 Aug 2003 01:29:33 -0500 Message-ID: From: "Peterson, Jon" To: "'Romascanu, Dan (Dan)'" , "Wijnen, Bert (Bert)" , David Zinman , list iptel Cc: David Zinman Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 27 Aug 2003 01:27:15 -0500 Okay, great! IETF Last call will be forthcoming shortly. Jon Peterson NeuStar, Inc. > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Tuesday, August 26, 2003 3:07 AM > To: Wijnen, Bert (Bert); David Zinman; list iptel > Cc: David Zinman; Jon Peterson (E-mail) > Subject: RE: [Iptel] RE: Comments on draft-ietf-iptel-trip-mib-08.txt > > > The 'MIB Doctor' agrees. > > Dan > > > > -----Original Message----- > > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > > Sent: 26 August, 2003 12:19 AM > > To: 'David Zinman'; Romascanu, Dan (Dan); 'list iptel' > > Cc: 'David Zinman'; 'Bert Wijnen (E-mail)'; Jon Peterson (E-mail) > > Subject: RE: [Iptel] RE: Comments on > draft-ietf-iptel-trip-mib-08.txt > > > > > > Seems all fine to me now. > > > > One remaining NIT, can be addressed during RFC-Editing phase > > as far as I am > > concerned: > > > > RFC2119 needs to be referenced NORMATIVELY. > > > > Jon, as far as I am concerned this one is ready for IETF Last > > Call and then > > IESG Agenda. I assume that the MIB Doctor (Dan Romascanu) agrees. > > > > Thanks, > > Bert > > > > > -----Original Message----- > > > From: Wijnen, Bert (Bert) > > > Sent: maandag 11 augustus 2003 20:59 > > > To: David Zinman; Wijnen, Bert (Bert); Romascanu, Dan (Dan); > > > list iptel > > > Cc: David Zinman; Bert Wijnen (E-mail) > > > Subject: RE: [Iptel] RE: Comments on > > draft-ietf-iptel-trip-mib-07.txt > > > > > > > > > Looks good. > > > I understand that the warnings do not go away. > > > But they are "warnings", and so we check if the DESCRIPTION > > > clause has the proper instructions to implementers, and they now > > > do. So it looks good to me. > > > > > > Thanks, > > > Bert > > > > > > > -----Original Message----- > > > > From: David Zinman [mailto:dzinman@rogers.com] > > > > Sent: maandag 11 augustus 2003 20:07 > > > > To: Wijnen, Bert (Bert); Romascanu, Dan (Dan); list iptel > > > > Cc: David Zinman; Bert Wijnen (E-mail) > > > > Subject: Re: [Iptel] RE: Comments on > > > draft-ietf-iptel-trip-mib-07.txt > > > > > > > > > > > > inline: > > > > > > > > ----- Original Message ----- > > > > From: "Wijnen, Bert (Bert)" > > > > To: "Romascanu, Dan (Dan)" ; "list iptel" > > > > > > > > Cc: "David Zinman" ; "Bert Wijnen > > > (E-mail)" > > > > > > > > Sent: Monday, August 11, 2003 9:20 AM > > > > Subject: [Iptel] RE: Comments on > draft-ietf-iptel-trip-mib-07.txt > > > > > > > > > > > > > Thanks Dan for your review. > > > > > > > > > > I think the copyright-year will be addressed by RFC-Editor > > > > when it gets > > > > there. > > > > > So unless there are othe reasons for a respin, I can live > > > > with it for now. > > > > > But it seems anew rev may be wise because of my additional > > > > comments below > > > > > > > > > > I wonder why sect 14 is needed. I leave this up to TSV > > > > AD(s) on how to > > > > deal > > > > > with it. > > > > > > > > > > > > > I am leaving section 14 in for now. > > > > > > > > > From a MIB review perspective I have a few additional > comments): > > > > > - I think that RFC2788 needs to be added to normative > > > > references since > > > > > this doc IMPORTs from the NETWORK-SERVICES-MIB in RFC2788 > > > > > - TRIP-TC module does not have a REVISION clause, which we > > > > actually DO > > > > > want to have. > > > > > > > > Added both the reference to RFC 2788 and the REVISION clause > > > > in TRIP-TC > > > > > > > > > - I get these smilint warnings: > > > > > .\TRIP-MIB:327: [5] {index-exceeds-too-large} index of row > > > > `tripRouteTypeEntry' > > > > > can exceed OID size limit by 6 subidentifier(s) > > > > > .\TRIP-MIB:511: [5] {index-exceeds-too-large} index of row > > > > `tripPeerEntry' can > > > > > exceed OID size limit by 6 subidentifier(s) > > > > > SMICng complains about the same. I see > > > > > 1.3.6.1.2.1.xxxx.1.2.1.6 tripRouteTypePeer > > > > > as the first accessible object int tripRouteTypeEntry. So > > > > prefix is 11 > > > > subids > > > > > index objects are 5 integer-based objects and a var size > > > > octet string. > > > > > so we have 5 plus 1 (for lenght) plus number of octets as > > > > index part. > > > > > So we have 6 fixed (5 integers plus length value) subids > > > > plus one for > > > > every > > > > > octet in the octet string. So max size for OCTET STRING > > > should be > > > > > 111 octets, not 117. > > > > > Similar calculation for tripPeerEntry seem to tell me max > > > > lenght can be > > > > 113 > > > > > instead of 119. > > > > > This makes me thin k that it is kind of strange to ha ve > > > > different size > > > > for InetAddress, > > > > > is it not. Another way to solve these concerns is to add > > > > something to > > > > the DESCRIPTION > > > > > clause that states the implementation issues w.r.t. 128 > > > > subids instad of > > > > setting > > > > > arbitray size constrains in the SYNTAX field (that we > > > > may regret if the > > > > 128 subid > > > > > limit ever gets removed). A good example of text for this > > > > would be in > > > > > arcEntry in draft-ietf-disman-conditionmib-09.txt or > > > > sctpAssocLocalAddrEntry in > > > > > draft-ietf-sigtran-sctp-mib-10.txt > > > > > - smicng (strict checking) also complains: > > > > > > > > I have removed the restriction on the index sizes, and > > included the > > > > description > > > > of the 128 limit. However this will not get rid of the warnings. > > > > > > > > > E: f(trip.mi2), (1629,33) Item "applRFC2788Group" > > > > should be IMPORTed > > > > > it is not a MUST that you do import it. But as the > > > > mib-review-guidelines > > > > state, > > > > > it would be good to do so to not cause confusion. > > > > > > > > I have included the IMPORT > > > > > > > > > > From a generic review > > > > > - Missing reference [BCP0014] > > > > > > > > Added reference to this BCP (RFC2119) > > > > > > > > > - Ref [RFC2026] probably goes away when this becomes an RFC > > > > > > > > I'm leaving this in for now. > > > > > > > > > > > > > > Thanks, > > > > > Bert > > > > > > > > > > > > > I have also addressed Dan's concern about the copyright year > > > > and the area > > > > directors in section 14. > > > > > > > > I will submit the new draft (08) if there are no > further comments. > > > > > > > > Cheers, > > > > DZ > > > > > > > > > > > _______________________________________________ > Iptel mailing list > Iptel@ietf.org > https://www.ietf.org/mailman/listinfo/iptel > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Fri Aug 29 19:32:53 2003 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 TAA18114 for ; Fri, 29 Aug 2003 19:32:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sroX-0007eI-Dq for iptel-archive@odin.ietf.org; Fri, 29 Aug 2003 18:33:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7TMXqnx029392 for iptel-archive@odin.ietf.org; Fri, 29 Aug 2003 18:33:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19spst-0002WJ-Rj for iptel-web-archive@optimus.ietf.org; Fri, 29 Aug 2003 16:30:15 -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 QAA02348 for ; Fri, 29 Aug 2003 16:30:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19spsr-0006MT-00 for iptel-web-archive@ietf.org; Fri, 29 Aug 2003 16:30:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19spsr-0006MQ-00 for iptel-web-archive@ietf.org; Fri, 29 Aug 2003 16:30:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19snvs-0005SA-Rb; Fri, 29 Aug 2003 14:25:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19slEr-0006Mc-T0 for iptel@optimus.ietf.org; Fri, 29 Aug 2003 11:32:37 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03386; Fri, 29 Aug 2003 11:32:30 -0400 (EDT) Message-Id: <200308291532.LAA03386@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-cpl-08.txt,.ps 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 29 Aug 2003 11:32:30 -0400 --NextPart 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 : CPL: A Language for User Control of Internet Telephony Services Author(s) : J. Lennox, X. Wu, H. Schulzrinne Filename : draft-ietf-iptel-cpl-08.txt,.ps Pages : 82 Date : 2003-8-29 The Call Processing Language (CPL) is a language that can be used to describe and control Internet telephony services. It is designed to be implementable on either network servers or user agent servers. It is meant to be simple, extensible, easily edited by graphical clients, and independent of operating system or signalling protocol. It is suitable for running on a server where users may not be allowed to execute arbitrary programs, as it has no variables, loops, or ability to run external programs. This document is a product of the IP Telephony (IPTEL) working group of the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at iptel@lists.research.bell-labs.com and/or the authors. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-08.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-cpl-08.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-cpl-08.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. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-8-29113648.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-cpl-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-cpl-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-8-29113648.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel