
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g4UHuDqN027980; Thu, 30 May 2002 19:56:14 +0200
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g4UHuBD17347; Thu, 30 May 2002 13:56:11 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <K0NDSXLL>; Thu, 30 May 2002 19:56:10 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E083B1A@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: eos@ops.ietf.org, "Nmrg (E-mail)" <nmrg@ibr.cs.tu-bs.de>
Date: Thu, 30 May 2002 19:56:08 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [nmrg] draft-irtf-nmrg-snmp-tcp-09.txt approved
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
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: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

The IESG has today approved this document to be published
as Experimental RFC. Official announcement will follow.

Thanks to Juergen, to the NMRG and to the EOS WG

Bert 


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g4NFMdVV019871; Thu, 23 May 2002 17:22:39 +0200
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g4NFMd315059; Thu, 23 May 2002 17:22:39 +0200
Date: Thu, 23 May 2002 17:22:39 +0200
Message-Id: <200205231522.g4NFMd315059@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: internet-drafts@ietf.org
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] please post draft-irtf-nmrg-snmp-tcp-09.txt
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
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: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Please post the following document as Internet Draft:

<http://www.ibr.cs.tu-bs.de/~schoenw/draft-irtf-nmrg-snmp-tcp-09.txt>

This ID updates a document already submitted for publication as
Experimental RFC due to feedback from IESG members.

Thanks,

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>




Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g4LE6PtN025218 for <nmrg@ibr.cs.tu-bs.de>; Tue, 21 May 2002 16:06:25 +0200
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g4LE6Nj03247 for <nmrg@ibr.cs.tu-bs.de>; Tue, 21 May 2002 10:06:23 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <K0NDMB85>; Tue, 21 May 2002 16:06:22 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0DECAE09@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Nmrg (E-mail)" <nmrg@ibr.cs.tu-bs.de>
Date: Tue, 21 May 2002 16:06:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [nmrg] FW: web services article
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
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: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Since we discussed this at our last NMRG meeting, 
here is an article that showed up today

Bert 

-----Original Message-----
This story appeared on Network World Fusion at
http://www.nwfusion.com/columnists/2002/0520kaplan.html


Hold off on Web services
By Jeff Kaplan
Network World, 05/20/02

One of the few hot technologies in our industry today is Web services. Unfortunately, making the promise of Web services a reality will be much harder than anyone is willing to admit. 

The premise of Web services is that applications should be made available to organizations as services rather than stand-alone software. The value proposition of Web services is that it would be easier to distribute application functionality across organizations if they used a common language or protocol. Making it easier to share applications makes it easier to conduct business across organizations.

The first problem with Web services is the term itself. In today's world, Web services are more likely to be sets of products than sets of services. Initial Web services implementations let companies wrap specific applications in industry-standard protocols so they can be delivered via the Web, but not in an easily automated fashion.

While the idea of establishing a common language or protocol to facilitate industrywide communications is not new or unreasonable, it represents another problem with Web services. The broader adoption of Web services depends on a new set of industry standards and products that are not going to happen overnight. With a number of megaplayers each determined to support its own flavor of Web services, and upstarts unveiling products ahead of full standards approval, finding truly standard technologies to support Web services is risky.

The third indication that the Web services market is not what it seems is that analysts, hardware and software vendors, and specialized service providers are talking about its virtues more than enterprise users and venture capitalists are. When double-digit analyst forecasts and exaggerated vendor promises outnumber customer testimonials and venture capital commitments, it's a sign of a technology still looking for a market.

The reality of the Web services market for the foreseeable future is that early adopters are more likely to use a set of products than to leverage a set of integrated services. This means they are also more likely to spend more time, money and resources developing and deploying their initial Web service implementations than they anticipated. And given the embryonic nature of Web services, there will be few consultants or systems integrators with expertise to turn to for help. 

Before adopting Web services, ask yourself the following questions. First, what is the business issue you are trying to solve and can today's Web services products satisfy your business objectives? Second, how can you isolate your initial Web services deployment to test their effectiveness without jeopardizing your ongoing operations? Third, when do your business partners plan to adopt Web services?

In other words, wait until there are real standards, products and services before you make any significant investment in Web services.

All contents copyright 1995-2002 Network World, Inc. http://www.nwfusion.com 

Bert 


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g46EOk6h017590; Mon, 6 May 2002 16:24:46 +0200
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g46EOk820597; Mon, 6 May 2002 16:24:46 +0200
Date: Mon, 6 May 2002 16:24:46 +0200
Message-Id: <200205061424.g46EOk820597@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] 10th nmrg meeting minutes
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
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: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

The minutes of the 10th NMRG meeting are now accessible via the
NMRG web page at <http://www.ibr.cs.tu-bs.de/projects/nmrg/>.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>



