[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS TC Call For Participation: OASIS DCML Network TC
A new OASIS technical committee is being formed. The OASIS DCML Network (DCML-Network) TC has been proposed by the following members of OASIS: Dave Roberts, Inkra Networks; Darrel Thomas, EDS; Tim Howes, Phillip Liu, and Ray Suorsa, Opsware; Ajay Gummadi, Rendition Networks; David G. Schrodel, Voyence; Raymond Cadden, Computer Associates; Jim Ritchings, F5; and Noam Fraenkel, Mercury. The proposal for a new TC meets the requirements of the OASIS TC Process (see http://oasis-open.org/committees/process.shtml), and is appended to this message. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's charter. The TC Process allows these items to be clarified (revised); such clarifications (revisions), as well as submissions of technology for consideration by the TC and the beginning of technical discussions may occur no sooner than the TC's first meeting. As specified by the OASIS TC Process, the requirements for becoming a member of the TC at the first meeting are that you must 1) be an employee of an OASIS member organization or an Individual member of OASIS; 2) notify the TC chair of your intent to participate at least 15 days prior to the first meeting; and 3) attend the first meeting of the TC. For OASIS members, to register for the TC using the OASIS collaborative tools, go to the TC's public web page at http://www.oasis-open.org/committees/dcml-network and click on the button for "Join This TC" at the top of the page. You may add yourself to the roster of the TC either as a Prospective Member (if you intend to become a member of the TC) or an Observer. A notice will automatically be sent to the TC chair, which fulfills requirement #2 above. OASIS members may also join the TC after the first meeting. Note that membership in OASIS TCs is by individual, and not by organization. Non-OASIS members may read the TC's mail list archive, view the TC's web page, and send comments to the TC using a web form available on the TC's web page; click the "Send A Comment" button. The archives of the TC's mail list and public comments are visible at http://lists.oasis-open.org/archives/ Further information about the topic of this TC may be found on the Cover Pages under the title "Standards for Automated Resource Management in the Computing Environment" at http://xml.coverpages.org/computingResourceManagement.html (Please feel free to forward this announcement to any other applicable lists.) -Karl ================================================================= Karl F. Best Vice President, OASIS office +1 978.667.5115 x206 mobile +1 978.761.1648 karl.best@oasis-open.org http://www.oasis-open.org Name of the TC OASIS DCML Network Technical Committee (DCML-Network TC) Statement of Purpose The Data Center Markup Language (DCML) is an XML-based specification for representing the contents of data centers and information used in managing those contents. The overall goal of the OASIS DCML TCs is to support the development of a holistic set of standards related to the automated management of data center infrastructure. This TC is part of the OASIS DCML Member Section. The purpose of the OASIS DCML Network TC is to design a data model and XML-based format for the exchange of information about networking elements in a data center. The OASIS DCML Network TC builds on and supports the DCML Framework specification produced by the OASIS DCML Framework TC while focusing on the specifics of network equipment and technology. Scope of the TC The OASIS DCML Network TC will develop the DCML data model and format based on the approach, concepts, and structures defined by the OASIS DCML Framework TC. The scope of the Network TC is large, covering all types of networking components. In the past, the definition of networking components was more straightforward; today, it ranges from “simple” switching and routing elements to nodes providing advanced processing at all layers of the protocol stack. Further, the distinction between networking and compute elements blurs when one considers either common appliances, which are often built from standard server-like components and software, or software that may run on a standard server platform (routing or firewall software, for instance). In spite of the fuzzy definition of “network component,” the following are specifically in scope. * Connectivity and cabling * Layer 2 MAC bridging and switching * Layer 2 VLANs * Layer 3 switching and routing * Firewalls * Intrusion detection systems * IPSec Virtual Private Networks (VPNs) * Load balancing and traffic management * SSL VPNs * SSL Acceleration * Other appliances providing specific application security or performance services, delivered at the network layer. Note that this item has the most opportunity to create confusion since such appliances are often built from standard server CPU designs and may be based on embedded versions of standard operating systems (Linux or FreeBSD, for instance). The general distinction here is that such platforms are “single purpose” and are not designed to run general applications software added to the system at a later date, even if the subcomponents are similar to general purpose technology. It is anticipated that the elements addressed by the DCML Network specification will exclude items addressed by the OASIS DCML Applications & Services TC, including: * General purpose servers running standard operating systems and applications related to application-level processing. However, the TC may elect to address some or all of those elements in consultation with the OASIS DCML Applications & Services TC if it facilitates unification of the model. List of Deliverables The OASIS DCML Network TC will produce the following deliverables: * DCML Network Use Cases: January 2005 * DCML Network Switching Specification: 1H05 * DCML Network Routing Specification: 1H05 * DCML Network Security Specification: 2H05 * DCML Network Performance Management Specification: 2H05 Audience The OASIS DCML Network TC output will be used by roughly the same groups of people using other DCML specifications, including: * Vendors of management toolsets building products to automate or manage data center infrastructure * Vendors of networking infrastructure building products that can be managed and automated by tools implementing DCML * End-users building custom DCML-compatible tools or inspecting the DCML-related interactions between * Future TCs working on additional network-related work items beyond the scope given above * End-users and vendors seeking to create bilaterally agreed upon DCML extensions * The general public with an interest in learning more about DCML Language The TC will conduct its business in English. ===== Non-charter information for the purpose of launching the TC: Related Work The TC will leverage standards developed by other organizations where appropriate for the DCML Network specification. The OASIS DCML Network TC will actively seek to collaborate with other groups doing complementary work, both inside and outside of OASIS, which may include the following: * OASIS DCML Framework TC * OASIS WSDM TC * DMTF Common Information Model * GGF OGSA * IETF SNMP Anticipated Contributions of Existing Work The proposers intend that the OASIS DCML Network TC use as its starting point some preliminary work developed by the DCML Organization. This includes a set of basic DCML network use cases. First Meeting The first meeting of the TC will be a teleconference meeting hosted by the OASIS DCML Member Section on 15 November 2004 at 12:00 noon Pacific. On-going Meeting Schedule The proposers anticipate that the TC will meet face to face at least quarterly, with at least monthly teleconference meetings in between. The TC will also conduct technical discussions via email. Proposers Dave Roberts <dave@inkra.com> of Inkra Networks Tim Howes <howes@opsware.com> of Opsware Darrel Thomas <darrel.thomas@eds.com> of EDS Phillip Liu <phillip@opsware.com> of Opsware Ray Suorsa <res@opsware.com> of Opsware Ajay Gummadi <Ajay@renditionnetworks.com> of Rendition Networks David G. Schrodel <dschrodel@voyence.com> of Voyence Raymond Cadden <Raymond.cadden@ca.com> of Computer Associates Jim Ritchings <j.ritchings@f5.com> of F5 Noam Fraenkel <nfraenkel@mercury.com> of Mercury TC Convener Dave Roberts, Inkra, dave@inkra.com TC Chair Nominee Dave Roberts, Inkra, dave@inkra.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]