From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Subject: Re: [PATCH v2 net-next 1/3] rds: Changing IP address internal
 representation to struct in6_addr
Date: Fri, 6 Jul 2018 11:25:58 -0400
Message-ID: <20180706152558.GJ30983@oracle.com>
References: <cover.1530086216.git.ka-cheong.poon@oracle.com>
 <693463ed87c5956eed05a6266c4edf354ab3d51a.1530086216.git.ka-cheong.poon@oracle.com>
 <c5d7497c-2761-8941-19df-dcae087d10ce@oracle.com>
 <6a7b0951-d950-1555-a5b2-622d6f7b9f8f@oracle.com>
 <20180706101505.GA32098@oracle.com>
 <64196e9e-bb90-9452-5fbf-2004e2bd68e3@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
        davem@davemloft.net, netdev@vger.kernel.org,
        rds-devel@oss.oracle.com
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from aserp2120.oracle.com ([141.146.126.78]:37000 "EHLO
        aserp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753814AbeGFP0d (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 6 Jul 2018 11:26:33 -0400
Content-Disposition: inline
In-Reply-To: <64196e9e-bb90-9452-5fbf-2004e2bd68e3@oracle.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On (07/06/18 23:08), Ka-Cheong Poon wrote:
> 
> As mentioned in a previous mail, it is unclear why the
> port number is transport specific.  Most Internet services
> use the same port number running over TCP/UDP as shown
> in the IANA database.  And the IANA RDS registration is
> the same.  What is the rationale of having a transport
> specific number in the RDS implementation?

because not every transport may need a port number.

e.g., "RDS over pigeon carrier" may not need a port number.

in a different design (e.g., KCM) the listen port is configurable
with sysctl

Some may need more than one, e.g., rds_rdma, evidently.

What is the problem with using the unused 18635 for the RDS_CM_PORT?