<?xml version="1.0" encoding="US-ASCII"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY rfc1498 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1498.xml">
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc2460 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2460.xml">
<!ENTITY rfc4919 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4919.xml">
<!ENTITY rfc4944 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4944.xml">
<!ENTITY rfc5826 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5826.xml">
<!ENTITY rfc6282 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6282.xml">
<!ENTITY rfc6568 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6568.xml">
  <!ENTITY rfc6775 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6775.xml">
  <!ENTITY rfc6830 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6830.xml">
  <!ENTITY rfc6833 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6833.xml">
  <!ENTITY rfc7252 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7252.xml">
<!ENTITY rfc7228 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7228.xml">
<!ENTITY rfc7428 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7428.xml">
<!ENTITY rfc7668 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7668.xml">
<!ENTITY rfc7927 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7927.xml">
]>
<rfc category="info" docName="draft-hong-icn-metaverse-interoperability-00" ipr="trust200902">

  <?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="no" ?>
  <!-- sort the reference entries alphabetically -->
  <!-- control vertical white space
   (using these PIs as follows is recommended by the RFC Editor) -->
  <?rfc compact="no" ?>
  <!-- do not start each<ul><li></li></ul><ul><li></li></ul> 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 -->

  <!-- ***** 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="ICN for Metaverse Interoperability">ICN Challenges for Metaverse Platform Interoperability</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->
    <!-- Another author who claims to be an editor -->
    <author fullname="Jungha Hong" initials="J." surname="Hong">
        <organization>ETRI</organization>

        <address>
            <postal>
                <street>218 Gajeong-ro, Yuseung-Gu</street>
                <!-- Reorder these if your country does things differently -->
                <city>Daejeon</city>
                <region></region>
                <code>34129</code>
                <country>Korea</country>
            </postal>
            <phone></phone>
            <email>jhong@etri.re.kr</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>


    <date day="21" month="October" year="2024" />
    <!-- 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>ICNRG</area>

    <workgroup>ICN Research Group</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 document explores the potential of Information-Centric Networking (ICN)
        to enhance interoperability between metaverse platforms. ICN's content-centric approach,
        in-network caching, and inherent security features can address key challenges such as scalability,
        low-latency performance, data ownership, and standardization needs. It also identifies these challenges
         and proposes solutions to optimize data sharing, enable efficient content distribution,
         and enforce secure access controls.
       </t>
    </abstract>
  </front>

