OASIS DCML Network TC

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200409/msg00006.html

The charter for this TC is as follows.

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.

 

TOP OF PAGE