RE: [ipfix-req] does raqmon-pdu compete with ipfix?

"Carter Bullard" <carter@qosient.com> Thu, 16 January 2003 19:00 UTC

Received: from mil.doit.wisc.edu (mil.doit.wisc.edu [128.104.31.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20750 for <ipfix-archive@lists.ietf.org>; Thu, 16 Jan 2003 14:00:10 -0500 (EST)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 18ZF9j-0002dK-00 for ipfix-list@mil.doit.wisc.edu; Thu, 16 Jan 2003 12:54:23 -0600
Received: from pool-151-202-13-76.ny5030.east.verizon.net ([151.202.13.76] helo=newyork.qosient.com) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 18ZF9i-0002dC-00 for ipfix-req@net.doit.wisc.edu; Thu, 16 Jan 2003 12:54:22 -0600
Received: from sphynx (sphynx [192.168.0.64]) by newyork.qosient.com (8.11.6/8.11.0) with ESMTP id h0GIsLO09864; Thu, 16 Jan 2003 13:54:21 -0500
From: Carter Bullard <carter@qosient.com>
To: "'MEYER,JEFFREY D (HP-Cupertino,ex1)'" <jeff.meyer2@hp.com>, ipfix-req@net.doit.wisc.edu
Subject: RE: [ipfix-req] does raqmon-pdu compete with ipfix?
Date: Thu, 16 Jan 2003 13:54:12 -0500
Message-ID: <5C8959A16A71B449AE793CF52FBBED6607A50E@ptah.newyork.qosient.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <5C8959A16A71B449AE793CF52FBBED660FC136@ptah.newyork.qosient.com>
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
Content-Transfer-Encoding: 7bit

Hey Jeff,
   The question was to the whole IPFIX group, of
course with the intention of trying to motivate
someone to point it out to an AD, who is suppose
to be paying attention to what's going on in 
their family of WG's to prevent duplicate efforts.

   Because RAQMON-PDU is in the RMON charter, 
its not just a, "here's an interesting draft,
why not come on over to IPFIX and lets work
together" kind of problem.  If, of course,
anyone ever recognizes it as a problem.  IMHO
this is definitely IPFIX killer technology.

   What I find interesting is that RAMON-PDU
transport has no congestion awareness.
   
Carter

   

> -----Original Message-----
> From: MEYER,JEFFREY D (HP-Cupertino,ex1) [mailto:jeff.meyer2@hp.com] 
> Sent: Thursday, January 16, 2003 1:12 PM
> To: 'carter@qosient.com'; ipfix-req@net.doit.wisc.edu
> Subject: RE: [ipfix-req] does raqmon-pdu compete with ipfix?
> 
> 
> Carter,
> 
>   From the synopsis, it certainly sounds like Raqmon could
> simply use IPFIX.  However, who is your question directed to?
> 
>   Have you had any dialog w/ A. Siddiqui et al.?
> 
> Regards,
> 
>   Jeff Meyer
> 
> > -----Original Message-----
> > From: Carter Bullard [mailto:carter@qosient.com]
> > Sent: Thursday, January 16, 2003 5:51 AM
> > To: ipfix-req@net.doit.wisc.edu
> > Subject: [ipfix-req] does raqmon-pdu compete with ipfix?
> > 
> > 
> > Gentle People,
> >    I believe that raqmon-pdu is indeed a direct
> > competitor to IPFIX.  Why not realize that raqmon
> > is a form of flow data and have it use IPFIX?
> > 
> > Carter
> > 
> > 
> > -----Original Message-----
> > From: rmonmib-admin@ietf.org 
> [mailto:rmonmib-admin@ietf.org] On Behalf
> > Of Internet-Drafts@ietf.org
> > Sent: Thursday, January 16, 2003 8:08 AM
> > To: IETF-Announce:
> > Cc: rmonmib@ietf.org
> > Subject: [RMONMIB] I-D ACTION:draft-ietf-rmonmib-raqmon-pdu-00.txt
> > 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This draft is a work item of the Remote Network 
> > Monitoring
> > Working Group of the IETF.
> > 
> > 	Title		: Real-time Application Quality of Service
> > Monitoring 
> >                          (RAQMON) Protocol Data Unit (PDU)
> > 	Author(s)	: A. Siddiqui et al.
> > 	Filename	: draft-ietf-rmonmib-raqmon-pdu-00.txt
> > 	Pages		: 26
> > 	Date		: 2003-1-15
> > 	
> > This memo defines a common protocol data unit (PDU) used 
> > between RAQMON
> > Data Source (RDS) and RAQMON Report Collector (RRC) to report a QOS
> > statistics using RTCP and SNMP as Transport Protocol. The original
> > RAQMON draft [SIDDIQUI3] was split into 3 parts to identify 
> the RAQMON
> > Framework, RAQMON QOS PDU and RAQMON MIB. This memo defined 
> RAQMON QOS
> > Protocol Data Unit (PDU). This memo also outlines mechanisms 
> > to use Real
> > Time Transport Control Protocol
> > (RTCP) and Simple Network Management Protocol (SNMP) to 
> > transport these
> > PDUs between RAQMON Data Source (RDS) and RAQMON Report 
> > Collector (RRC)
> > as outlined in RAQMON Charter of the RMON Workgroup. The memo
> > [SIDDIQUI2] defines a Real-Time Application QOS Monitoring
> > (RAQMON) Framework that extends the RMON Framework to allow 
> Real-time
> > Application QoS information as outlined by RAQMON Charter 
> of the RMON
> > Workgroup. The memo [SIDDIQUI1] defines a portion of the Management
> > Information Base (MIB) for use with network management 
> > protocols in the
> > Internet community. The document proposes an extension to the Remote
> > Monitoring MIB [RFC2819] to accommodate RAQMON solution. 
> > Distribution of
> > this memo is unlimited.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-
> pdu-00.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-rmonmib-raqmon-pdu-00.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-rmonmib-raqmon-pdu-00.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.
> 



--
Help        mailto:majordomo@net.doit.wisc.edu and say "help" in message body
Unsubscribe mailto:majordomo@net.doit.wisc.edu and say
"unsubscribe ipfix" in message body
Archive     http://ipfix.doit.wisc.edu/archive/