RE: Real Notification Requirements

["McDonald, Ira" <imcdonald@sharplabs.com>]

Hi,

All of which was supposed to be an answer to an off-list
question of Shane's - sorry about that.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

> -----Original Message-----
> From: McDonald, Ira 
> Sent: Tuesday, March 28, 2006 1:19 PM
> To: 'shane_kerr@isc.org'; Andy Bierman
> Cc: Netconf (E-mail)
> Subject: RE: Real Notification Requirements
> 
> 
> Hi Shane,
> 
> A partial, informal list of current, widely-deployed network
> element configuration protocols:
> 
> - IETF SNMP over TCP, UDP, ISO TP4, NetWare, AppleTalk, etc.
> - ISO CMIP over TCP, ISO TP4, etc.
> - DMTF DMI over TCP - DMI MIFs for IETF and vendor MIBs
> - DMTF WBEM over HTTP - XML schema for DMTF CIM MOFs
> - Oasis WSDM over SOAP - XML schema for WS-Resource* framework
> - DMTF WS-Management over SOAP - XML schema for WS-Resource*
> 
> DMTF and Oasis have a formal alliance to convert all CIM XML
> schema into the WS-Resource* framework for use with WSDM.
> 
> WSDM and WS-Management have just issued a historic convergence
> white paper that shows how they'll add new higher level classes
> to allow a single application data model and harmonize the
> resource, transfer, notifications, and subscriptions elements:
> 
>   
> http://www-128.ibm.com/developerworks/webservices/library/spec
ification/ws-roadmap/ 
> 
>   http://devresource.hp.com/drc/specifications/wsm/index.jsp
> 
> Cheers,
> - Ira
> 
> Ira McDonald (Musician / Software Architect)
> Blue Roof Music / High North Inc
> PO Box 221  Grand Marais, MI  49839
> phone: +1-906-494-2434
> email: imcdonald@sharplabs.com
> 
> > -----Original Message-----
> > From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org]On
> > Behalf Of Shane Kerr
> > Sent: Tuesday, March 28, 2006 10:02 AM
> > To: Andy Bierman
> > Cc: Netconf (E-mail)
> > Subject: Re: Real Notification Requirements
> > 
> > 
> > Andy Bierman wrote:
> > > Hi,
> > > 
> > > This new thread is for people to articulate use cases
> > > to support functional requirement requests.
> > > Translation: What is the developer or operator doing now, and
> > > how will it change to something great and wonderful because
> > > of this new feature?
> > > 
> > > Let's try some top-down design, since ad-hoc design isn't
> > > going so well.
> > > 
> > > I believe there is consensus so far for 2 uses of notifications
> > > in the NETCONF protocol:
> > > 
> > > 
> > > Content Layer Requirements
> > > --------------------------
> > > 
> > > C1) 'Full XML' or 'XML Wrapper' notification for SYSLOG content
> > > 
> > > C2) NETCONF configuration change notification
> > > 
> > > C3) ???
> > 
> > I had a quick look at draft-ietf-syslog-protocol-16, and was 
> > interested
> > to see it supports structured data in addition to traditional syslog
> > free-form text. It also has a way for vendors to specify their own
> > structured data identifiers, and several standard ones 
> > defined already.
> > 
> > I wonder what the key differences are between the SYSLOG stuff and
> > anything within the NETCONF notification. Perhaps:
> > 
> > - XML (of course)
> > - Registration vs. complete log feed
> > 
> > Is there anything else?
> > 
> > Perhaps it would be better to focus on adding a 
> subscription mechanism
> > to SYSLOG?
> > 
> > --
> > Shane
> > 
> > --
> > to unsubscribe send a message to netconf-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://ops.ietf.org/lists/netconf/>
> > 
> > -- 
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.385 / Virus Database: 268.3.2/294 - Release 
> > Date: 3/27/2006
> >  
> > 
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.2/294 - Release 
> Date: 3/27/2006
>  
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.2/294 - Release Date: 3/27/2006
 

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>