[Sipping] RAQMON I-Ds Last Call
Henry Sinnreich <Henry.Sinnreich@mci.com> Tue, 09 November 2004 04:01 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22151 for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 23:01:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRNCo-0007RA-FK for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 23:02:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRN9u-0003gY-Sg; Mon, 08 Nov 2004 22:59:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRN5v-00032T-I3; Mon, 08 Nov 2004 22:54:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21682; Mon, 8 Nov 2004 22:54:56 -0500 (EST)
Received: from omzesmtp01.mci.com ([199.249.17.7]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRN6X-0007Jl-Lb; Mon, 08 Nov 2004 22:55:41 -0500
Received: from pmismtp04.wcomnet.com ([166.38.62.39]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I6W0095H86MVH@firewall.mci.com>; Tue, 09 Nov 2004 03:54:22 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6W00I0186LW5@pmismtp04.mcilink.com>; Tue, 09 Nov 2004 03:54:22 +0000 (GMT)
Received: from ThinkpadT40 ([131.146.54.147]) by pmismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6W00H6Z86G7T@pmismtp04.mcilink.com>; Tue, 09 Nov 2004 03:54:21 +0000 (GMT)
Date: Mon, 08 Nov 2004 21:54:16 -0600
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
To: rmonmib@ietf.org, sipping@ietf.org
Message-id: <0I6W00H7486K7T@pmismtp04.mcilink.com>
Organization: MCI
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcTGDgjgtoMfXMtvRNuLCfFqS38YBg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: "'Johnston, Alan'" <Alan.Johnston@mci.com>, 'Alan Clark' <alan.d.clark@telchemy.com>, 'Amy Pendleton' <aspen@nortelnetworks.com>
Subject: [Sipping] RAQMON I-Ds Last Call
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Three excellent I-Ds for RAQMON are on last call in the RMONMIB WG: http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon- framework-07.txt http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon- pdu-07.txt http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon- mib-05.txt This is very thorough work and should be made available to the Internet community as INFORMATIVE RFCs IMHO. The reason why informative ONLY is recommended is that application specific reporting, such as for VoIP, IM or SMS messaging, etc. may be application targeted and service providers or IT managers should not be mandated to use this SNMP based approach, where other techniques are preferable. The specific approach should be the choice of the service provider, IT group and the application vendor, for example a desktop office suite enabled with real time communications or IM and presence SLA may not need SNMP. An example of a VoIP targeted approach is http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-summary-04.t xt This proposal is based on the experience of deploying and monitoring large numbers of personal IP telephony devices, such as SIP phones and PC soft phones. Other approaches may emerge as well. How do we monitor all the communication enabled applications on the PC for example, now that every application, for example in Microsoft Office (Word, PowerPoint, Outlook, Access are SIP/SIMPLE enabled, besides the Windows Messenger and Conferencing/Collaboration, etc.)? In summary, the RAQMON I-Ds are ready for last call, but should NOT be the only mandated approach. I suggest some additional wording to be added to make this point clear. I have copied here the co-authors of the proposal for the RTCP Summary in case the issue of normative vs. informative RAQMON RFCs needs to be discussed on the list. Thanks, Henry Henry Sinnreich MCI 1201 E. Arapaho Rd./Office 1020 Richardson, Texas 75081 USA _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] RAQMON I-Ds Last Call Henry Sinnreich
- RE: [Sipping] RAQMON I-Ds Last Call Romascanu, Dan (Dan)
- RE: [Sipping] RAQMON I-Ds Last Call Henry Sinnreich