[mgmtprotocol] Minutes for F2F November 6-7, 2002

[Hedyalb@aol.com]

please see attached

Title: Untitled Document

OASIS Management Protocol Technical Committee (MPTC)
Meeting Minutes

Logistics
Roll-call
Other Business
Business In Order
Action Items & Motions
References

Logistics

Meeting Date	Nov 6-7, 2002
Meeting Time	November 6th 9am -12noon, 1pm - 5pm MST November 7th 9am -12noon, 1pm-2pm MST
Location	HP, 3404 East Harmony Road, Ft. Collins, 80525 Dial-in Number – 888 808 7889 International: 719 457 0701 Conference ID: 100346
Duration	1 hour
Chair	Winston Bumpus
Recording Secretary	Hedy Alban
Agenda	As published [1]

Roll-call

 

2002			16-Oct	30-Oct	6-7 Nov (F2F)
Alan Davies	AD	SeeBeyond	N	N	N
Anand Akela	AA	HP	N	N	N
Andrea Westerinen	AW	Cisco	Y	N	Y
Andreas Maier	AM	IBM	N	Y	Y
Aravinda Gollapudi	AG	Verisign	N	N	N
Darran Rolls	DR	Waveset	N	N	N
Dennis Ho	DH	Iona	Y	N	N
Dick Spellman	DS	Sun Microsystems Inc.	Y	Y	N
Ellen Stokes	ES	IBM	N	Y	N
Fred Carter	FC	Amber Software	Y	Y	Y
George Arriola	GA	Talking Blocks	resigned	resigned	N
Gil Kirkpatrick	GK	NetPro	N	Y	Y
Guru Bhat	GB	Sun Microsystems Inc.	N	N	N
Heather KrIeger	HK	IBM	Y	Y	Y
Hedy Alban	HED	Max Shevet Consulting	Y	N	N
Homayoun Pourheidari	HP	HP	N	N	Y
Jim Willits	JW	HP	Y	Y	Y
Julie Schott	JS	Cisco	Y	N	Y
Ken Crozier	KC	Cisco	Y	N	N
Karl Schopmeyer	KS2	Independent	Y	N	Y
Krishna Sankar	KS1	Cisco	N	N	N
Michael Thatcher	MT	Microsoft	N	Y	N
Robert Baafi	RB	Iona	N	N	N
Richard Nikula	RN	BMC	Y	Y	Y
Sekhar Saukkai	SS	Corporate Oxygen Inc.	N	N	N
Srinivas Vadhri	SV	CommerceOne	N	N	N
Samiar Vaidya *	SV	Talking Blocks	Y	Y	Y
Veena Subrahmanyam	VS	HP	N	Y	Y
Winston Bumpus	WB	Novell	Y	Y	Y
Yoshimasa Masuoka	YM	Hitachi	N	Y	Y
New Members
Kevin Brinkley	KB	Intel	N	N	N
Jim Davis	JD	Sun	N	N	N
Bart Whitely	BW	Caldera International	N	N	N
George Erricson	GE	EMC	N	N	N
Ravi Fernando	RS	HP	N	N	N
Igor Sedukhin	IS		N	N	N
Bill Dunigan	BD	Cyclone Commerce	N	N	N
Jeff Boulin		WebMethods	N	N	N
Takaki Kuroda	TK	Hitachi	N	N	N
Ken Fife	KF	Defense Information Systems Agency (DISA)	Y	Y	N
Ben Bloch	BB	Inteq	Y	N	Y
Dimdira Dcherevik	DD	CA	N	Y	N
* replacing George Arriola

 

Other Business

WB

None

Business In Order

11/6	Review Agenda for this meeting
	Agenda reviewed.
11/6		Review and Approve Minutes of Oct 30
		Approved as posted
11/6		Review Membership Levels
		TC authorized Winston to send a warning e-mail to members who have missed four or more meetings: Alan Davies, Anand, Darren, Avarinda, Krishna (Cisco) Robert Boffi, and Srinivas.
		Samir has attended three consecutive meetings to become a voting member.
		Other non-voters will continue on probation until they attend three consecutive meetings, at which point they will become voting members.

 

