Cosgrid vendor added to mesh-overlay.yml #79
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for zero-trust-network-access ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is the new pull request based on the #77 .
#77 was closed before we gave our explanation. that' s why this new pull request is issued.
@enclave-marc-barry
As per the classification definition listed on https://zerotrustnetworkaccess.info/, our COSGrid MicroZAccess(MZA) has the below key features:
"Agent based architecture. Devices talk directly to one another coordinated by centralised policy-based management. Direct connections between cooperating systems are established using outbound-only traffic and a combination of device and user identity, UDP & TCP hole punching and NAT traversal techniques together create fast, end-to-end encrypted tunnels between connected systems from behind closed firewalls"
MZA Depends on Trust Broker (in our case TURN Mediator)
Offers Mesh connectivity
Can handle East-West traffic
No gateway devices or proxy servers
However, Gateway or Appliance scenario, is where the MZA Software is installed on a linux Server or on a linux based SD-WAN gateway as an extension use case. Not the core use case. Again to clarify, we've extended the mesh overlay concept to Edge devices for service those use cases.
Again, we're very clear that COSGrid MZA belongs to Mesh Overlay Networks given that exhibits all the qualities of
We request you to consider the facts given above on COSGrid MZA architecture, not much on a diagram which could look like SDP to some. To clear the confusion, we have updated the architecture diagram.
Considering, that listing does not amount to certification by you, request you focus on the core character of the product and ignore any enhancements that may prompt you to make other category assumptions. We firmly believe that our architecture belongs to a Mesh Overlay Networks.
It's been more than a year since we raised the pull request, followed up multiple clarifications on this subject. I hope and look forward that you'll accept the pull request.