<middle>

    <section title="Introduction">
            <t>
              The metaverse represents the next evolution of the internet, blending
              virtual and physical worlds to enable rich, interactive experiences
              across various platforms. A critical challenge is achieving interoperability
              among various metaverse platforms to ensure seamless user interactions, asset transfers, and content sharing.</t>
            <t>
              Information-Centric Networking (ICN) offers a promising alternative to
              traditional server-based architectures by focusing on content delivery
              rather than host-based communication. ICN's native support for efficient
              data retrieval, caching, and security could address many of the challenges
              in enabling metaverse platform interoperability.</t>
            <t>
              This document identifies key challenges for ICN in supporting interoperability
              between metaverse platforms and suggests potential solutions to overcome these issues.</t>
      </section>

      <section anchor="sec-MV platform iop">
            <name>Metaverse Platform Interoperability</name>
            <t>
              The metaverse cross-platform interoperability refers to different metaverse platforms'
              ability to interact seamlessly, allowing users to access content, assets,
              and experiences across multiple virtual worlds. This interoperability is
              achieved through the use of open standards and protocols that enable
              communication and data exchange between different metaverse platforms.</t>
            <t>
              Interoperability is important in the development of the metaverse because
              it allows for greater creativity and innovation by enabling developers to
              create and share content across different platforms. It also allows users
              to have a more seamless and cohesive experience, as they can move between
              different virtual worlds without creating new accounts or starting from scratch.</t>
            <t>
              The need for metaverse cross-platform interoperability arises from the
              fact that there are multiple metaverse platforms being developed by
              different companies, each with its own set of rules, protocols, and assets.
              This can create a fragmented metaverse ecosystem, making it difficult for
              users to move between different virtual worlds and for developers to create
              cross-platform applications.</t>
      </section>

      <section title="Service Scenarios of Metaverse Platform Interoperability">
            <t>
              This section describes several considerable service scenarios realized
              by interoperable metaverse platforms.</t>

            <t>
                <list style="symbols">
                    <t>
                      Cross-platform metaverse exhibition: A cross-platform metaverse exhibition provides immersive knowledge that spans multiple metaverse platforms, offering visitors an immersive and enlightening journey. Leveraging advanced technologies, including augmented reality (AR) and virtual reality (VR), attendees can traverse a range of exhibits, interactive installations, and curated digital content. This innovative approach presents a novel way for individuals to immerse themselves in various thematic showcases, irrespective of their physical location.
                    </t>
                    <t>
                      Cross-platform metaverse shopping: In a cross-platform metaverse shopping, users can seamlessly buy, sell, and trade digital assets and/or content across platforms. This interconnected ecosystem allows for broader opportunities and increased versatility in virtual transactions.
                    </t>
                    <t>
                      Cross-platform metaverse co-working: Metaverse co-working entails leveraging metaverse technology to provide virtual co-working services, thereby offering an online work environment while maintaining the offline work environment and eliminating spatial limitations. In other words, it is beyond the typical online work environment of remote work and creates a virtual co-working environment. Users can access the metaverse co-working offices through the metaverse platform and animate their avatars to walk into a co-working office, work in a conference room, give a presentation, and so on. This makes it possible for people to co-work from anywhere, anytime, even if they are in different physical spaces, through the medium of the metaverse.
                    </t>
                </list>
            </t>

      </section>


      <section anchor="sec-icn">
            <name>ICN for Metaverse Platform Interoperability</name>
            <t>Information-Centric Networking (ICN) offers several key strengths that
              make it a promising solution for achieving seamless interoperability between
              diverse metaverse platforms. These strengths address critical requirements
              for efficient, scalable, and secure data sharing in highly interactive virtual environments:</t>
            <t>
              	<list style="symbols">
              		  <t>
                      Content-Centric Communication: ICN fundamentally shifts the network
                      paradigm from host-centric to content-centric communication.
                      In a metaverse, where content (such as 3D objects, avatars, and media)
                      needs to be easily and quickly accessed regardless of its origin,
                      ICN's naming-based approach allows users to retrieve data directly
                      by its name instead of relying on server locations. This content-centric
                      model simplifies data sharing across platforms, enhancing interoperability
                      without relying on centralized infrastructure.</t>

                      <t>
                        Efficient In-Network Caching: One of ICN's primary features is
                        in-network caching, where frequently accessed data can be stored
                        at intermediate nodes closer to users. This reduces latency and
                        minimizes server load, which is crucial for metaverse platforms
                        that involve real-time interactions and require instant access
                        to virtual assets. ICN's caching capabilities improve data
                        delivery performance, particularly when many users in different
                        metaverse platforms access the same content.</t>

                        <t>
                        Seamless Multicast and Broadcast Capabilities: ICN's inherent
                        support for multicast and broadcast communication is highly
                        beneficial in the metaverse. For example, when multiple users
                        interact with the same virtual environment or event, ICN enables
                        the efficient distribution of content to all users simultaneously.
                        This eliminates the need for multiple unicast streams, reducing
                        network congestion and ensuring consistency in shared experiences.</t>

                        <t>
                        Security and Data Integrity: In a decentralized and interactive metaverse, security is paramount. ICN provides security at the content level, meaning that each piece of data is independently secured, regardless of its storage or transmission path. This ensures that sensitive information and virtual assets are protected as they move between platforms, making ICN well-suited for securing cross-platform interactions and transactions.
                       </t>

                      <t>
                        Dynamic and Flexible Data Naming: ICN's use of Named Data Objects (NDOs) allows for flexible and dynamic naming of virtual content. In a metaverse setting, this enables granular control over virtual objects, allowing developers to define specific names and properties for each asset. This flexibility supports complex data interactions and ownership management, which is essential for the interoperability of digital assets across platforms.
                      </t>

                      <t>
                        Scalability and Resilience: Metaverse platforms involve millions of simultaneous users and interactions, creating challenges for traditional host-based networks. ICN's architecture, which focuses on distributing data rather than establishing host-based connections, scales more effectively as the number of users and devices increases. Its distributed nature also enhances resilience, allowing metaverse platforms to continue operating efficiently even under high loads or partial network failures.
                      </t>

                     <t>
                       Decoupling Content from Location: ICN's approach to decoupling content from its storage location provides flexibility in how data is stored, shared, and retrieved. In a metaverse, this decoupling allows different platforms to store and retrieve virtual assets without dependency on a single central server, improving the availability and accessibility of content across various virtual worlds.
                     </t>
               </list>
             </t>

          </section>
  <!--   <t>
							<list style="symbols">
							<t> global scalability of routing </t>
							<t> Producer mobility </t>
							<t> Finding off-path cached objects </t>
							<t> Security of routing information injected from outside the routing system.</t>
							</list>
			  </t> -->

    <section title="ICN Challenges for Metaverse Platform Interoperability">
          <t>
            This section outlines ICN's critical challenges in enabling interoperability between metaverse platforms. Each challenge considers the metaverse's unique requirements and how ICN must adapt to meet those demands.
          </t>
          <section title="Scalability">
            <t>
              The metaverse involves interactions between millions of users simultaneously, often in real time.
              ICN must handle large-scale content distribution without introducing bottlenecks or network congestion.
            </t>
            <t>
              Managing the simultaneous request and distribution of content at scale in dynamic metaverse environments presents a significant challenge for ICN.
            </t>
          </section>
          <section title="Latency and Real-Time Interaction">
            <t>
              Low-latency performance is a fundamental requirement in metaverse applications, where real-time interactions are critical for user experience.
            </t>
            <t>
              While ICN's local caching and content routing reduce data retrieval time, maintaining sub-millisecond latencies for real-time interactions, such as avatar movement and voice communication, remains a challenge.
            </t>
          </section>
          <section title="Security and Privacy">
            <t>
              Metaverse platforms require stringent security and privacy measures to protect user data, digital assets, and interactions. ICN's model of distributing content over a network introduces concerns about unauthorized access and data integrity.
            </t>
            <t>
              ICN needs to implement robust encryption mechanisms, access control policies, and privacy-preserving protocols to ensure that sensitive information remains secure.
            </t>
          </section>
          <section title="Data Ownership and Rights Management">
            <t>
              In the metaverse, digital objects often have complex ownership structures, with different levels of access rights and permissions. ICN must support dynamic and granular rights management, ensuring proper handling of ownership and usage rights across platforms.
            </t>
            <t>
              Managing metadata for digital objects in the metaverse, including tracking ownership, usage, and modification rights, adds complexity to the ICN model.
            </t>
          </section>
          <section title="Interoperability Standards">
            <t>
              For true interoperability, there must be a standardized approach to naming, data formats, and APIs that enable different metaverse platforms to communicate effectively.
            </t>
            <t>
              Managing metadata for digital objects in the metaverse, including tracking ownership, usage, and modification rights, adds complexity to the ICN model.
            </t>
          </section>

    </section>

    <section title="Proposed Solutions for ICN in Metaverse Platform Interoperability">
       <t>
          <list style="symbols">
          <t>
            Adaptive Caching Strategies: Propose methods to optimize ICN's caching mechanisms for the high-volume, dynamic nature of metaverse traffic. These strategies should aim to minimize latency while ensuring that relevant content is cached close to users.
          </t>
          <t>
            Leveraging Multicast and Broadcast: ICN's inherent support for multicast can be used to efficiently distribute content to multiple users in shared virtual spaces. Propose optimizations for using multicast in real-time, interactive environments like the metaverse.
          </t>
          <t>
            Enhanced Security Layers: Recommend implementing advanced encryption techniques, user authentication protocols, and access control mechanisms to safeguard the decentralized nature of ICN in metaverse applications.
          </t>
          <t>
            Rights Management via Named Data Objects: Explore ways to enhance ICN's Named Data Objects (NDOs) to support complex ownership, access control, and rights management for digital assets in the metaverse.
          </t>
          <t>
            Standardizing Interoperability: Suggest developing a set of standardized naming schemes, APIs, and content formats within ICN to facilitate interoperability across diverse metaverse platforms. Collaborating with existing metaverse standards bodies will be critical.
          </t>

        </list>
      </t>

    </section>

    <!--  <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"></xref>.</t>
  -->