11/6	OASIS Security Joint Committee Participation (SJC)
	TC would like to find a member with security background to participate in the SJC. Winston will discuss with Krishna or Aravinda. Alternatively, Winston will recruit someone from the SJC to talk to us. Worst case, Winston will be liaison with SJC.

 

11/6	Review Requirements Document
	Karl led a review of existing requirements.
	Regarding the requirement for data model agnosticity, the TC compared several different protocol strategies, as follows:   Payload agnostic strategies Standard set of ops Native wrapped Native format (uppercase binding)   Data interoperability strategies Pick 1 existing model Create new one true model (DOA)   Pros/cons 1 Pro – Easy 1st step Pro – Enables more consumers Pro – Discovery, security Con – No data interoperability Con – Need new marshaller Con – Need new demarshaller Con – Extensibility of operations/protocols Con – consumer has to understand all of underlying service Con – No ability to determine compliance   Pros/cons 2 Pro – Extensibility of operations/protocols Pro – Ability to determine compliance Pro – Discovery, security Pro – Easy 1st step Pro – Enables more consumers Con – consumer has to understand all of underlying service Con – No data interoperability Con – Need new marshaller Con – Need new demarshaller   Pros/cons 3 Pro – Extensibility of operations/protocols Pro – Ability to determine compliance Pro - Discovery Pro – Easy 1st step Con – No data interoperability Con – consumer has to understand all of underlying service Con – no security N/A – Need new marshaller N/A – Need new demarshaller N/A – Enables more consumers   Pros/cons 4 Pro – data interoperability Pro – Discovery/Security Pro – Extensibility of data and methods Pro – Compliance Pro – enables consumers and clients Pro – reuse of CIM infrastructure Con – Extensibility of operations Con – need to map all existing models to CIM Con – Existing clients need to support this before its useful   Pros/cons 5 (DOA) Pro – data interoperability Pro – Discovery/Security Pro – Extensibility of data and methods Pro – Compliance Pro – enables consumers and clients Pro – reuse of CIM infrastructure Con – Extensibility of operations Con – need to map all existing models to CIM Con – Existing clients need to support this before its useful Con – no existing implementations Con – workgroup intensive Con – duplicate implementation

 

 

11/6	Discuss proposed Use Cases
	Richard presented seven use cases for the management protocol:   1.                Management application uses the management protocol to access managed objects via a single management server   2.                Management application uses the management protocol to access managed objects via multiple management servers of the same type, each managing a unique set of managed objects.   3.                Management application uses the management protocol to access managed objects via multiple management servers of the same type, where some or all of the managed objects exist in multiple servers. Management application uses the management protocol to access managed objects via multiple management servers of the different types, each managing a unique set of managed objects. Management application uses the management protocol to access managed objects via multiple management servers of the different types, where some or all of the managed objects exist in multiple servers. The management protocol is integrated in the object by the object provider. The management application (vendor or end user provided) directly interacts with the objects, e.g. SNMP. M management application uses the management protocol to access a management server that is managing other management servers
11/6	WSDL Tutorial
	Heather reviewed contents of WSDL 1.2, including updates to W3C architecture to accommodate management.

 

 

11/6	Protocol Proposals
	Discussion of where do we want to end up, what function(s) should this TC perform.
11/7	Protocol Proposals (cont)
	Heather presented a proposal. TC discussed this proposal. Discussion included assessment of how Heather’s proposal meets the requirements.
	TC members are invited to build example WSDL 1.2 port types to gain perspective on implementability using the operating system class (from system 27 preliminary)
	Re-draw the diagram in PowerPoint
11/7	Future meetings
	Plan for F2F week of Jan 13 or Jan 20 in the Bay Area
	Telecons will be held at 7AM PST on the following dates: Nov 20, Dec 4, Dec 11, Dec 18, Jan 8
11/7	Motion to Adjourn
	Meeting adjourned at 1:30 PM to reconvene on Nov 20 at 7AM PST.

 

Action Items & Motions

	Owner	Action Item/Motion
	All	TC members are invited to build example WSDL 1.2 port types to gain perspective on implementability of Heather’s suggestion using the OS class (from system 27 preliminary)
		Re-draw the diagram in PowerPoint
	Winston	Find liaison for the Security Joint Committee

 

References

[1] published agenda URL