RE: What about the OAM in OAM&P

["Hare, Michael" <Michael.Hare@us.fujitsu.com>]

OK, I wasn't sure :)

I basically go with:
Maintenance : Alarms, Alarm Config, Loopbacks, test signals, SW upgrades
Operations: System Turnup, 
Administrative: Billing, SLAs,

But your point is well taken. I don't think the silos are that well defined.

- m

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Wednesday, July 05, 2006 11:41 AM
To: Hare, Michael; Netconf Mailing List (E-mail)
Subject: RE: What about the OAM in OAM&P


Well, that much I figured out as well, but I was hoping for some
definitions :-)

IMO we need to make a distinction between applications or services and
management operations. It looks to me that MAN, OP and ADM do not refer
strictly to a well (?) defined class of management operations as CONF
does. 

Dan

BTW - you mentioned Test Signals - are you on the ntdp list? 

 
 

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Hare, Michael
> Sent: Wednesday, July 05, 2006 7:28 PM
> To: Netconf Mailing List (E-mail)
> Subject: RE: What about the OAM in OAM&P
> 
> MAN : Maintenance
> OP : Operations
> ADM : Administrative
> 
> Some of this, like alarms and alarm config are covered by Netconf.
> Others like SW upgrades and Test Signals is not.
> 
> - m
> 
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Wednesday, July 05, 2006 11:13 AM
> To: Hare, Michael; Netconf Mailing List (E-mail)
> Subject: RE: What about the OAM in OAM&P
> 
> 
> Michael,
> 
> Can you define MAN, OP and ADM? 
> 
> Thanks,
> 
> Dan
> 
> 
>  
>  
> 
> > -----Original Message-----
> > From: owner-netconf@ops.ietf.org
> > [mailto:owner-netconf@ops.ietf.org] On Behalf Of Hare, Michael
> > Sent: Wednesday, July 05, 2006 6:15 PM
> > To: Netconf Mailing List (E-mail)
> > Subject: RE: What about the OAM in OAM&P
> > 
> > 
> > Maybe there's a need for other WGs to define NETMAN, NETOP 
> and NETADM 
> > to cover the rest. Not your problem, I understand, but I have to 
> > convience the folks here that things like software 
> upgrades, loopbacks 
> > and such are not part of NETCONF. We will need to write proprietary 
> > RPCs for all that.
> > 
> > Thanks,
> 
> --
> 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/>
> 

--
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/>