<!--
				<t>
          The name resolution in ICN can be performed by consumer, routers, or both. Once it is decided where the name resolution will take place, it has to be considered how the name resolution will be performed.
          The name provided by a consumer might be always resolved to identifiers in a differnet namespace just like a DNS lookup.
          Conversely, an NRS is always needed to map names to a different namespace. </t>
-->


    <section anchor="IANA" title="IANA Considerations">
  		<t>There are no IANA actions required by this document.</t>
  	</section>

    <section title="Security Considerations">
    	<t>
        [TBD]
      </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">

	 		&rfc2119;
	 		&rfc7927;


  <!--
      <reference anchor='RFC8569'>
         <front>
           <title>Content-Centric Networking (CCNx) Semantics</title>
           <author initials='M.' surname='Mosko' fullname='M. Mosko'></author>
           <author initials='I.' surname='Solis' fullname='I. Solis'></author>
           <author initials='C.' surname='Wood' fullname='C. Wood'></author>

           <date month='July' year='2019' />
          </front>
         <seriesInfo name='https://www.rfc-editor.org/info/rfc8569' value='' />
       </reference>

        <reference anchor='RFC8609'>
          <front>
           <title>CCNx Messages in TLV Format </title>
           <author initials='M.' surname='Mosko' fullname='M. Mosko'></author>
           <author initials='I.' surname='Solis' fullname='I. Solis'></author>
           <author initials='C.' surname='Wood' fullname='C. Wood'></author>

           <date month='July' year='2019' />
          </front>
         <seriesInfo name='https://www.rfc-editor.org/info/rfc8609' value='' />
       </reference>

       <reference anchor='RFC9138'>
       	<front>
       	<title>Design Considerations for Name Resolution Service in Information-Centric Networking (ICN)</title>
       	<author initials='' surname='Hong, J. et al.' fullname='J. Hong et al' ></author>
       	<date month='November' year='2021' />
       	</front>
       	<seriesInfo name='https://www.rfc-editor.org/info/rfc9138' value='' />
       </reference>

