How to give VNET names:

VNET ID and FQDN (Fully Qualified Domain Name):

In order to use VNET Plus, it is necessary to give a name to each applicable communication device.
FQDN is normally the name given to a server to be used on the Internet.
The FQDN rules ensure that every name is unique throughout the world.
The name given to the VNET Plus device ,that is called VNET ID here, conforms to the FQDN, and the name must end with letters ” .ntm200.com”.
For example, the name of your VNET Plus device is given like below.
VNET Plus name: aaa.acompany.ntm200.com

If the device is a web server, it could already have the FQDN like below.
Web server name: aaa.acompany.co.jp
In that case, you leave the conventional FQDN as it is and simply add a VNET ID.　
If the device is a client, it usually does not have FQDN.
In this case, a VNET ID needs to be given to the client.

When the user enters the VNET ID (aaa.acompany.ntm200.com) and the file name in the URL field of the browser, the contents of the server can be browsed.
In the case where you have been accessing your server by inputting the name reading
http://aaa.acompany.co.jp/document.html
in the case of VNET Plus accessing the same file.
http://aaa.acompany.ntm200.com/document.html

VNET user name:

The "acompany" part of VNET ID is the subdomain name to identify the VNET user.
The representative person of users has to obtain a subdomain name from the "User Registration" tab.
You can decide your favorite domain name as long as it does not overlap with domain names of other VNET users.
The representative person has to assign an VNET ID including the acquired subdomain name to each of the end users.
The aaa part is user specific, and can be further layered like aaa.bbb.

Communication group:

Communication group names are also required for the VNET Plus networks.
At least one group name needs to be assigned to each unit of the VNET Plus devices.
Only the devices having the same group name can communicate with each other.
No special rules exist concerning the group names.
Devices can belong to a number of different groups.

The figure below shows an example of how to get access to the web server in the company from internal and external PCs securely.
The web server can be accessed using either of the traditional name or the VNET ID.
P2P communication security is guaranteed when accessed with the name of VNET ID.
External PCs such as home PCs can get access to the web server in the company by using the VNET ID.
You do not need to be concerned about the existence or non-existence of NATs, and you can access the server with exactly the same way as the PCs in the company.

Development of new communication applications:

You will be able to develop and verify your application on the Internet by taking the following steps.
(1) Build an application on the LAN and verify its operation.
(2) Install the VNET Plus application on each communication device.
Then, it becomes possible for you to migrate to a system with wider areas that straddles over the Internet.
The already proven systems in LAN can also be used as they are.

You should take into account the following matters when developing a new application.
You keep in mind the fact that VNET Plus will remove all network constraints.
What you have to do is just to develop a system that runs on a LAN.
As VNET Plus solves the NAT traversal problem, you can forget about the existence of NATs.
Although there exist technologies called STUN/TURN as a NAT traversal means, you should not use these technologies together with VNET Plus because they compete with the functions of VNET Plus.
Safe operation cannot be guaranteed if the application is designated with the real IP address in mind.　
VNET Plus starts operation by the name resolution protocol based on DNS as a trigger. Thus, the name resolution using LAN broadcasting such as Multicast DNS cannot be used.

Performance:

VNET Plus is equipped with a high communication performance.
In our experiment, the TCP throughput of VNET Plus was measured as follows.
- Linux PC (Core i5, 2.7GHz Ubuntu 20.04LTS): 220Mbps
- Raspberry pi 4 (64bit) : 120Mbps
Measurement conditions:
- 1000BASE-TX wired direct connection
- PC specifications: Core i5, 2.7GHz Ubuntu20.04LTS
- Measurement tool: iperf

If and when the networks in use are switched during the communication, the time required for the resumption of communication is less than 1 second.

Specifications of VNET Plus:

• Communication functions:

  - Unconstrained mutual communications in IPv4 areas without the necessity of being aware of the existence of NATs are possible.
  - Unconstrained mutual communications in the environment of a mixture of the IPv4 / IPv6 networks are possible(under developing).
  - Mobility is possible.

• Communication route:

  - Basically, P2P direct communication route is established. However, communications via TS are established in the following cases.　
  

  • When one device is connected to IPv4 while the other is connected to IPv6.
  • When both end devices are connected under Symmetric NATs.
  • Configuration is based on a special multi-staged NAT.

• Security:

  P2P packet authentication and encryption processes are undertaken.
  (AES CBCmode 256 bit, SHA-256)
  Countermeasures against DoS attacks and those against replay attacks are adopted.
  Communication grouping is realized.
  The encryption keys for communications are kept unknown even to the administrator.
  An extended password method (multi-factor authentication using a random number) is applied.
  

• Scalability:

  Distributed arrangements for TS is adopted.