TOC 
Network Working GroupM. Ninomiya
Internet-DraftR. Atarashi
Intended status: InformationalInternet Initiative Japan Inc.
Expires: November 1, 2010April 30, 2010


The VLAN Model for Applications
draft-ninomiya-netappvlan-02

Abstract

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.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

This Internet-Draft will expire on November 1, 2010.

Copyright Notice

Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.


Table of Contents

1.  Introduction
    1.1.  Requirements notation
2.  VLAN Model
    2.1.  VLAN Schema
    2.2.  VLAN XML example
3.  Security Considerations
4.  Normative References
§  Authors' Addresses



 TOC 

1.  Introduction

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.


 TOC 

1.1.  Requirements notation

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 [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).


 TOC 

2.  VLAN Model

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. 


    +-------------------------------------------------+
    |                Network Device                   |
    |                                                 |
    +-------------------------------------------------+
       port 0/7   port 0/11      port 0/15  port 0/17
           |          |              |          |
           |          |              |          |
        VLAN100    VLAN100         untag      untag
           |          |              |          |
           |          |              |          |
       port 0/1   port 0/1       port 0/1   port 0/1
     +---------+ +---------+   +---------+ +---------+
     | ServerA | | ServerB |   | ServerC | | ServerD |
     |         | |         |   |         | |         |
     +---------+ +---------+   +---------+ +---------+

 TOC 

2.1.  VLAN Schema

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. 


<?xml version="1.0" encoding="utf-8" ?>

<xsd:schema elementFormDefault="qualified"
 targetNamespace="http://siesta.iij.ad.jp/L2_domain"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:L2_domain="http://siesta.iij.ad.jp/L2_domain">
 <xsd:element name="root">
  <xsd:complexType>
   <xsd:sequence>
    <xsd:element name="tagged_vlan_domain" maxOccurs="unbounded">
     <xsd:complexType>
      <xsd:sequence>
       <xsd:element name="tagged_vlan_domain_id" type="xsd:string" />
       <xsd:element name="tagged_vlan" maxOccurs="4096">
        <xsd:complexType>
         <xsd:sequence>
          <xsd:element name="vlan_id">
           <xsd:simpleType>
            <xsd:restriction base="xsd:integer">
             <xsd:minInclusive value="1" />
             <xsd:maxInclusive value="4096" />
            </xsd:restriction>
           </xsd:simpleType>
          </xsd:element>
          <xsd:element name="vlan_name" type="xsd:string" />
          <xsd:element name="network_interface_list">
           <xsd:complexType>
            <xsd:sequence>
             <xsd:element name="network_interface_location"
               type="xsd:string" maxOccurs="unbounded">
             </xsd:element>
            </xsd:sequence>
           </xsd:complexType>
          </xsd:element>
         </xsd:sequence>
        </xsd:complexType>
       </xsd:element>
      </xsd:sequence>
     </xsd:complexType>
    </xsd:element>
    <xsd:element name="unntagged_vlan_domain" maxOccurs="unbounded">
     <xsd:complexType>
      <xsd:sequence>
       <xsd:element name="untagged_vlan_domain_id" type="xsd:string" />
       <xsd:element name="untagged_vlan">
        <xsd:complexType>
         <xsd:sequence>
          <xsd:element name="untagged_vlan"
             type="xsd:string" fixed="untag" />
          <xsd:element name="network_interface_list">
           <xsd:complexType>
            <xsd:sequence>
             <xsd:element name="network_interface_location"
               type="xsd:string" maxOccurs="unbounded" />
            </xsd:sequence>
           </xsd:complexType>
          </xsd:element>
         </xsd:sequence>
        </xsd:complexType>
       </xsd:element>
      </xsd:sequence>
     </xsd:complexType>
    </xsd:element>
   </xsd:sequence>
  </xsd:complexType>
 </xsd:element>
</xsd:schema>

 TOC 

2.2.  VLAN XML example

This section describes the VLAN XML example. 


<?xml version="1.0" encoding="utf-8" ?>

<L2_domain:root xmlns:L2_domain="http://siesta.iij.ad.jp/L2_domain">
 <L2_domain:tagged_vlan_domain>
  <L2_domain:tagged_vlan_domain_id>tagged_vlan_domain_1
    </L2_domain:tagged_vlan_domain_id>
  <L2_domain:tagged_vlan>
   <L2_domain:vlan_id>100</L2_domain:vlan_id>
   <L2_domain:vlan_name>VLAN100</L2_domain:vlan_name>
   <L2_domain:network_interface_list>
    <L2_domain:network_interface_location>NetworkDevice:port0/7
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>NetworkDevice:port0/11
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>serverA:port0/1
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>serverB:port0/1
      </L2_domain:network_interface_location>
   </L2_domain:network_interface_list>
  </L2_domain:tagged_vlan>
 </L2_domain:tagged_vlan_domain>
 <L2_domain:unntagged_vlan_domain>
  <L2_domain:untagged_vlan_domain_id>untagged_vlan_domain_1
    </L2_domain:untagged_vlan_domain_id>
  <L2_domain:untagged_vlan>
   <L2_domain:untagged_vlan>untag</L2_domain:untagged_vlan>
   <L2_domain:network_interface_list>
    <L2_domain:network_interface_location>NetworkDevice:port0/15
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>NetworkDevice:port0/17
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>serverC:port0/1
      </L2_domain:network_interface_location>
    <L2_domain:network_interface_location>serverD:port0/1
      </L2_domain:network_interface_location>
   </L2_domain:network_interface_list>
  </L2_domain:untagged_vlan>
 </L2_domain:unntagged_vlan_domain>
</L2_domain:root>

 TOC 

3.  Security Considerations

TBD


 TOC 

4. Normative References

[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).

 TOC 

Authors' Addresses

  Megumi Ninomiya
  Internet Initiative Japan Inc.
  Jinbocho-Mitsui Buld., 1-105 Kanda Jinbo-cho,
  Chiyoda-ku, Tokyo 101-0051
  Japan
Phone:  +81 3 5205 6464
Email:  ninomiya@iij.ad.jp
  
  Ray S. Atarashi
  Internet Initiative Japan Inc.
  Jinbocho-Mitsui Buld., 1-105 Kanda Jinbo-cho,
  Chiyoda-ku, Tokyo 101-0051
  Japan
Phone:  +81 3 5205 6464
Email:  ray@iijlab.net