Re: [nmrg] another possible subject for the nmrg workshop on voip management
Cullen Jennings <fluffy@cisco.com> Wed, 02 March 2005 18:16 UTC
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by agitator.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j22IGA5j003747 for <nmrg@ibr.cs.tu-bs.de>; Wed, 2 Mar 2005 19:16:16 +0100
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-4.cisco.com with ESMTP; 02 Mar 2005 10:17:36 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j22IGDYO004986; Wed, 2 Mar 2005 10:16:13 -0800 (PST)
Received: from [127.0.0.1] ([171.68.225.134]) by vtg-um-e2k4.sj21ad.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 2 Mar 2005 10:16:12 -0800
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Wed, 02 Mar 2005 10:16:08 -0800
Subject: Re: [nmrg] another possible subject for the nmrg workshop on voip management
From: Cullen Jennings <fluffy@cisco.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Margaret Wasserman <margaret@thingmagic.com>, henry@sinnreich.net, j.schoenwaelder@iu-bremen.de, alan.d.clark@telchemy.com, klingle@cisco.com, jf.mule@cablelabs.com
Message-ID: <BE4B42E8.2B9FF%fluffy@cisco.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F07F67A4D@IS0004AVEXU1.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2005 18:16:12.0786 (UTC) FILETIME=[EA8E2D20:01C51F53]
X-IBRFilter-SpamReport: 0 ()
X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang)
X-Mailman-Approved-At: Thu, 03 Mar 2005 17:48:03 +0100
Cc: nmrg@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <http://www.ibr.cs.tu-bs.de/pipermail/nmrg>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2005 18:16:18 -0000
On 3/2/05 3:02 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wrote: >> >> I hope to see folks weighing on the debate of xcon vs. xcap >> since a draft >> was just submitted on that issue. Lisa D has tried to start >> discussions on >> this before and not many people have helped provide input on what IETF >> should do. >> >> The comparison of XCON to NETCONF or WebDAV leaves me totally >> confused. XCON >> is about conferencing. >> > > I apologize for not being clear, but that was just one bullet trying to say > too much. By looking at the requirements described > http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-xcon-cpcp-reqs-04 > .txt I cannot help wondering if inventing a new protocol is really necessary. No problem - yes I think there are some good points, with this draft in particular xcon may move to discarding cpcp all together. Still unclear but discussions are starting and could use the help of a network management perspective and experience. > I know discussions are happening, and I believe they are a good start, but > maybe we need to go further. At the end of the day operators will need to > manage IP networks, running SIP, and conferencing, and many other. Do we need > to invent a different protocol for configuration of each one of the layers and > applications? Do we need to invent a different protocol - probably not depending on what you define as the scope. But if we asked the questions slightly different, do we need to invent something other than SNMP, well I think the current deployment results more or less speak for themselves. I don't know why people choose not to do SNMP, but it seems like something worth figuring out and addressing. Cullen
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- RE: [nmrg] another possible subject for the nmrg … Alan Clark
- RE: [nmrg] another possible subject for the nmrg … henry
- Re: [nmrg] another possible subject for the nmrg … Juergen Schoenwaelder
- RE: [nmrg] another possible subject for the nmrg … Jean-Francois Mule
- RE: [nmrg] another possible subject for the nmrg … henry
- Re: [nmrg] another possible subject for the nmrg … Juergen Schoenwaelder
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- Re: [nmrg] another possible subject for the nmrg … Juergen Schoenwaelder
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- Re: [nmrg] another possible subject for the nmrg … Juergen Schoenwaelder
- RE: [nmrg] another possible subject for the nmrg … henry
- Re: [nmrg] another possible subject for the nmrg … Margaret Wasserman
- [nmrg] another possible subject for the nmrg work… Romascanu, Dan (Dan)
- Re: [nmrg] another possible subject for the nmrg … Cullen Jennings
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- Re: [nmrg] another possible subject for the nmrg … Cullen Jennings
- Re: [nmrg] another possible subject for the nmrg … Cullen Jennings
- RE: [nmrg] another possible subject for the nmrg … henry
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- RE: [nmrg] another possible subject for the nmrg … Romascanu, Dan (Dan)
- Re: [nmrg] another possible subject for the nmrg … Cullen Jennings
- Re: [nmrg] another possible subject for the nmrg … Cullen Jennings