The VLAN Model for Applications

This document describes the model for application and network interaction in reaction to Application Area Architecture Workshop held on February 11 and 12, 2008. There is not completed mechanism for collaboration between application and network yet even though a solution is required. The model proposed in this document is designed without a layer violation. This document propose the VLAn model for the application users.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The VLAN is one of technologies to implement the L2 layer closed network. Since VLAN configuration is proprietary parameter and interface, it is useful to provide common model and schema for the application users. This model is the primitive data model involved by usage scenario corresponding to requirements. This kind of primitive data model is required to standardized because it should be common for application and user. Application and user don't need to CLI level configuration using this model. We designed the common VLAN model as below.

This section describes the VLAN Schema. This schema can describe both tagged vlan and untagged vlan. Tagged vlan id is managed to keep uniq and not exceed to 4096.

]]>

This section describes the VLAN XML example.

tagged_vlan_domain_1 100 VLAN100 NetworkDevice:port0/7 NetworkDevice:port0/11 serverA:port0/1 serverB:port0/1 untagged_vlan_domain_1 untag NetworkDevice:port0/15 NetworkDevice:port0/17 serverC:port0/1 serverD:port0/1 ]]>