CCNx Extension for Name Resolution Service
draft-hong-icnrg-ccnx-nrs-00

Abstract

This document presents the CCNx extension for Name Resolution Service (NRS). It describes TLV-based CCNx messages for NRS and modification of CCNx forwarder where the messages for NRS are working.

Status of This Memo

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

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

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

This Internet-Draft will expire on May 3, 2018.

Copyright Notice

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

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

Table of Contents

• 1. Introduction
• 2. Conventions and Terminology
• 3. Mappig System for Name Resolution Service in CCN
• 4. CCNx Extension for Name Resolution
• 4.1. Interest
• 4.2. Content Object
• 4.3. Forwarder
• 5. CCNx Extension for Name Management
• 5.1. Interest
• 5.2. Content Object
• 5.3. Forwarder
• 6. IANA Considerations
• 7. Security Considerations
• 8. Acknowledgements
• 9. References
• 9.1. Normative References
• 9.2. Informative References
• Authors' Addresses

1. Introduction

In Information Centric Networking (ICN)[RFC7927], the name resolution is defined as the first step of ICN routing along with content discovery and delivery, which translates a content name to locator(s) of providers/sources that can provide the content. However, the name resolution step can be omitted in the hierarchical name based routing.

NDN [NDN] and CCN [CCN] are representative projects of ICN which use the hierarchical name based routing. Nevertheless, in [Afanasyev], in order to address the routing scalability problem in NDN's DFZ, a distributed mapping system called NDNS was designed, which maintains and lookups the mapping information from a name to its globally routed prefixes. Here, NDNS is a kind of Name Resolution Service (NRS) in NDN.

Similarly, CCN also has a challlenge to address the routing scalability problem in CCN's DFZ even though CCN uses the hierarchical name based routing. Thus, NRS can be utilized in CCN for the scalable name based routing as well as the efficient mobility support.

This document presents the design of NRS-Mapping System (NRS-MS) which is a system that provides the name resolution service in CCN and its implementation by extending CCNx. It also describes TLV-based CCNx messages for NRS and modification of CCNx forwarder where the messages for NRS are working.

2. Conventions and Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

This document uses the terminology of [CCNxSemantics] and [CCNxMessages] for CCNx entities.

The following terms are used in this document and defined as follows:

• Mapping Server (MS) : stores and maintains the actual mapping table which keeps the bindings of name to some information that is used for forwarding Interest. MS is a role of NRS resolver and all NRS messages are processed though the MS. In other words, CCN nodes such as consumer, provider communicate with only MS to get the name resolution service. Thus we design the MS using C CN protocol assuming that the NRS is served at the content router (CR) and each CR knows its default MS.
• Name List Server (NLS) : is constructed by the DNS-like tree according to the name hierarchy. NLS is only used to find the corresponding MS which stores the binding information of the requested name since CR sends the NRS lookup request to its default MS whether it has the binding information of the requested name or not. MS is located at the second level NLS and we have utilized the IP for the communications between MSs and NLSs.

3. Mappig System for Name Resolution Service in CCN

This document presents the new implementation of NRS-MS functions based on extension of CCNx to show usefulness of NRS in CCN. We design a simple scenario to maximize NRS usefulness and to understand NRS functionalities easily.

• Scenario : Similar with CDN approach, multiple media servers containing popular contents can be deployed in different areas, but all of media data in replica servers (RSs) must have equivalent name to keep data integrity as one publisher's authority. In order to take an advantage from the replica servers, NRS can be utilized to lookup the physical locations of the rplica servers. The nearest replica server can be chosen from the information resolved by NRS.
• Design choices : We design and implement a new entity named a Mapping Server (MS) by extension of content router (CR). The MS can be deployed by single network provider. Moreover, we assume that an ICN edge domain is required to have at least one MS. MS maintains mapping information between name and another name and processes a lookup request and its response. Consumer is not changed. The first hop content router (CR1) like a first hop router should have a communication channel toward a mapping server. We design new messages to implement NRS functionalities just by following the CCNx messages in TLV format [CCNxMessages] by extension of optional fields.

                                       
                  +-----+                
                  | MS  |
                  +-----+
                     | 
                     |     
   +----------+   +-----+   +-----+   +-----+
   | Consumer |---| CR1 |---| CR2 |---| RS1 |
   +----------+   +-----+   +-----+   +-----+
                        \
                         \
                        +-----+   +-----+    
                        | CR3 |---| RS2 |
                        +-----+   +-----+ 
         
       

Figure 1: Replica server scenario

4. CCNx Extension for Name Resolution

We have implemented the NRS for CCN based on CCNx. This means that the name is resolved by Interest and Content Object packets defined in CCNx. We define two types of Interest packets for NRS: Interest for registration (I-reg) and Interest for lookup (I-get) which are sent from a proper CR to its default MS for name registration and lookup, respectively. We also define two types of Content Object (CO) packets: CO-reg and CO-get which are corresponding to the I-reg and I-get, respectively. We have utilized the nested header format used in CCNx [CCNxMessages] to enable the newly defined packets.

4.1. Interest

I-get is an Interest packet requesting the name resolution. It has the name of MS first where it needs to be sent.

                    
                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1    
   +---------------+---------------+---------------+---------------+
   |    Version    |  PT_INTEREST  |         PacketLength          |
   +---------------+---------------+---------------+---------------+
   |   HopLimit    |   Reserved    |     Flags     | HeaderLength  |
   +---------------+---------------+---------------+---------------+  
   |    MessageType, T_NAME        |         MessageLength         |
   +---------------+---------------+---------------+---------------+
   |                       Name TLV (MS Name)                      |
   +---------------+---------------+---------------+---------------+
   |    MessageType, T_GET         |         MessageLength         |
   +---------------+---------------+---------------+---------------+
   |                     Name TLV (requested Name)                 |
   +---------------+---------------+---------------+---------------+      
       
       

Figure 2: Interest packet format for name resolution request

[TBD]

4.2. Content Object

CO-get is a Content Object packet replying to the name resolution request, I-get.

                    
                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1    
   +---------------+---------------+---------------+---------------+
   |    Version    |  PT_CONTENT   |         PacketLength          |
   +---------------+---------------+---------------+---------------+
   |            Reserved           |     Flags     | HeaderLength  |
   +---------------+---------------+---------------+---------------+  
   |    MessageType, T_NAME        |         MessageLength         |
   +---------------+---------------+---------------+---------------+
   |                       Name TLV (requested Name)               |
   +---------------+---------------+---------------+---------------+
   | MessageType, T_PAYLDTYPE_GET  |         MessageLength         |
   +---------------+---------------+---------------+---------------+
   |                       Name TLV (acquired Name)                |
   +---------------+---------------+---------------+---------------+      
       
       

Figure 3: Content Object packet format for name resolution request

[TBD]

4.3. Forwarder

Forwarder has been modified to make the I-get and CO-get working properly. PIT is updated by the resolution requesting name.

[TBD]

5. CCNx Extension for Name Management

[TBD]

5.1. Interest

[TBD]

5.2. Content Object

[TBD]

5.3. Forwarder

[TBD]

6. IANA Considerations

There are no IANA considerations related to this document.

7. Security Considerations

[TBD]

8. Acknowledgements

[TBD]

9. References

9.1. Normative References

9.2. Informative References

Authors' Addresses