-->


    </references>



 		<references title="Informative References">

      <reference anchor='FGMV-19'>
            <front>
                <title>ITU FGMV-19: Service scenarios and high-level requirements for metaverse cross-platform interoperability</title>
                <author initials='' surname='' fullname=''></author>
                <date month='December' year='2023' />
            </front>

      </reference>

      <reference anchor='aw-MV-icn'>
            <front>
                <title>Metaverse and ICN: Challenges and Use Cases</title>
                <author initials='C.' surname='Westphal' fullname='C. Westphal'></author>
                <author initials='H.' surname='Asaeda' fullname='H. Asaeda'></author>
                <date month='October' year='2023' />
            </front>
        <seriesInfo name='https://www.ietf.org/archive/id/draft-aw-metaverse-icn-01.txt' value='' />
      </reference>

    <reference anchor='IC-MV'>
    <front>
    <title>Information-Centric Metaverse </title>
    <author initials='G.' surname='Fioccola, G. et al.' fullname='G. Fioccola et al' ></author>
    <date month='July' year='2023' />
    </front>
    <seriesInfo name='https://www.ietf.org/archive/id/draft-fmbk-icnrg-metaverse-01.txt' value='' />
    </reference>


    <reference anchor='Dirk'>
        <front>
          <title>Statement: The Metaverse as an Information-Centric Network</title>
          <author initials='D.' surname='Kutscher, D. et al.' fullname='D. Kutscher et al.'></author>
          <date month='October' year='2023' />
        </front>
        <seriesInfo name='https://dl.acm.org/doi/10.1145/3623565.3623761' value='' />
      </reference>

 <!--
    <reference anchor='Ravindran'>
    	<front>
    	<title>Forwarding-Label support in CCN Protocol </title>
    	<author initials='' surname='Ravindran, R. et al.' fullname='R. Ravindran et al' ></author>
    	<date month='July' year='2017' />
    	</front>
    	<seriesInfo name='draft-ravi-icnrg-ccn-forwarding-label-01' value='' />
    </reference>

    <reference anchor='SAIL'>
          <front>
              <title>FP7 SAIL project.</title>
              <author initials='' surname='' fullname=''></author>
              <date month='' year='' />
          </front>
      <seriesInfo name='http://www.sail-project.eu/' value='' />
    </reference>

    <reference anchor='MF'>
            <front>
                <title>NSF Mobility First project.</title>
                <author initials='' surname='' fullname=''></author>
                <date month='' year='' />
            </front>
        <seriesInfo name='http://mobilityfirst.winlab.rutgers.edu/' value='' />
      </reference>

    <reference anchor='Bayhan'>
    	<front>
    	<title>On Content Indexing for Off-Path Caching in Information-Centric Networks </title>
    	<author initials='' surname='Bayhan, S. et al.' fullname='S. Bayhan et al' ></author>
    	<date month='September' year='2016' />
    	</front>
    	<seriesInfo name='ACM ICN' value='' />
    </reference>

    <reference anchor='CCNxNRS'>
       <front>
          <title>CCNx Extension for Name Resolution Service</title>
          <author initials='' surname='Hong, J. et al.' fullname='J. Hong et al.' ></author>
          <date month='July' year='2018' />
        </front>
        <seriesInfo name='draft-hong-icnrg-ccnx-nrs-02' value=''  />
      </reference>

       <reference anchor='Hong'>
    <front>
    <title>Demonstrating a Scalable Name Resolution System for Information-Centric Networking </title>
    <author initials='J.' surname='Hong' fullname='J. Hong' ></author>
    <author initials='W.' surname='Chun' fullname='W. Chun' ></author>
    <author initials='H.' surname='Jung' fullname='H. Jung' ></author>
    <date month='September' year='2015' />
    </front>
    <seriesInfo name='ACM ICN' value='' />
    </reference>




       <reference anchor='Jung'>
       <front>
          <title>IDNet: Beyond All-IP Network</title>
          <author initials='' surname='Jung, H. et al.' fullname='H. Jung et al.' ></author>
          <date month='October' year='2015' />
        </front>
        <seriesInfo name='ETRI Jouranl' value='vol. 37, no. 5' />
      </reference>


      <reference anchor='Jacobson'>                                                               <front>
          <title>Networking Named Content</title>
          <author initials='V.' surname='Jacobson' fullname='V. Jacobson'></author>
          <author initials='D. K.' surname='Smetters' fullname='D. K. Smetters'></author>
          <author initials='J. D.' surname='Thornton' fullname='J. D. Thornton'></author>
          <author initials='M. F.' surname='Plass' fullname='M. F. Plass'></author>
          <author initials='N. H.' surname='Briggs' fullname='N. H. Briggs'></author>
          <author initials='R. L.' surname='Braynard' fullname='R. L. Braynard'></author>
          <date month='' year='2009' />
         </front>
        <seriesInfo name='ACM CoNEXT' value='' />
      </reference>

      <reference anchor='Baid'>                                                               <front>
          <title>Comparing Alternative Approaches for Networking of Named Objects in the Future Internet</title>
          <author initials='A.' surname='Baid' fullname='A. Baid'></author>
          <author initials='T.' surname='Vu' fullname='T. Vu'></author>
          <author initials='D.' surname='Raychaudhuri' fullname='D. Raychaudhuri'></author>
          <date month='' year='2012' />
         </front>
        <seriesInfo name='IEEE Workshop on Emerging Design Choices in Name-Oriented Networking (NOMEN)' value='' />
      </reference>

      <reference anchor='Bari'>                                                               <front>
          <title>A Survey of Naming and Routing in Information-Centric Networks</title>
          <author initials='M. F.' surname='Bari' fullname='M. F. Bari'></author>
          <author initials='S. R.' surname='Chowdhury' fullname='S. R. Chowdhury'></author>
          <author initials='R.' surname='Ahmed' fullname='R. Ahmed'></author>
          <author initials='R.' surname='Boutaba' fullname='R. Boutaba'></author>
          <author initials='B.' surname='Mathieu' fullname='B. Mathieu'></author>
          <date month='' year='2012' />
         </front>
        <seriesInfo name='IEEE Communications Magazine' value='Vol. 50, No. 12, P.44-53' />
      </reference>

      <reference anchor='Rajahalme'>                                                               <front>
          <title>On Name-based Inter-domain Routing</title>
          <author initials='J.' surname='Rajahalme' fullname='J. Rajahalme'></author>
          <author initials='M.' surname='Sarela' fullname='M. Sarela'></author>
          <author initials='K.' surname='Visala' fullname='K. Visala'></author>
          <author initials='J.' surname='Riihijarvi' fullname='J. Riihijarvi'></author>
          <date month='March' year='2011' />
         </front>
        <seriesInfo name='Computer Networks' value='Vol. 55, No. 4, P. 975-986' />
      </reference>

      <reference anchor='Katsaros'>                                                               <front>
          <title>On Inter-Domain Name Resolution for Information-Centric Networks</title>
          <author initials='K. V.' surname='Katsaros' fullname='K. V. Katsaros'></author>
          <author initials='N.' surname='Fotiou' fullname='N. Fotiou'></author>
          <author initials='X.' surname='Vasilakos' fullname='X. Vasilakos'></author>
          <author initials='C. N.' surname='Ververidis' fullname='C. N. Ververidis'></author>
          <author initials='C.' surname='Tsilopoulos' fullname='C. Tsilopoulos'></author>
          <author initials='G.' surname='Xylomenos' fullname='G. Xylomenos'></author>
          <author initials='G. C.' surname='Polyzos' fullname='G. C. Polyzos'></author>
          <date month='' year='2012' />
         </front>
        <seriesInfo name='Proc.IFIP-TC6 Networking Conference' value='' />
      </reference>

      <reference anchor='ID.Wang'>                                                               <front>
          <title>Namespace Resolution in Future Internet Architectures</title>
          <author initials='J.' surname='Wang' fullname='J. Wang'></author>
          <author initials='S.' surname='Li' fullname='S. Li'></author>
          <author initials='C.' surname='Wetphal' fullname='C. Wetphal'></author>
          <date month='October' year='2015' />
         </front>
        <seriesInfo name='draft-wang-fia-namespace-01' value='' />
      </reference>

      <reference anchor='ID.Zhang'>                                                               <front>
          <title>PID: A Generic Naming Schema for Information-centric Network</title>
          <author initials='X.' surname='Zhang' fullname='X. Zhang'></author>
          <author initials='R.' surname='Ravindran' fullname='R. Ravindran'></author>
          <author initials='H.' surname='Xie' fullname='H. Xie'></author>
          <author initials='G.' surname='Wang' fullname='G. Wang'></author>
          <date month='August' year='2013' />
         </front>
        <seriesInfo name='draft-zhang-icnrg-pid-naming-scheme-03' value='' />
      </reference>


      <reference anchor='D.Zhang'>                                                               <front>
          <title>Routing and Name Resolution in Information-Centric Networks</title>
          <author initials='D.' surname='Zhang' fullname='D. Zhang'></author>
          <author initials='H.' surname='Liu' fullname='H. Liu'></author>
          <date month='' year='2013' />
         </front>
        <seriesInfo name='22nd International Conference on Computer Communications and Networks (ICCCN)' value='' />
      </reference>


      <reference anchor='Sevilla'>                                                               <front>
          <title>iDNS: Enabling Information Centric Networking Through The DNS</title>
          <author initials='S.' surname='Sevilla' fullname='S. Sevilla'></author>
          <author initials='P.' surname='Mahadevan' fullname='P. Mahadevan'></author>
          <author initials='J.' surname='Garcia-Luna-Aceves' fullname='J. Garcia-Luna-Aceves'></author>
          <date month='' year='2014' />
         </front>
        <seriesInfo name='Name Oriented Mobility (workshop co-located with Infocom 2014)' value='' />
      </reference>

      &rfc1498;

      <reference anchor='oneM2M'>
            <front>
                <title>oneM2M Functional Architecture TS 0001.</title>
                <author initials='' surname='' fullname=''></author>
                <date month='' year='' />
            </front>
        <seriesInfo name='http://www.onem2m.org/technical/published-documents.' value='' />
      </reference>

      &rfc7252;

      <reference anchor='ID.Shelby'>
            <front>
                <title>CoRE Resource Directory</title>
                <author initials='Z.' surname='Shelby' fullname='Z. Shelby'></author>
                <date month='March' year='2017' />
            </front>
        <seriesInfo name='draft-ietf-core-resource-directory-10' value='' />
      </reference>


      <reference anchor='CoRE'>
            <front>
                <title>Constrained RESTful Environments, CoRE</title>
                <author initials='' surname='' fullname=''></author>
                <date month='March' year='2013' />
            </front>
        <seriesInfo name='https://datatracker.ietf.org/wg/core/charter/' value='' />
      </reference>


      <reference anchor='Westphal'>                                                       <front>
          <title>An IP-based Manifest Architecture for ICN</title>
                <author initials='C.' surname='Westphal' fullname='C. Westphal'></author>
                <author initials='E.' surname='Demirors' fullname='E. Demirors'></author>
                <date month='' year='2015' />
         </front>
        <seriesInfo name='ACM ICN' value='' />
      </reference>

      <reference anchor='Mosko'>                                                       <front>
          <title>CCNx Manifest Specification</title>
          <author initials='M.' surname='Mosko' fullname='M. Mosko'></author>
          <author initials='G.' surname='Scott' fullname='G. Scott'></author>
          <author initials='I.' surname='Solis' fullname='I. Solis'></author>
          <author initials='C.' surname='Wood' fullname='C. Wood'></author>
                <date month='July' year='2015' />
         </front>
        <seriesInfo name='draft-wood-icnrg-ccnxmanifests-00' value='' />
      </reference>
      -->
  <!--
      &rfc6830;
      &rfc6833;

  -->





  <!--

  <reference anchor='Zhang'>
  <front>
  <title>Named data networking</title>
  <author initials='' surname='Zhang, L. et al.' fullname='L. Zhang et al.'></author>
    <date month='July' year='2014' />
    </front>
    <seriesInfo name='ACM SIGCOMM Computer Communication Review' value='vol. 44, no. 3'   />
      </reference>

      <reference anchor='Zhang2'>
        <front>
          <title>A Survey of Mobility Support in Named Data Networking</title>
          <author initials='Y.' surname='Zhang' fullname='Y. Zhang et al.'></author>
          <date month='' year='2016' />
        </front>
        <seriesInfo name='NAMED-ORIENTED MOBILITY: ARCHITECTURES, ALGORITHMS, AND APPLICATIONS(NOM)' value=''   />
      </reference>



    <reference anchor='Dannewitz'>
    <front>
    <title> Network of Information (NetInf)-An information centric networking architecture </title>
    <author initials='' surname='Dannewitz, C. et al.' fullname='C. Dannewitz et al.' ></author>
    <date month='April' year='2013' />
    </front>
    <seriesInfo name='Computer Communications' value='vol. 36, no. 7' />
    </reference>


  <reference anchor='Seskar'>
        <front>
        <title>MobilityFirst Future Internet Architecture Project</title>
     <author initials='I.' surname='Seskar' fullname='I. Seskar' ></author>
     <author initials='K.' surname='Nagaraja' fullname='K. Nagaraja' ></author>
     <author initials='S.' surname='Nelson' fullname='S. Nelson'  ></author>
     <author initials='D.' surname='Raychaudhuri' fullname='D. Raychaudhurin' ></author>
     <date month='November' year='2011' />
     </front>
     <seriesInfo name='7th Asian Internet Engineering Conference' value='' />
     </reference>

    <reference anchor='Dannewitz2'>
    <front>
    <title>Hierarchical DHT-based name resolution for Information-Centric Networks</title>
    <author initials='C.' surname='Dannewitz' fullname='C. Dannewitz' ></author>
    <author initials='M.' surname='DAmbrosio' fullname='M. DAmbrosio' ></author>
    <author initials='V.' surname='Vercellone' fullname='V. Vercellone' ></author>
    <date month='April' year='2013' />
    </front>
    <seriesInfo name='Computer Communications' value='vol. 36, no. 7' />
    </reference>

    <reference anchor='Vu'>
    <front>
    <title>DMap: A Shared Hosting Scheme for Dynamic Identifier to Locator Mapping in the Global Internet </title>
    <author initials='' surname='Vu, T. et al.' fullname='T. Vu et al' ></author>
    <date month='' year='2012' />
    </front>
    <seriesInfo name='IEEE 32nd International Conference on Distributed Computing Systems' value='' />
    </reference>

    <reference anchor='Hong'>
    <front>
    <title>Demonstrating a Scalable Name Resolution System for Information-Centric Networking </title>
    <author initials='J.' surname='Hong' fullname='J. Hong' ></author>
    <author initials='W.' surname='Chun' fullname='W. Chun' ></author>
    <author initials='H.' surname='Jung' fullname='H. Jung' ></author>
    <date month='September' year='2015' />
    </front>
    <seriesInfo name='ACM ICN' value='' />
    </reference>

    <reference anchor='Ravindran'>
    <front>
    <title>Forwarding-Label support in CCN Protocol </title>
    <author initials='' surname='Ravindran, R. et al.' fullname='R. Ravindran et al' ></author>
    <date month='July' year='2017' />
    </front>
    <seriesInfo name='draft-ravi-icnrg-ccn-forwarding-label-01' value='' />
    </reference>




    <reference anchor='Mosko2'>
    <front>
    <title>Nameless Objects </title>
    <author initials='M.' surname='Mosko' fullname='M. Mosko' ></author>
    <date month='July' year='2015' />
    </front>
    <seriesInfo name='' value='' />
    </reference>                                                                 -->




    </references>

    <section anchor="Acknowledgments" title="Acknowledgements" numbered="false" toc="include">
      <t>
        [TBD]
      </t>
    </section>

