Network Working Group                                        M. Ninomiya
Internet-Draft                                               R. Atarashi
Intended status: Informational            Internet Initiative Japan Inc.
Expires: January 7, 2009                                    July 6, 2008


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

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 7, 2009.


















Ninomiya & Atarashi      Expires January 7, 2009                [Page 1]

Internet-Draft       The VLAN Model for Applications           July 2008


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.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements notation  . . . . . . . . . . . . . . . . . .  3
   2.  VLAN Model . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  VLAN Schema  . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  VLAN XML example . . . . . . . . . . . . . . . . . . . . .  6
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   4.  Normative References . . . . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9
   Intellectual Property and Copyright Statements . . . . . . . . . . 10





























Ninomiya & Atarashi      Expires January 7, 2009                [Page 2]

Internet-Draft       The VLAN Model for Applications           July 2008


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.

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].




































Ninomiya & Atarashi      Expires January 7, 2009                [Page 3]

Internet-Draft       The VLAN Model for Applications           July 2008


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.

   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 |
        |         | |         |   |         | |         |
        +---------+ +---------+   +---------+ +---------+

2.1.  VLAN Schema

   This section describes the VLAN Schema.

 <?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>



Ninomiya & Atarashi      Expires January 7, 2009                [Page 4]

Internet-Draft       The VLAN Model for Applications           July 2008


             <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>



Ninomiya & Atarashi      Expires January 7, 2009                [Page 5]

Internet-Draft       The VLAN Model for Applications           July 2008


 </xsd:schema>

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>






Ninomiya & Atarashi      Expires January 7, 2009                [Page 6]

Internet-Draft       The VLAN Model for Applications           July 2008


3.  Security Considerations

   TBD
















































Ninomiya & Atarashi      Expires January 7, 2009                [Page 7]

Internet-Draft       The VLAN Model for Applications           July 2008


4.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.















































Ninomiya & Atarashi      Expires January 7, 2009                [Page 8]

Internet-Draft       The VLAN Model for Applications           July 2008


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































Ninomiya & Atarashi      Expires January 7, 2009                [Page 9]

Internet-Draft       The VLAN Model for Applications           July 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.











Ninomiya & Atarashi      Expires January 7, 2009               [Page 10]