<?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-hanliu-ricg-01" 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="Rule-based International Cyberspace Governance">Framework for Rule-based International Cyberspace Governance</title>

   <!-- add 'role="editor"' below for the editors if appropriate -->

   <!-- Another author who claims to be an editor -->
  <author fullname="Han Liu" initials="LH" role="editor"
           surname="Liu">
     <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>liuhan@tsinghua.edu.cn</email>
       
       <!-- uri and facsimile elements MAY also be added -->
     </address>
   </author>
   <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="Chengyuan Zhang" initials="ZCY" 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>chengyua21@mails.tsinghua.edu.cn</email>
       
       <!-- uri and facsimile elements MAY also be added -->
     </address>
   </author>

   <author fullname="Pardis M Tehrani" initials="PMT" role="editor"
     surname="Zhang">
     <organization>Sunderland University</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Sunderland</city>
         
         <region></region>
         
         <code>SR1 3SD</code>
         
         <country>UK</country>
       </postal>
       
       <phone></phone>
       
       <email>pardis.tehrani@sunderland.ac.uk</email>
       
       <!-- uri and facsimile elements MAY also be added -->
     </address>
   </author>

   <author fullname="Ji Ma" initials="MJ" role="editor"
     surname="Ma">
     <organization>Oxford University</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Oxford</city>
         
         <region></region>
         
         <code>OX1 2JD</code>
         
         <country>UK</country>
       </postal>
       
       <phone></phone>
       
       <email>ji.ma@mansfield.ox.ac.uk</email>
       
       <!-- uri and facsimile elements MAY also be added -->
     </address>
   </author>
   
   <date year="2023" />

   <!-- 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>

   <!-- 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>Cyberspace involves politics, economy, culture, and technology; it engages governments, international organizations, Internet companies, technology communities, civil society, and citizens, forming an integrated, organic body. In a word, cyberspace is the online version of a community with a shared future for mankind. This memo tries to outline a new framework for rule-based international cyberspace governance regime in the context of IPv6 application, which looks into the future international cooperation of cyberspace governance. 
       </t>
   </abstract>
 </front>

 <middle>
   <section title="Introduction">
   	<t>As for governance, cyberspace exhibits complexity. From a technological point of view, cyberspace is layered: it can be roughly divided into the physical layer, the logical layer, and the content layer. From the perspective of governance, these strata are interrelated and interlinked. The difficulty of international governance of cyberspace lies in the disharmony between the logic of technological layering and the logic of governance connectivity.</t>
	  <t>Information technology, however, demarcated the boundaries of governance and coevolves with governance structure. In the IPv4 era, regulations on DNS resource allocation, as the core issue, is characterized by unclear governance subject, weak rules and chaotic mechanism. In the IPv6 era, technological progress has brought new opportunities and new perspectives for improving governance. International cyberspace governance requires the participation of various parties, each performing its own duties and making full use of its capabilities, and making concerted efforts to build a new system of rules.</t>
     <t>This draft tries to outline a new, rule-based international cyberspace governance regime in the context of IPv6 application, which looks into the future international cooperation of cyberspace governance.</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>Data: any electronic or other means of information on the record.</t>
       
    <t>Data Processing: the collection, storage, use, processing, transmission, provision, and disclosure of data.</t>
       
    <t>Data Security: taking the required steps to ensure that data is effectively protected and used lawfully, as well as having the ability to guarantee a continual state of security.</t>
       
    <t>Network Data Processing: the collection, storage, use, processing, transmission, provision, and disclosure of network data. </t>

    <t>Personal Information: a variety of information related to identified or identifiable natural persons recorded mainly in electronic form, not limited to the use of the network generated or processed in the personal information, but does not include the anonymization of the information after processing. </t>
     
    <t>Network Credit: an IP address (hereinafter referred to as the credit subject), in the cyberspace activities to comply with the legal obligations, the state of fulfilling the agreed obligations. </t>

    <t>Network Credit Information: the objective data and information that can be used to identify, analyze and judge the credit status of the credit subject.</t>
   </section>
   
   <section title="General Principles">
    <section title="Purpose">
      <t>In accordance with the basic spirit of the Charter of the United Nations and the fundamental principles of international law, the following rules are formulated so as to safeguard state sovereignty and promote human rights protection in cyberspace, improve the security and credibility of the global Internet and capacities of comprehensive governance, encourage innovation and change in network information technology, industry and applications, and promote, encourage governance in cyberspace sharing and cooperation among countries as well as high-quality Internet development in each country, and to strengthen the orderly open sharing of data resources and the level of information security protection.</t>
    </section>
    <section title="Fundamental Principles and Objectives">
      <t>Cyberspace governance SHOULD follow principles of sovereign equality, peace and cooperation, fairness and justice, openness and inclusiveness, mutual benefit and progress; and SHOULD aim to create a community of common destiny, interests and responsibilities based on mutual political trust, economic integration, and cultural integration, and endeavor to construct a well order in which mankind shares the achievements of global development.</t>
    </section>
    <section title="Respect Sovereignty">
      <t>Governance in cyberspace SHOULD respect the sovereignty of all countries. State sovereignty in cyberspace is independent and equal. Rights of jurisdiction and defense are the embodiments of a country's sovereignty and SHOULD be respected and maintained by all countries. Countries MUST obey the fundamental principles and general rules of international law, refrain from infringing on the sovereignty of other countries through the Internet and interfering in the internal affairs of other countries, and bear the responsibility for prudent prevention and security of cyber activities within the scope of sovereign control.</t>
    </section>
    <section title="Human Rights Protection">
      <t>Governance in cyberspace SHOULD fully protect human rights. Countries SHOULD protect the security of personal information and privacy, and cooperate to combat cyber attacks, cybercrimes and cyber terrorism. They SHOULD guarantee equal access and smooth communication in the Internet, prohibit discrimination and other unreasonable differential treatments. They SHOULD jointly promote the development of Internet infrastructure, ensure the safe flow of data, aim to close the digital divide, and protect and promote the rights and interests of the broadest range of Internet development.</t>
    </section>
    <section title="Rule of Law and Justice">
      <t>All activities and acts in cyberspace MUST comply with the law and MUST NOT contravene the regulations, principles, and basic spirit of international law. Governments SHOULD NOT use their dominating position in the cyber domain in terms of facilities, technology, systems, and data to interfere with other countries' exercise of cyber sovereignty and to pursue cyber hegemony, cyber isolation, and other unfair activities.</t>
    </section>
    <section title="Comity and Reciprocity">
      <t>Countries exercising cyber sovereignty SHOULD follow the principles of self-restraint, comity and reciprocity, so as to reduce friction and confrontation, avoid mutual constraints, and promote economic cooperation and security collaboration.</t>
    </section>
    <section title="Flexible Governance">
      <t>Countries SHOULD strengthen mutual trust, actively collaborate, comprehensively improve Internet governance capacity, cooperate to establish a credit-based flexible governance system, achieve incentives for trustworthiness and constraints for breach of trust, and establish a secure, good faith, and honest cyberspace.</t>
    </section>
    <section title="Capacity Enhancement">
      <t> Governments SHOULD actively engage in dialogues and encourage multi-field, multi-level, and multi-faceted cooperation to improve the overall security and defense capability of the cyberspace, as well as to promote socio-economic development.</t>
    </section>
   </section>

   <section title="Cyberspace Development">
    <section title="Cooperative Development">
      <t>Countries SHALL intensify their cooperation in the fields of information network technology, product and service innovation, and talent training, as well as to collaborate to overcome technical problems that threaten cybersecurity, develop cybersecurity products collaboratively, innovate network economic development models, and build a high-level, high-quality network talent team.</t>
      <t>Countries SHALL encourage collaboration in developing a network security alerting platform and the establishment of a shared security alerting mechanism to compensate for disparities in network management capacities.</t>
      <t>Countries SHALL enhance research and development of inclusive health care, inclusive education, and inclusive network products and services that promote minors' healthy development.</t>
    </section>
    <section title="International Communication Channel">
      <t>Countries SHALL endorse multi-field, multi-level, and multi-faceted exchanges and collaboration, support trade organizations, enterprises, educational and scientific research institutions, relevant professional institutions and personnel of various countries to carry out exchanges and sharing activities on the development and utilization of network data security technologies, and promote education and training on cybersecurity.</t>
    </section>
    <section title="Ensure Multi-Participation">
      <t>Countries SHOULD actively promote the formation of a well environment for governments, enterprises, relevant social organizations, and the public to participate in governance, and promote mutual recognition of cybersecurity and data processing rules and standards made by other countries and international organizations.</t>
    </section>
    <section title="Promote Safe and Orderly Data Flow">
      <t>On the premise of ensuring data security and protecting personal information , privacy rights and interests, countries SHALL promote the safe and orderly flow of data, jointly explore the new growth of data economy, promote the innovation and development of network information technology, and facilitate the establishment of cross-border factor flow rules and risk prevention mechanisms.</t>
    </section>
    <section title="Respecting Patterns of Technological Development">
      <t>Governance in cyberspace SHOULD respect and adapt to the objective patterns of technological development, and promote the coexistence and progress of mankind and technology.</t>
      <t>Countries SHOULD respect the nature of connectivity in cyberspace, maintain the unity of the Internet and avoid fragmentation of the Internet. Countries SHOULD NOT maliciously exclude other countries' suppliers, information technology and products, fiber optic cables and other facilities, nor SHOULD they take advantage of their own technological, economic, or political advantages to unfairly distribute or block important cyber resources and jeopardize the security of global supply chains.</t>
      <t>Countries SHOULD strive to overcome the problems of Internet Protocol Version 4 (IPv4), such as the depletion of network addresses, the difficulty of ensuring service quality, and the inefficiency of transnational collaborative governance, and give full play to the advantages of Internet Protocol Version 6 (IPv6) in network addresses, innovation space and governance, so as to improve the carrying capacity and service level of their own network.</t>
      <t>Countries with technological advantages MAY provide necessary assistance to countries in need.</t>
    </section>
   </section>

   <section title="Cyberspace Security">
    <section title="Network Infrastructure Protection">
      <t>Countries have the right to protect their network infrastructure in accordance with domestic laws. No country, military, government, government-authorized organizations or individuals SHALL attack or damage network infrastructure of other countries.</t>
      <t>An attack on another country's network infrastructure constitutes a violation of that country's sovereignty.</t>
      <t>A state MAY restrict or protect Internet access in accordance with the principle of sovereignty. Access to the Internet does not mean that the country gives up its sovereignty.</t>
      <t>In case of damage, loss of function or data leakage, key information infrastructure that MAY seriously endanger national security and public interests, a country MAY carry out critical measures of protection and defense, and MAY request assistance from other countries when necessary.</t>
    </section>
    <section title="Security of Internet Names and Digital Address">
      <t>Internet root servers, communication protocols and IP addresses and other key Internet resources are global public resources. Countries SHOULD actively promote the fair allocation and management of Internet key resources and the international reform of the Internet name and digital address allocation authority, and effectively improve its representativeness and the openness and transparency of its decision-making and operation.</t>
    </section>
    <section title="Prohibition of Network Eavesdropping">
      <t>Network eavesdropping and wiretapping activities are prohibited among countries. To ensure the safe operation of the Internet in each country, countries have the right to regulate their networks, impose access licenses for unlawful websites, and discontinue providing services to websites that do not conform to management, etc.</t>
    </section>
    <section title="Prohibition of Cyber Attacks and War">
      <t>Launching of cyber attacks and cyber war are prohibited. Consultations, discussions, and other peaceful methods of resolving disputes SHALL be sought first, and if necessary, relevant agencies and organizations established by these rules MAY be requested to collaborate in order to resolve disputes at the minimum cost.</t>
    </section>
    <section title="Teenagers Protection OF Teenagers">
      <t>Countries SHOULD punish according to law the use of the Internet to engage in activities that endanger the physical and mental health of minors, and provide a safe and healthy Internet environment for minors. They SHOULD cooperate to combat Internet use of child pornography and violent crime.</t>
      <t>Where an online data processor processes the personal information or other online data of a minor under the age of 14, it SHALL obtain the consent of the minor's parents or other guardians. Where there are provisions in the domestic laws of each country, such provisions SHALL prevail.</t>
      <t>Cyberspace governance bodies of all countries MAY, in accordance with domestic laws, consciously undertake the obligation to review, screen and intercept content that harms or MAY harm the physical and mental development of minors, and punish the production, dissemination and provider of harmful information according to law. If conditions permit, channels for reporting illegal content SHOULD also be provided to individuals and organizations in their own countries and other countries.</t>
    </section>
    <section title=" Cross-Border Collaboration of Electronic Evidence Retrieval">
      <t>For cybercrimes committed within the territory of a country or against that country, if the law enforcement authorities of that country request the public authorities, enterprises or individuals of another country to provide relevant electronic evidence for assistance, the country requested MAY, in accordance with the provisions of its domestic law, provide necessary assistance on the premise of not harming its national security, public interests and significant rights and interests of individuals.</t>
    </section>
    <section title="Protection of Data Security">
      <t>Data conveying a country's economy, culture, national defense security, and other key public interests, as well as citizens' rights and interests, SHOULD be processed under the premise of data security.</t>
      <t>Data processing activities SHOULD adhere to international treaties, norms, and legal principles, and SHALL NOT jeopardize national security, public interest, or the legitimate rights and interests of citizens of other nations.</t>
      <t>Countries SHOULD urge domestic data processors to consciously assume international and domestic social responsibilities, respect social justice, business ethics and professional ethics, and fulfill the corresponding data security protection obligations in their network data processing activities. </t>
    </section>
    <section title="Protection of Personal Information And Privacy">
      <t>If it is truly necessary for states to collect personal information of citizens of other countries in the course of commercial cooperation, judicial cooperation or other processes, they SHALL do so for clear and reasonable purposes and in accordance with the principles of legality, legitimacy, necessity and good faith. On the basis of obtaining the consent of the relevant subject, the obligation of protection SHALL be properly fulfilled in respect of the collection, storage, use, processing, transmission, provision, disclosure, deletion and other links of personal information. If the country where the data is collected has relevant regulations, such regulations SHALL be complied with.</t>
    </section>
    <section title="Cooperation in Combating Cybercrime and Cyberterrorism">
      <t>Countries SHALL explore to establish a new cybercrime convention that is more inclusive and transparent. To address the new threats posed by new technologies such as artificial intelligence and cloud computing, and to take aim at new forms of complex and diverse cybercrimes and new threats of cyber terrorism, countries SHALL explore to establish a new convention that covers the legitimate appeals and major concerns of all contracting parties, with transparent procedures and reasonable mechanisms.</t>
    </section>
   </section>

   <section title="Credit System for Network Governance Enforcement Mechanism">
    <section title="Network Credit System Construction">
      <t>Countries SHOULD cooperate in establishing a credit system in cyberspace, comprehensively improve the network credit information management capabilities, promote the unification of credit status determination standards, realize credit-based prior risk prevention and security warning mechanism, create a safe and reliable cyberspace for economic development and provide guarantee for economic development and information exchange.</t>
    </section>
    <section title="Credit Status Determination">
      <t>Countries SHALL, in accordance with the principles of legality, objectivity, prudence and relevance, identify the credit status of the credit subject and load it into the credit file according to the network credit information directory and network credit status identification criteria.</t>
      <t>The network credit information directory aims to standardize the credit information included in the scope. The collection of credit information SHALL NOT exceed the scope stipulated in the catalogue of network credit information.</t>
      <t>The standard of network credit status identification aims at standardizing the principle, basis and rating standard of credit status identification and credit file recording. The identification of network credit status and the recording of credit files SHALL strictly comply with the identification standards of network credit status.</t>
      <t>The catalogue of network credit information and the standards for the identification of network credit status SHALL be determined by the countries through consultation. Each country MAY, in accordance with its domestic laws and regulations, compile supplementary catalogues of online credit information and detailed rules on standards for the identification of online credit status applicable to its own country.</t>
    </section>
    <section title="Credit Information Management">
      <t>Countries SHALL establish credit files of credit subjects with a uniform or mutually identifiable logo and open the inquiry portal to member countries within rules stipulated in this Framework Rules. </t>
      <t>Sharing of credit files and other credit information is encouraged.</t>
      <t>Credit exchange of information SHALL respect each country's sovereignty and protect basic human rights, not to jeopardize national security or to breach personal rights to information or privacy.</t>
    </section>
    <section title="Credit Alert Platform">
      <t>Countries SHALL jointly establish a unified credit early alert platform. Countries SHOULD take the initiative to conduct early risk alert on that platform for the credit subjects with serious trust-breaking behaviors in their own countries. If a country finds that a credit subject of another country has committed serious dishonesty, it SHALL submit the relevant information to the credit early warning coordinating body, which SHALL decide to issue the early alert information.</t>
    </section>
    <section title="Creditworthy Incentives and Discipline">
      <t>Countries MAY give incentives to credit subjects with good credit standing in accordance with their domestic laws. Countries MAY, in accordance with their domestic laws, impose credit punishments on credit subjects that break faith. The subject of credit who receives incentives to keep faith and punishments for breaking faith SHALL be recorded in credit files.</t>
      <t>Countries MAY impose restrictions on other countries' seriously dishonest credit subjects, and the restrictive measures SHALL be determined by consensus of all countries through consultation. Binding measures SHOULD NOT violate the Charter of the United Nations and the basic principles of international law.</t>
    </section>
    <section title="Credit Repairment">
      <t>Credit information recorded in error SHOULD be corrected. Countries SHOULD make credit repair legislations, implement credit repair procedures, and provide credit subjects with feedback, complaints, and other forms of relief.</t>
      <t>If the credit information on the  credit alert platform is erroneous, it is the responsibility of the credit warning coordinating agency to fix it. The credit alert coordination body SHALL establish remedies and corrective standards.</t>
    </section>
   </section>

   <section title="Operational Mechanisms for Cooperation in Network Governance">
    <section title="Rulemaking">
      <t>Countries SHOULD actively formulate rules for cyberspace governance that are inclusive, feasible and developable on the basis of respecting cyber sovereignty and consultations on an equal footing.</t>
      <t>Under the guidance of this Framework Rules, countries SHOULD actively formulate rules on cyberspace security, rules on digital economy cooperation, rules on credit information evaluation and sharing, and rules on consultation and mediation of cyberspace disputes.</t>
    </section>
    <section title="Cooperation Platform">
      <t>Countries SHOULD cooperate in establishing a network security alert platform and credit alert platform, and explore for a digital economy cooperation platform and a cyberspace technology research, development and exchange platform.</t>
    </section>
    <section title="Establishing and Cybersecurity Alert Institution">
      <t>Countries SHOULD establish a cybersecurity early warning institutions on the basis of respect for national sovereignty, in accordance with the principles of equality, justice, democracy, openness and scientificity.</t>
      <t>An advisory committee to provide assistance to alert institutions on decision-making SHALL be established. Members of that committee SHALL comprise of Scientific and technological institutes, commercial institutions, other organizations and relevant experts.</t>
      <t>A decision-making committee to exercise final decision-making authority based on advisory opinions SHALL be established. The members of that committee SHALL be composed of governments from all countries.</t>
    </section>
    <section title="Funding">
      <t>The funds required for activities such as the formulation of normative documents, the establishment of platforms and the establishment of institutions under this Framework Rules SHALL be prepared by all countries through consultation in accordance with the principle of equity.</t>
      <t>The share of funds MAY be reasonably adjusted according to the actual situation such as the level of economic development of each country.</t>
    </section>
   </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>
   </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>