</back>
</rfc>                        <!--
 <       </reference>                                                              title>Networking named content</title>          <sInfo name='IEEE Network' value='vol. 30, no. 2' />                                                                                                </reference>                                                                  &id.draft-winter-energy-efficient-internet;
    </reference>                                                                                                                                              &id.draft-cheshire-edns0-owner-option;
    <reference anchor='ITU'>
        <front>
            <title>Resolution 73 - Information and communication technologies and climate change</title>
            <author></author>
            <date month='October' year='2008' />
        </front>
        </reference>

    <reference anchor='EPC'>
        <front>
            <title>The Case for Energy-Proportional Computing</title>
            <author initials='L.' surname='Barroso' fullname='Luiz Andre Barroso'></author>
            <author initials='U.' surname='Holzle' fullname='Urs Holzle'></author>
            <date month='December' year='2007'/>
        </front>
        <seriesInfo name='Proc. IEEE International Conference on Network Protocols (ICNP)' value=''/>
    </reference>

	<reference anchor='GreenSurvey'>
        <front>
            <title>A survey of green networking research</title>
            <author initials='A.P.' surname='Bianzino' fullname='Aruna Prem Bianzino'></author>
            <author initials='C.' surname='Chaudet' fullname='Claude Chaudet'></author>
            <author initials='D.' surname='Rossi' fullname='Dario Rossi'></author>
            <author initials='J.-L.' surname='Rougier' fullname='Jean-Louis Rougier'></author>            <date month='' year='2012' />
        </front>
        <seriesInfo name='IEEE Communications Surveys Tutorials' value='' />
    </reference>

    <reference anchor='EEE'>
        <front>
            <title>802.3az-2010</title>
            <author></author>
            <date month='' year='2010' />
        </front>
        <seriesInfo name='IEEE std' value='' />
    </reference>

    <reference anchor='PROXZZZY'>
        <front>
            <title>ProxZZZy for sleeping hosts</title>
            <author></author>
            <date month='June' year='2012' />
        </front>
        <seriesInfo name='ECMA International' value='ECMA-393' />
    </reference>


    <reference anchor='EEEC'>
        <front>
            <title>Improving the Energy Efficiency of Ethernet-Connected:
			A Proposal for Proxying</title>
            <author initials='B.' surname='Nordman' fullname='Bbuce Nordman'></author>
            <author initials='K.' surname='Christensen' fullname='Ken Christensen'></author>
            <date month='September' year='2007' />
        </front>
        <seriesInfo name='Ethernet Alliance' value='' />
    </reference>


    <reference anchor='NCP'>
        <front>
            <title>A Network Connection Proxy to Enable Hosts to Sleep and Save Energy</title>
            <author initials='M.' surname='Jimeno' fullname='M. Jimeno'></author>
            <author initials='K.' surname='Christensen' fullname='K. Christensen'></author>
	    <author initials='B.' surname='Nordman' fullname='B. Nordman'></author>
	 <date month='' year='2008' />
        </front>
        <seriesInfo name='Proc. IEEE Internat. Performance Computing and Communications Conf' value='' />
    </reference>

    <reference anchor='SKILL'>
        <front>
            <title>Skilled in the Art of Being Idle: Reducing Energy Waste in Networked Systems</title>
            <author initials='S.' surname='Nedevschi' fullname='S. Nedevschi'></author>
            <author initials='J.' surname='Liu' fullname='J. Liu'></author>
			<author initials='B.' surname='Nordman' fullname='B. Nordman'></author>
		    <author initials='S.' surname='Ratnasamy' fullname='S. Ratnasamy'></author>
			<author initials='N.' surname='Taft' fullname='N. Taft'></author>
			<date month='' year='2009' />
        </front>
        <seriesInfo name='Proc. USENIX Symposium on Networked Systems Design and Implementation' value='' />
    </reference>
 -->
