<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
    There has to be one entity for each item to be referenced. 
    An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
    please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
    (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
    (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-jilongwang-opsawg-crc-03" ipr="trust200902">
 <!-- category values: std, bcp, info, exp, and historic
    ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
       or pre5378Trust200902
    you can add the attributes updates="NNNN" and obsoletes="NNNN" 
    they will automatically be output with "(if approved)" -->

 <!-- ***** FRONT MATTER ***** -->

 <front>
   <!-- The abbreviated title is used in the page header - it is only necessary if the 
        full title is longer than 39 characters -->

   <title abbrev="Cyberspace Resources Categorization">Framework for Cyberspace Resources Categorization</title>

   <!-- add 'role="editor"' below for the editors if appropriate -->

   <!-- Another author who claims to be an editor -->

   <author fullname="Jilong Wang" initials="WJL" role="editor"
           surname="Wang">
     <organization>Tsinghua University</organization>

     <address>
       <postal>
         <street></street>

         <!-- Reorder these if your country does things differently -->

         <city>Beijing</city>

         <region></region>

         <code>100084</code>

         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>wjl@tsinghua.edu.cn</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
  
   <author fullname="Congcong Miao" initials="MCC" role="editor"
     surname="Miao">
     <organization>Tsinghua University </organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Beijing</city>
         
         <region></region>
         
         <code>100084</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>mccmiao@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   <author fullname="Shuying Zhuang" initials="ZSY" role="editor"
     surname="Zhuang">
     <organization>Tsinghua University </organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Beijing</city>
         
         <region></region>
         
         <code>100084</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>17751034616@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   
   <author fullname="Qianli Zhang" initials="ZQL" role="editor"
     surname="Zhang">
     <organization>Tsinghua University</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Beijing</city>
         
         <region></region>
         
         <code>100084</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>zhang@cernet.edu.cn</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   
   <author fullname="Jianfeng Chen" initials="CJF" role="editor"
     surname="Chen">
     <organization>CETC</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Chengdu</city>
         
         <region></region>
         
         <code>610000</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>atrix@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   
   <date year="2022" />

   <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
        in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

   <!-- Meta-data Declarations -->

   <area>Management</area>

   <workgroup>opsawg</workgroup>

   <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>Internet-Draft</keyword>

   <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

   <abstract>
     <t>This memo presents the definition of cyberspace resource, and then discusses a classification framework for cyberspace resources. Cyberspace is widely applied in people's daily life and it is regarded as a new space, paralleled to the geographic space. There are various resources in cyberspace. However, they have not been systematically defined and classified. The objective of this draft is to present the deifinition of cyberspace resource and a standard classification framework, thus, supporting the unified resource storage and shares. 
       </t>
   </abstract>
 </front>

 <middle>
   <section title="Introduction">
   	<t>
   		Cyberspace, created by communication technologies especially the Internet, is a virtual space where people can easily communicate with others regardless of geographic distance. Due to its convenience, cyberspace has been widely applied in people&apos; daily life and it is regarded as a new space, paralleled to the geographic space. The widely adoption of cyberspace has promote the rapid growth of cyberspace resources.</t>

     

	 <t>
	 	Since the resources in cyberspace have exsited objectively, such as traditional network facilities, access devices, network applications and network datas, it is even not defined up to now. Furthermore, there are not any systematical classification frameworks for cyberspace resources. Most of them are given corresponding names depending on their purpose or vendor, but they seem to be in a "divine" state. Therefore, the resources in cyberspace are not able to stored and shared unifiedly.</t>


     <t>
     	In order to provide a unified description of cyberspace resources, this draft firstly gives the definition of resources in cyberspace. Then it designs a standard classification framework to classify the resource in cyberspace. This standard framework helps to establish a unified cyberspace resources database, which can be used as the basis for network information storage and sharing in both academia and industry field.</t>
     
     <section title="Requirements Language">
       <t>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 <xref
       target="RFC2119">RFC 2119</xref>.</t>
     </section>
   </section>
  
   <!-- This PI places the pagebreak correctly (before the section title) in the text output. -->
   <?rfc needLines="8" ?>
   
   
   <section title="Terminology">
    
     <t>Methods of linear classification: The classification objects are divided into several levels according to specific forms and attributes, and each level is divided into several categories. The same level category constitutes a parallel relationship, 
       and different level categories form a affiliation relationship.</t>
       
     <t> category in higher level: In the methods of linear classification ,
        a category is called category in higher level relative to the next-level category directly
        divided by it.</t>
       
      <t>category in lower level: In the methods of linear classification,  a category is called  category in 
         lower level relative to the upper-level category that classifies the category.</t>
       
       <t>category in same level: In the methods of linear classification, a number of 
         lower-level categories directly classified by a category are called category in same level.</t>
     
   </section>
   
   <section title="Use cases">
     <t>The following sections highlight some of the most common framework for 
       network resources categorization use case scenarios and are in no way 
       exhaustive.</t>
     <section title="Network Management">
       <t>Network management is the process of administering and managing computer networks. Services provided by this discipline include fault analysis, performance management, provisioning of networks and maintaining the quality of service. Now The variety of resources lead to confusion in network. Network resources as the object of network management need to be  paid more attention. But  for network managers, there is a lack of uniform identification, location and management of resources.</t>
       <t>The framework for network resources categorization offers a way 
         for network managers to divide the managed resources. It 
         provides unique identities for each resource, that is, all 
         resources can find the appropriate location in the resources 
         framework tree. Then the corresponding code, name and attributes 
         are added into the database to facilitate unified management. 
         At the same time,  for resources with abnormal properties ,it 
         can be located and fixed vulnerabilities in time.
       </t>
     </section>
     <section title="Network Search">
       <t>
         Now many platforms(Shodan, Censys  etc.) detect network 
         from the network layer to the application layer based 
         on multiple detection technologies. The main goal is to
         identify network resources, including websites, network 
         hardware, etc and provide network identifiable resources 
         search and classification, establish corresponding database 
         to support user full-text search, regular expression, boolean 
         logic and digital range search. But the lack of a unified 
         standardized model will lead to inaccurate and incomplete retrieval of resources.
       </t>
       <t>This framework classifies the resources of the whole network.  
         It can be used to fill the resources search database, and cover 
         the resources that have not been covered before. At the same time, 
         standardize the storage of network resources and improve the search 
         efficiency. </t>
       
     </section>
    
     <section title="Network Security">
       <t>Network viruses and worms themselves are also a kind of network
         resources. With the deepening of network opening and complexity,
         network viruses and worms are evolving constantly, and the 
         characteristics of diversity and spatial discretization are 
         increasing, resulting in a great hidden danger of network 
         security. </t>
       <t>The framework for network resources categorization can locate 
         the network resources more accurately and distinguish the 
         benign or malignant network resources,  study the process of 
         virus evolution and the possible effects according to the 
         attached attributes , and provide a clearer way to safeguard 
         the operation of network space security, such as anti 
         virus, antivirus and so on.
         
       </t>  
     </section>
             
   </section>
   
   <section title="Methodology for Network Resources Categorization"> 
     <section title="Basic Principles">
      <t>The network resources categorization rules SHOULD follow the 
       following principles to meet the completeness, measurability, 
       scalability and relative orthogonality of resources 
       categorization.</t>
       
       <section title="Scientific principle">
         <t>Categorization rules SHOULD be consistent with the basic. 
           organizational rules of network resources.</t>
         <t>The resources categorization perspective SHOULD meet the traditional internet resources integration requirements, and meet the mapping entity integration 
            requirements of the multi-sources mapping platform. </t>
         <t>The resources categorization system SHOULD start from the traditional network resources system and cover
            resource elements and have certain compatibility.</t>
       </section>
       <section title="Systematic principle">
         <t>The network resources categorization architecture can sort and systemize all network resources according to their 
           characteristics, correctly reflect the vertical and 
           horizontal architecture, and form a reasonable categorization
           system.
         </t>
         <t>Each resource in the system occupies a position. And it SHALL reflect the certain relationship between resources, and profoundly reveal the network relationship and the whole 
           picture between resources.
         </t>
       </section>
       <section title="Orthogonality principle ">
         <t> Each taxonomic unit of each categorization level in the resources categorization system SHOULD be mutually incompatible, so that any network resource cannot belong to two groups at the same time. That is, the unique encoding allows the 
           network resources to be uniquely identified and described.
         </t>
        
       </section>
       
       
       <section title="Consistency principle">
         <t>Categorization design SHOULD be consistent with other national standards in related fields, and at the same time meets the original information concept and semantic consistency when 
           resources coding and code expansion, addition and deletion.
         </t>
       
       </section>
       
       <section title="Scalable principle">
         <t>It SHALL meet the needs of the development and change of network resources to a great extent. It can increase the 
           categorization of different levels and can also be extended 
           for expansion of unknown resources.
         </t>
         
       </section>
       
     </section>
     
     
     
 
   
   
   <section title="Requirements on categorization"> 
     <t>This section describes the requirements for categorization of
       network resources . The network resources categorization SHOULD 
       meet these requirements to make sure it is orthogonal and 
       accurate. Note that the requirements listed in this section have 
       been separated from the context in which they may appear. </t>
     <t>The following template is used for the definition of the 
       Requirements:
     </t>
     
     <t>Req-ID:  An ID composed of a unique two-digit number.</t>
     <t>Description: The rationale and description of the requirement.</t>
       
     <t>The detail requirements on categorization are listed as following:</t>  
     <t>Req-ID:  01</t> 
     <t>Description: The total range of categories in lower level 
       classified by categories in higher level SHOULD be the 
       same as the range of categories in higher level.</t>
     <t>Req-ID:  02</t>
     <t>Description: When dividing category in higher level,  SHOULD 
     choose the same classification perspective to get the
     categories in lower level.</t>
     <t>Req-ID:  03</t>
     <t>Description: The categories in same level SHALL do not intersect, 
     do not repeat, and only correspond to a category in higher 
     level.</t>
     <t>Req-ID:  04</t>
     <t>Description: Categorization SHOULD be carried out from high to 
       low, and there MUST be no jump.</t>
   </section>
     
     
     
     
     
   </section>
   <section title="Framework for Network Resources Categorization">
     <t>This framework for network resources categorization uses methods 
       of linear classification to classify them into five categories: 
       category, sub-category, large, medium and small-category based 
       on the above principles and requirements. It specifies the 
       classification names of the categories, Class-I, Class-II, 
       Class-III, Class-IV, Class-V, and the small-categories are 
       subdivided and named according to the application requirements.
     </t>
     <section title="Class-I">
       <t>Firstly, The categories of network resources are divided into 
       four categories: the network infrastructure, the network 
       application service, the network data resource and the network  
       virtual body based on the sources, applications and 
       activities of network resources. Then the 4 categories are 
       further subdivided into 12 sub-categories.</t>
       <t>The following template is used for the definition of the 
         categorization  of network resources:
       </t>
       <t>Class-I: The name of network resources category in highest level</t>
       <t>EnCode-q: An ID organized in OID format to identify network 
         resources. It can be added to 1.3.6.1.2 mgmt  <xref
           target="RFC3232">RFC3232</xref>.
       </t>
       <t>Upper-Class: The name of its category in  higher level.</t>
       <t>Attribute:The characteristics of this network resource 
         category from different levels of internet.
       </t>
       
       
       <t>Class-I: Network Infrastructure</t>
       <t>EnCode-q:1</t>
       <t>Upper-Class: None</t>
       <t>Attribute:MAC Address\IP Address\DNS Address\ DHCP 
       Address\Gateway address\ Operating System\</t>
       
       <t>Class-I: Network application service</t>
       <t>EnCode-q:2</t>
       <t>Upper-Class: None</t>
       <t>Attribute:MAC Address\IP Address\Port\Service\
       Protocol\Performance\</t>
       
       <t>Class-I: Network data source</t>
       <t>EnCode-q:3</t>
       <t>Upper-Class: None</t>
       <t>Attribute:IP Address\Port\Service\ Protocol\ Data Format\ Data 
       size\Data Permission\</t>
       
       
       <t>Class-I: Network virtual subject</t> 
       <t>EnCode-q:4</t>
       <t>Upper-Class: None</t>
       <t>Attribute:IP Address\Port\Service\ Protocol\Account Name\ 
       Landing Time\</t>
       
     </section>
     
     
     <section title="Class-II">
       <t>The following template is used for the definition of the 
         categorization of network resources category in second category 
         level:
       </t>
       <t>Class-II: The name of network resources category in second level</t>
       <t>EnCode-q: An ID organized in OID format to identify network 
         resources. It can be added to 1.3.6.1.2 mgmt  <xref
           target="RFC3232">RFC3232</xref>.
       </t>
       
    
       <t>Upper-Class: The name of its category in  higher level.</t>
       <t>Attribute: The characteristics of this network resource 
         category from different levels of internet.
       </t>
       <section title="Network Infrastructure">
         <t>The Network infrastructure is the physical part of the network 
           resources which provides basic support, including various 
           hardware devices. It is the material basis of all network 
           services and is divided into the following 5 sub-category based 
           on the internet architecture and its network functions, device 
           roles and network levels .</t>
       
       
           <t>Class-II: Autonomous domain </t>
           <t>EnCode-q:1.1</t>
           <t>Upper-Class: Network Infrastructure (EnCode-q:1)</t>
           <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating 
         System\ASN\ISP\Institutions\Organizations\Operators\</t>
        
         
         <t>Class-II: Network</t>
         <t>EnCode-q:1.2</t>
         <t>Upper-Class: Network Infrastructure (EnCode-q:1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network</t>
        
         
         <t>Class-II: Intermediate node</t>
         <t>EnCode-q:1.3</t>
         <t>Upper-Class: Network Infrastructure  (EnCode-q:1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code</t>
         
         <t>Class-II: Terminal node</t>
         <t>EnCode-q:1.4</t>
         <t>Upper-Class: Network Infrastructure  (EnCode-q:1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         
         <t>Class-II: Link</t>
         <t>EnCode-q:1.5</t>
         <t>Upper-Class: Network Infrastructure (EnCode-q:1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
       
         
         
       </section>
       
       
       <section title="Network application service">
       <t>Network application service is an application running on top of 
         the network application layer and provide data storage, 
         manipulation, rendering, communication, or other capabilities.
         These capabilities typically use an application layer network 
         protocol. It is classified into inorganic services and organic 
         services based on the internet architecture and the unity of a 
         network application service.</t>
         
         <t>Class-II: Inorganic service</t>
         <t>EnCode-q:2.1</t>
         <t>Upper-Class: Network application service  (EnCode-q:2)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
         
         <t>Class-II: Organic service</t>
         <t>EnCode-q:2.2</t>
         <t>Upper-Class: Network application service (EnCode-q:2)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
        
       </section>
       <section title="Network data source">
         <t>Network data  is defined as a resource that is stored on the 
           Internet and is not running. We divide it into five categories 
           based on resource content.
         </t>
         <t>Class-II: Code</t>
         <t>EnCode-q:3.1</t>
         <t>Upper-Class: Network data source(EnCode-q:3)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\ Programming Language\</t>
         
         <t>Class-II: Text resource</t>
         <t>EnCode-q:3.2</t>
         <t>Upper-Class: Network data source(EnCode-q:3)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>Class-II: Picture resource</t>
         <t>EnCode-q:3.3</t>
         <t>Upper-Class: Network data source(EnCode-q:3)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>Class-II: Audio resource</t>
         <t>EnCode-q:3.4</t>
         <t>Upper-Class: Network data source(EnCode-q:3)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>Class-II: Video resource</t>
         <t>EnCode-q:3.5</t>
         <t>Upper-Class: Network data source(EnCode-q:3)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
       </section>
       <section title="Network virtual subject">
         <t>The virtual subject of network refers to the account behavior 
           of the network virtual feature stored on the Internet. The 
           carrier of the user in network is a virtual account, So The 
           network virtual subject is divided into the following sub-
           category.
         </t>
         <t>Class-II: Network account</t>
         <t>EnCode-q:4.1</t>
         <t>Upper-Class: Network virtual subject (EnCode-q:4)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\Account Name\ 
         Landing Time\</t>
         
       </section> 
    </section>
     <section title="Class-III  and Class-IV">
       <t>Note that Network infrastructure, the categorization of the 
       large-categories are organized from the hierarchical location 
       of the network infrastructure in the network architecture and 
       the role played by it. </t>
       
       <t>Note that Network application service, first organize the 
       categorization of large-category from the perspective of whether 
       the application is based on ports, and then classify these 
       categories according to the types of services provided by the 
       application. </t>
       
       <t>Note that Network data source, firstly the categorization of 
       large-categories are organized from whether the data resources 
       need to be compiled, the storage mode , structure of the data 
       resources and the functions of the data resources are completed. 
       And then classify these categories according to the application 
       scenarios of the data and the data are performed. </t>
       
       <t>On the basis of category and sub-category, the resources are 
       further classified and named according to methods of linear 
       classification. On the basis of 4 Class-I and 13 Class-II, there 
       are 22 categories, of which there are 10 network infrastructure 
       categories,5 network  application services categories and 7 
       network  data resources categories.</t>
       <section title="Autonomous domain">
         <t>We continue "Autonomous domain" sub-category categorization.</t>
         <t>Class-III: Autonomous domain.</t>
         <t>EnCode-q:1.1.1</t>
         <t>Upper-Class: Autonomous domain (EnCode-q:1.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating 
         System\ASN\ISP\Institutions\Organizations\Operators\</t>
         
         <t>According to the division of the number of digits of the 
         autonomous system number ASN which is owned by each autonomous 
         region. This large-category is divided into 16 autonomous 
         regions and 32 autonomous regions, with a total of 2 categories.</t>
         <t>Class-IV:Autonomous domain(16 bits)</t>
         <t>EnCode-q:1.1.1.1</t>
         <t>Upper-Class: Autonomous domain (EnCode-q:1.1.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating 
         System\ASN\ISP\Institutions\Organizations\Operators\</t>
         <t>Class-IV:Autonomous domain(32 bits)</t>
         <t>EnCode-q:1.1.1.2</t>
         <t>Upper-Class: Autonomous domain (EnCode-q:1.1.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating 
         System\ASN\ISP\Institutions\Organizations\Operators\</t>
         
       </section>
       <section title="Network">
         <t>The subcategories of "network" are organized in accordance with 
         the characteristics of whether the application layer is only 
         oriented to the application layer or the main application layer.</t>
         
         <t>Class-III: physical network</t>
         <t>EnCode-q:1.2.1</t>
         <t>Upper-Class: Network (EnCode-q:1.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>Class-III: overlay network</t>
         <t>EnCode-q:1.2.2</t>
         <t>Upper-Class: Network (EnCode-q:1.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>The physical network is divided into categories: the backbone 
         network, the access network, the Internet of things, the 
         industrial network and the other network according to the 
         hierarchical position of the network ,the deployed area, and 
         the production and life tasks undertaken in the entire network 
         architecture.</t>
         
         <t>Class-IV: backbone network</t>
         <t>EnCode-q:1.2.1.1</t>
         <t>Upper-Class: physical network (EnCode-q:1.2.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\
         Organization\</t>
         
         <t>Class-IV: access network</t>
         <t>EnCode-q:1.2.1.2</t>
         <t>Upper-Class: physical network (EnCode-q:1.2.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\
         Organization\</t>
         
         <t>Class-IV: Internet of things </t>
         <t>EnCode-q:1.2.1.3</t>
         <t>Upper-Class: physical network (EnCode-q:1.2.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>Class-IV: industrial network</t>
         <t>EnCode-q:1.2.1.4</t>
         <t>Upper-Class: physical network (EnCode-q:1.2.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\Protocol\</t>
         
         <t>Class-IV: other network</t>
         <t>EnCode-q:1.2.1.5</t>
         <t>Upper-Class: physical network (EnCode-q:1.2.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>The overlay network is divided into 4 categories:Content 
         Delivery Network, peer-to-peer network, virtual private network 
         and the other network.</t>
         
         <t>Class-IV:Content Delivery Network </t>
         <t>EnCode-q:1.2.2.1</t>
         <t>Upper-Class: overlay network (EnCode-q:1.2.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>Class-IV:peer-to-peer network</t>
         <t>EnCode-q:1.2.2.2</t>
         <t>Upper-Class: overlay network (EnCode-q:1.2.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>Class-IV:virtual private network <xref
           target="RFC2764">RFC2764</xref></t>
         <t>EnCode-q:1.2.2.3</t>
         <t>Upper-Class: overlay network (EnCode-q:1.2.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
         <t>Class-IV:other network</t>
         <t>EnCode-q:1.2.2.4</t>
         <t>Upper-Class: overlay network (EnCode-q:1.2.2)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Network\</t>
         
       </section>
       <section title="Intermediate node">
         <t>The "intermediate node" sub-category organizes a large-category
           according to the functions that nodes play in the network 
           architecture. It is divided into routing node, switching node, 
           and controlling node.
         </t>
         <t>Class-III: routing node </t>
         <t>EnCode-q:1.3.1 </t>
         <t>Upper-Class: Intermediate node(EnCode-q:1.3) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number 
         Code\ Routing Protocol\ </t>
         
         <t>Class-III: switching node </t>
         <t>EnCode-q:1.3.2 </t>
         <t>Upper-Class: Intermediate node(EnCode-q:1.3) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
          Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>Class-III: controlling node </t>
         <t>EnCode-q:1.3.3 </t>
         <t>Upper-Class: Intermediate node(EnCode-q:1.3) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>The routing node is classified into categories inter-domain 
         routing node and intra-domain routing  node according to the 
         working level of the routing.  </t>
         
         <t>Class-IV: inter-domain routing node  <xref
           target="RFC904">RFC904</xref> </t>
         <t>EnCode-q:1.3.1.1 </t>
         <t>Upper-Class: routing node (EnCode-q:1.3.1)  </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\Operating System\Model Number 
         Code\ Routing Protocol\ </t>
         
         <t>Class-IV: intra-domain routing node </t>
         <t>EnCode-q:1.3.1.2 </t>
         <t>Upper-Class: routing node (EnCode-q:1.3.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\Operating System\Model Number 
         Code\ Routing Protocol\ASN\ISP\ </t>
         
         <t>The switching node is organized into different categories 
         according to different network segments where the node is 
         located. </t>
         
         <t>Class-IV: hub  </t>
         <t>EnCode-q:1.3.2.1 </t>
         <t>Upper-Class: switching node (EnCode-q:1.3.2) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>Class-IV: bridge <xref
           target="RFC1242">RFC1242</xref></t>
         <t>EnCode-q:1.3.2.2 </t>
         <t>Upper-Class: switching node (EnCode-q:1.3.2) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>Class-IV: switch </t>
         <t>EnCode-q:1.3.2.3 </t>
         <t>Upper-Class: switching node (EnCode-q:1.3.2) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>Class-IV: gateway </t>
         <t>EnCode-q:1.3.2.4 </t>
         <t>Upper-Class: switching node (EnCode-q:1.3.2) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>Class-IV: other </t>
         <t>EnCode-q:1.3.2.5 </t>
         <t>Upper-Class: switching node (EnCode-q:1.3.2) </t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\Model Number Code\ </t>
         
         <t>The controlling  node is no longer to be classified here. </t> 
         
       </section>
       <section title="Terminal node">
         
         <t>The "Terminal node" sub-category organizes a large-category 
         according to the functions played by the terminal in actual 
         production and life. It is divided into  client, site, hybrid 
         node, and a total of three major categories.</t>
         <t>Class-III: client</t>
         <t>EnCode-q:1.4.1</t>
         <t>Upper-Class: Terminal node (EnCode-q:1.4)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         
         <t>Class-III: server</t>
         <t>EnCode-q:1.4.2</t>
         <t>Upper-Class: Terminal node (EnCode-q:1.4)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\Performance\</t>
         
         <t>Class-III: hybrid node</t>
         <t>EnCode-q:1.4.3</t>
         <t>Upper-Class: Terminal node (EnCode-q:1.4)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         
         <t>The client category  is subdivided into desktop device, 
         mobile device, sensor device, and other according to the 
         physical device types of the nodes.</t>
         
         <t>Class-IV: desktop device</t>
         <t>EnCode-q:1.4.1.1</t>
         <t>Upper-Class: client (EnCode-q:1.4.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         
         <t>Class-IV: mobile device</t>
         <t>EnCode-q:1.4.1.2</t>
         <t>Upper-Class: client (EnCode-q:1.4.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         
         <t>Class-IV: sensor device </t>
         <t>EnCode-q:1.4.1.3</t>
         <t>Upper-Class: client (EnCode-q:1.4.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\ Detection information\</t>
         
         <t>Class-IV: other</t>
         <t>EnCode-q:1.4.1.4</t>
         <t>Upper-Class: client (EnCode-q:1.4.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Model Number 
         Code\</t>
         <t>The server and  hybrid node continue the division of their sub-
         category</t>
         
         
       </section>
       <section title="Link">
       <t>The "Link" sub-category is organized into a large-category of 
         transmission links according to the transmission medium used 
         by the network, and is divided into two categories: wired link 
         and wireless link.</t>
         
         <t>Class-III: wired link </t>
         <t>EnCode-q:1.5.1</t>
         <t>Upper-Class: Link (EnCode-q:1.5)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
         <t>Class-III: wireless link</t>
         <t>EnCode-q:1.5.2</t>
         <t>Upper-Class: Link (EnCode-q:1.5)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway addre</t>
         
         <t>The wired link category is organized according to the material 
         of the transmission medium and the winding mode of the 
         transmission medium. It is divided into twisted pair, coaxial 
         cable,  digital subscriber line ,optical fiber and other.</t>
         
         <t>Class-IV: twisted pair</t>
         <t>EnCode-q:1.5.1.1</t>
         <t>Upper-Class: wired link (EnCode-q:1.5.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
         <t>Class-IV: coaxial cable </t>
         <t>EnCode-q:1.5.1.2</t>
         <t>Upper-Class: wired link (EnCode-q:1.5.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
         <t>Class-IV: digital subscriber line</t> 
         <t>EnCode-q:1.5.1.3</t>
         <t>Upper-Class: wired link (EnCode-q:1.5.1)</t>
         <t> Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
         <t>Class-IV: optical fiber </t>
         <t>EnCode-q:1.5.1.4</t>
         <t>Upper-Class: wired link (EnCode-q:1.5.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         
         <t>Class-IV: other</t>
         <t>EnCode-q:1.5.1.5</t>
         <t>Upper-Class: wired link (EnCode-q:1.5.1)</t>
         <t>Attribution: MAC Address\IP Address\DNS Address\ DHCP 
         Address\Gateway address\ Operating System\ Transmission 
         medium\Protocol\</t>
         <t>The wireless is no longer to be classified here. </t>
         
       </section>
       <section title="Inorganic service">
         <t>The "Inorganic Service" sub-category, according to the port 
           type used by the application, the tight program bound to the 
           application and the port <xref
             target="RFC6346">RFC6346</xref>, organizes a large-category. 
           which is divided into  generic port service , registered port 
           service , and  dynamic/private port service. 
         </t>
         
         <t>Class-III: generic port service  </t>
         <t>EnCode-q:2.1.1 </t>
         <t>Upper-Class: Inorganic service (EnCode-q:2.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-III: registered port service </t>
         <t>EnCode-q:2.1.2 </t>
         <t>Upper-Class: Inorganic service (EnCode-q:2.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-III: dynamic/private port service </t>
         <t>EnCode-q:2.1.3 </t>
         <t>Upper-Class: Inorganic service (EnCode-q:2.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>According to the port used and the type of service provided, 
         the generic port service is divided into website service (HTTP, 
         HTTPS), file transfer service (FTP, TFTP), mail service (SMTP, 
         POP3, IMAP), network management service (SNMP) <xref
           target="RFC1157">RFC1157</xref>, domain 
         name service (DNS) and other. </t>
         
         <t>Class-IV: website service </t>
         <t>EnCode-q:2.1.1.1 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\URL\ </t>
         
         <t>Class-IV: file transfer service </t>
         <t>EnCode-q:2.1.1.2 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: mail service  </t>
         <t>EnCode-q:2.1.1.3 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: network management service  </t>
         <t>EnCode-q:2.1.1.4 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: domain name service </t>
         <t>EnCode-q:2.1.1.5 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: other </t>
         <t>EnCode-q:2.1.1.6 </t>
         <t>Upper-Class: generic port service  (EnCode-q:2.1.1) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>The registered port service is no longer to be classified here. 
         According to the type of services provided by the application, 
         the dynamic/private port service is divided into search query 
         service, audio and video service, shopping service, social 
         service and other. </t>
         
         <t>Class-IV: search query service  </t>
         <t>EnCode-q:2.1.3.1 </t>
         <t>Upper-Class: dynamic/private port service (EnCode-q:2.1.3)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: audio and video service </t>
         <t>EnCode-q:2.1.3.2 </t>
         <t>Upper-Class: dynamic/private port service (EnCode-q:2.1.3) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: shopping service </t>
         <t>EnCode-q:2.1.3.3 </t>
         <t>Upper-Class: dynamic/private port service (EnCode-q:2.1.3) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: social service  </t>
         <t>EnCode-q:2.1.3.4 </t>
         <t>Upper-Class: dynamic/private port service (EnCode-q:2.1.3) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
         <t>Class-IV: other </t>
         <t>EnCode-q:2.1.3.5 </t>
         <t>Upper-Class: dynamic/private port service (EnCode-q:2.1.3) </t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\ </t>
         
       </section>
       
       <section title="Organic service">
         
         <t>The "organic service" continues the sub-category classification.</t>
         <t>Class-III: Organic service</t>
         <t>EnCode-q:2.2.1</t>
         <t>Upper-Class: Organic service (EnCode-q:2.2)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
         
         <t>The organic service categories are classified into P2P service 
         , CDN service and other according to the scenario where the application 
         is located and the network service function.</t>
         
         <t>Class-IV: P2P service </t>
         <t>EnCode-q:2.2.1.1</t>
         <t>Upper-Class: Organic service (EnCode-q:2.2.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
         
         <t>Class-IV: CDN service </t>
         <t>EnCode-q:2.2.1.2</t>
         <t>Upper-Class: Organic service (EnCode-q:2.2.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
         
         <t>Class-IV: other </t>
         <t>EnCode-q:2.2.1.3</t>
         <t>Upper-Class: Organic service (EnCode-q:2.2.1)</t>
         <t>Attribution: MAC Address\IP Address\Port\Service\ 
         Protocol\Performance\</t>
         
       </section>
       
       <section title="Code">
         <t>The "Code" continues the sub-category classification and is no 
           longer subdivided. </t>
         <t>Class-III: Code</t>
         <t>EnCode-q:3.1.1</t>
         <t>Upper-Class: Code (EnCode-q:3.1)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\ Programming Language\ </t>
         
       </section>
       
       <section title="Text resource">
         
         <t>The "Text resource" sub-category, according to the storage form 
         of text, whether the text can be represented by unified data or 
         format to organize large categories, is divided into structured 
         text, semi-structured text, unstructured text.</t>
         
         <t>Class-III: structured text</t>
         <t>EnCode-q:3.2.1</t>
         <t>Upper-Class: Text resource (EnCode-q:3.2)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>Class-III: semi-structured text</t>
         <t>EnCode-q:3.2.2</t>
         <t>Upper-Class: Text resource (EnCode-q:3.2)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>Class-III: unstructured text </t>
         <t>EnCode-q:3.2.3</t>
         <t>Upper-Class: Text resource (EnCode-q:3.2)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         <t>The " structured text", "semi-structured text" and " structured 
         text "continues the large-category classification and is no 
         longer subdivided. </t>
         
       </section>
       
       
       <section title="Picture resource">
         
         <t>The "picture resource" continues the sub-category classification 
         and is no longer subdivided.  </t>
         
         <t>Class-III: Picture resource </t>
         <t>EnCode-q:3.3.1 </t>
         <t>Upper-Class: Picture resource (EnCode-q:3.3) </t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\ </t>
         
         
       </section>
       <section title="Audio resource">
         <t>The  Audio resource continues the sub-category classification 
         and is no longer subdivided. </t>
         <t>Class-III: Audio resource</t>
         <t>EnCode-q:3.4.1</t>
         <t>Upper-Class: Audio resource (EnCode-q:3.4)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>
         
         
       </section>
       
       
       <section title="Video resource">
         <t>The " Video resource" continues the sub-category classification. and is no longer subdivided.</t>
         <t>Class-III: Video resource</t>
         <t>EnCode-q:3.5.1</t>
         <t>Upper-Class: Video resource (EnCode-q:3.5)</t>
         <t>Attribution: IP Address\Port\Service\ Protocol\ Data Format\ 
         Data size\Data Permission\</t>   
       </section>
       
       </section>
       
     </section>
     




   

     
   

   

   <section anchor="Acknowledgements" title="Acknowledgements">
     <t>The authors would like to thank the support of Tsinghua. University  and China Electronic Technology Group Corporation thirtieth Research Institute. We also thank the following persons for their suggestions on earlier versions of this work: Zhi Sun,
       Jianfeng Chen, Da He, Rui Xu, Zhihong Rao, etc, for their. discussion, comments and suggestions. 
     </t>

    
   </section>
    
   <!-- Possibly a 'Contributors' section ... -->

   <section anchor="IANA" title="IANA Considerations">
     <t>This memo includes no request to IANA.</t>
   </section>

   <section anchor="Security" title="Security Considerations">
     <t>This document only defines a framework for network resources categorization. 
        This document itself does not directly introduce security issues. </t>
   </section>
   
 </middle>
  
  
  

 <!--  *****BACK MATTER ***** -->

 <back>
   <!-- References split into informative and normative -->

   <!-- There are 2 ways to insert reference entries from the citation libraries:
    1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
    2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
       (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

    Both are cited textually in the same manner: by using xref elements.
    If you use the PI option, xml2rfc will, by default, try to find included files in the same
    directory as the including file. You can also define the XML_LIBRARY environment variable
    with a value containing a set of directories to search.  These can be either in the local
    filing system or remote ones accessed by http (http://domain/dir/... ).-->

   <references title="Normative References">
     <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
    

     <reference anchor="RFC2119">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Key words for use in RFCs to Indicate
           Requirement Levels</title>

         <author initials="S." surname="Bradner">
           <organization>Harvard University</organization>
         </author>

         <date month="March" year="1997" />
       </front>
       <seriesInfo name="RFC" value="2119" />
     </reference>
    
    
     <reference anchor="RFC3232">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Assigned Numbers: RFC 1700 is Replaced by an On-line Database</title>
         
         <author initials="J." surname="Reynolds">
           <organization>RFC</organization>
         </author>
           
         <date month="January" year="2002" />
       </front>
       <seriesInfo name="RFC" value="3232" />
     </reference>
     
     <reference anchor="RFC1242">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Benchmarking Terminology for Network
           Interconnection Devices
         </title>
         
         <author initials="S." surname="Bradner">
           <organization></organization>
         </author>
         
         <date month="July" year="1991" />
       </front>
       <seriesInfo name="RFC" value="1242" />
     </reference>
     
     <reference anchor="RFC2764">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>A Framework for IP Based Virtual 
           Private Networks
         </title>
         
         <author initials="B." surname="Gleeson">
           <organization></organization>
         </author>
         
         <date month="February" year="2000" />
       </front>
       <seriesInfo name="RFC" value="2764" />
     </reference>
     
     
     <reference anchor="RFC904">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>A Framework for IP Based Virtual 
           Private Networks
         </title>
         
         <author initials="D." surname="Mills">
           <organization>BBN</organization>
         </author>
         
         <date month="April" year="1984" />
       </front>
       <seriesInfo name="RFC" value="904" />
     </reference>
     
     <reference anchor="RFC6346">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>The Address plus Port (A+P) Approach to the 
           IPv4 Address Shortage
         </title>
         
         <author initials="R." surname="Bush">
           <organization>BBN</organization>
         </author>
         
         <date month="August" year="2011" />
       </front>
       <seriesInfo name="RFC" value="6346" />
     </reference>
     
     <reference anchor="RFC1157">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title> A Simple Network Management Protocol (SNMP) 
         </title>
         
         <author initials="J." surname="Case">
           <organization>BBN</organization>
         </author>
         
         <date month="May" year="1990" />
       </front>
       <seriesInfo name="RFC" value="1157" />
     </reference>
     
   </references>
   
   

  


   

   <!-- Change Log

v00 2006-03-15  EBD   Initial version

v01 2006-04-03  EBD   Moved PI location back to position 1 -
                     v3.1 of XMLmind is better with them at this location.
v02 2007-03-07  AH    removed extraneous nested_list attribute,
                     other minor corrections
v03 2007-03-09  EBD   Added comments on null IANA sections and fixed heading capitalization.
                     Modified comments around figure to reflect non-implementation of
                     figure indent control.  Put in reference using anchor="DOMINATION".
                     Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH     Major changes: shortened discussion of PIs,
                     added discussion of rfc include.
v05 2007-03-10 EBD    Added preamble to C program example to tell about ABNF and alternative 
                     images. Removed meta-characters from comments (causes problems).

v06 2010-04-01 TT     Changed ipr attribute values to latest ones. Changed date to
                     year only, to be consistent with the comments. Updated the 
                     IANA guidelines reference from the I-D to the finished RFC.  -->
 </back>
</rfc>