Why do we need a new protocol?

Businesses are loosing $1 Trillian per year because of security issues.

Technology needs to evolve to meet the needs of IT and IoT. A new approach is required so that:

    • TCP/IP is not secure.

    • Security becomes impenetrable with monitored, issue resolution and accountability.

    • Security works for both IT implementations and IoT implementations.

    • Businesses need to be able to easily create relationships with suppliers, partners, resellers, support providers and clients seamlessly. Sometimes relationships need to be created to meet short term or temporary needs.

    • The barriers between device ownership, operations, management and support need to blur to have a more flexible sharing of information and operations.

    • A business's service and support vision needs to be supported by the infrastructure to realize the opportunities offered in a networked world.

    • People need privacy and security of information.

What are the problems with our existing protocol and infrastructure?

Current systems are failing to meet the needs of society. In the big picture:

  • Security - does not work

  • Privacy - does not exist

  • Accountability - does not exist

  • Control - is limited

We all know (technologists) that TCP/IP needs to be replaced.

Specific issues:

    • Routing systems are not secure therefore path validation and operational integrity is not ensured.

    • DDOS attaches are not easily mitigated, there is no accountability and no sender identification.

    • Not designed for critical realtime data.

    • more details are listed below.

Why did you choose the name Secure Relationship Protocol?

Secure Relationship Protocol (SRP) was chosen because it best describes the needs of a new infrastucture.

  • Relationships are core to society.

  • Sharing is core to relationships.

Relationships and sharing of information, devices and operations must be core to a new protocol so that technical and businesses solutions work together.

What is the mission of SRP?

Business Vision:

Businesses need the freedom to safely create relationships, perform transactions and share information with others.

Privacy Vision:

We need an infrastructure to support freedom to choose with whom they share information and interaction without fear of theft or loss of privacy and information.

What are the technical needs to make RSP work?

Relationship Management in central to the all operations both technical and operational. The following exaples illustrate the issue:

    • Relationships define operations between: Nodes, Devices, Connection, Information, Ownership, Messaging/Telemetry

    • Relationships exist between owners, users, devices and information.

    • Ownership is a central to systems operations.

    • Businesses own devices and have users.

    • Businesses define rights to access, operation and management devices by users and businesses.

    • Individuals are entities who have information and resources.

    • SRP is self securing and self managed infrastrastructure

Who is driving this initiative ahead?

Smart Talk Beacon Solutions Ltd. is promoting this project. It is our belief that system security risks such as intrusions, malware and monitoring represent a great risk that needs to be resolved for the benefit of everyone.

A new infrastructure is required to protect businesses and users (everyone) from theft of information and resources. Privacy as defined by ownership for businesses and individuals is a right as defined by the GDPR and CCPA, at minimum, is required for business and social development.

What terms would you use to describe the Secure Relationship Protocol?

The best term is an "Infrastructure as a Shared Service".

What is the basis of this new protocol?

Smart Talk Beacon Solution has developed a protocol that works. Over the last 5 years, we have developed 4 version of Beacon. Beacon is a software defined network designed to operate, manage and support IoT devices. In the process of developing Beacon, we develop a security solution called "No Trust Security" to support:

  • Edge computing

  • Distributed computing

  • Peer device operations

  • Monitoring and analysis

  • Support services

The result has been insights into the replacement requirements for TCP/IP.

Beacon is a high security implementation to ensure intrusions and bad behavior is detected, identified, reported and mitigated.

No Trust security is unique employing multiple layers or types of security in a monitored environment or infrastructure. The infrastructure is managed therefore can adapt and adopt new solutions if required. The idea of a managed infrastructure is consistant with reuse in cloud implementations, employment of specialized services for security and infrastructure management.

SRP will make the network more powerful and useful by securing, managing and supporting business, users, devices and information operations.

Will the SRP work with TCP/IP?

Various metods for TCP/IP compatability can be utilized. The best method needs to be determined.

When will there be applications available for SRP?

RSP applications will be available based on board and management timelines.

Partners will have the first opportunities related to the development of applications because they will have:

  • Licensing rights

  • Access to new APIs

  • Research information

Where will one acquire SRP?

You will be able to obtain a licence from SRProtocol (owner), a partner or an infrastructure provider based on the service offering you want related to monitoring and support.

Will existing business applications work in SRP?

Applications will continue to work as designed.

Who will have rights to build applications?

All developers will have the right to develop applications. Training related to structure and design issue is TBD.

What will be different related to application development?

Application development will be much different. Functions and repositories are added. Access rights, rights to functions, information rights and visibility will be determined by relationship management.

Rights are no longer restriced to one user or business or location. Rights can be public or private or a combination.

Can you have SRP installed along side of TCP/IP?

Yes, this is a design requirement for the smooth migration from TCP/IP to an SRP infrastructure.

When will SRP be available?

No timeline for availablity is available.

Who will be responsible for the protocol development and business operations?

SRP will be controlled by the partners who support the development of SRP. A board of directors (7 directors) will be established by vote of the partners. Founders will have representation on the board.

    • The board will determine the business parameters of RSP.

    • The board will appoint SRP executives.

    • A technology advisory group of 5 researchers will determine the technical features and development projects for SRP.

Who provides our communication infrastructure today?

Communication infrastructure is provided by telecommunication companies of different sizes.

Who will implement the SRP infrastructure?

Telecommunications companies will benefit from a secure, resilient, safe and reliable infrastructure to improve services for business and local communities.

How much different is SRP from our existing infrastructure operations?

SRP is significantly different both technically and operationally.


TCP/IP is a communication protocol designed to efficiently and reliably manage communications between devices (ultimately users). There is no security and no management tools built into TCP/IP.

SRP will be a comprehensive infrastructure designed to securely manage relationships between legal entities (businesses, people and devices). Entities use SRP by creating accounts, adding users, adding devices and defining relationships. An SRP includes all the components required for secure management and implementation.


A Relationship environment is not restricted by technical barriers. You create relationships based on need.

Bad behavior has consequences. Bad actors will are identified, restricted by peers and in some cases ejected.

What are 3 concept changes unique to SRP? Why do we need them?

The 3 concepts are:

  1. Relationship Management
    Relationship management makes it possible to develop relationships that reflect the real world so that small and large relationships can be developed based on need.

  2. Infrastructure as a Shared Services
    SRP is shared by everyone. As SRP implementation numbers grow, so do the services offered. The infrastructure is common but it supports unique use and functionality.

  3. Management services
    Businesses used managed services to leverage expertise and save money. The problem with our solutions today is the fact that every implementation (including cloud services) are unique. This makes managing services difficult. SRP security and operations will be managed as a shared service removing the complexity of security, operations and management.
    Application development is greatly simplified since core issues such as security, user operations and monitoring are APIs.

Disclaimer: The answers to these questions will change based on business and technical implementation.