Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Assessment
Workspace Domino
Categories Administration
Created by Guest
Created on Nov 9, 2019

Implement and document NRPC so we can have SNI for Domino NRPC

Modern protocols running on TLS have SNI capability (Server Name Indication).
 
We need to have the same capability for Domino NRPC.
 
Use case:
To have a single public IP listening 1352 and based on the server the client is requesting being connected to a different backend server.
 
We investigated this and NRPC is already passing the target server name in the TCP connection to servers.
 
We can implement this kind of dispatcher with HAProxy or similar proxy but the NRPC protocol needs to be documented at least to figure out how to reliably match the server name.
 
Is HCL willing to support this. This is really important for efficience if the number of domino server for an org get to grows (and even more for cloud providers).
 
Something like this should already have been implemented for IBM SmartCloud Notes. This would make sense as a general capability for customers / partners.
  • Attach files
  • Guest
    Reply
    |
    Nov 15, 2019

    I like this idea. This is already available for Notes clients to get to internal Domino servers via the Passthru Use feature. You set up the external server through the corp firewall and then allow that first server to be a pass-through to the other back-end servers who are set-up to be allowed for pass-through destinations. It's on the right side of the Security tab of a all the Server documents.  It is very easy to set-up and work great. Most of our mid-sized customers use this feature.

  • Guest
    Reply
    |
    Nov 12, 2019

    Agreed.  We need to move away from endpoints needing to know the exact details of how the back-end is architected and how it changes over time.

    The Notes client, for example, should never have to know anything more then this is where I go to find my "cluster".  The server it ultimately gets directed to should be sorted dynamically behind the scenes.

  • Guest
    Reply
    |
    Nov 10, 2019

    This idea is very useful in the field of cloud hosting and docker. It allows automated and agile creation of Domino servers.

    If, at the same time Notes would run in a browser (WebAssembly), there would be agility throughout the whole stack.

    This feature is a quite important future-enabler.

    [Toni Feric, Belsoft Collaboration]

  • Guest
    Reply
    |
    Nov 9, 2019

    Makes a lot of sense and is really important, also for Docker deployments!
    Domino on Docker is one of the view applications that needs a separate IP, which is really a road-blocker in Docker infrastructure.

    [ Daniel Nashed / http://blog.nashcom.de ]