From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Cc: netdev@vger.kernel.org, santosh.shilimkar@oracle.com,
davem@davemloft.net, rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next 2/3] rds: Enable RDS IPv6 support
Date: Tue, 26 Jun 2018 09:08:44 -0400 [thread overview]
Message-ID: <20180626130844.GD20575@oracle.com> (raw)
In-Reply-To: <e390f13d-f45b-9566-63c3-64ed1292da53@oracle.com>
On (06/26/18 21:02), Ka-Cheong Poon wrote:
>
> In this case, RFC 6724 prefers link local address as source.
the keyword is "prefers".
> While using non-link local address (say ULA) is not forbidden,
> doing this can easily cause inter-operability issues (does the
> app really know that the non-link local source and the link
> local destination addresses are really on the same link?). I
> think it is prudent to disallow this in RDS unless there is a
> very clear and important reason to do so.
I remember the issues that triggered 6724. The "interop" issue
is that when you send from Link-local to global, and need forwarding,
it may not work.
but I dont think an RDS application today expects to deal with
the case that "oh I got back and error when I tried to send to
address X on rds socket rs1, let me go and check what I am bound
to, and maybe create another socket, and bind it to link-local"
You're not doing this for IPv4 and RDS today (you dont have to do this
for UDP, afaik)
This is especially true if "X" is a hostname that got resovled using DNS
> BTW, if it is really > needed, it can be added in future.
shrug. You are introducing a new error return.
--Sowmini
next prev parent reply other threads:[~2018-06-26 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 10:38 [PATCH net-next 0/3] rds: IPv6 support Ka-Cheong Poon
2018-06-25 10:38 ` [PATCH net-next 1/3] rds: Changing IP address internal representation to struct in6_addr Ka-Cheong Poon
2018-06-25 13:39 ` [RFC PATCH] rds: rds_rdma_cm_event_handler_cmn() can be static kbuild test robot
2018-06-25 13:39 ` [PATCH net-next 1/3] rds: Changing IP address internal representation to struct in6_addr kbuild test robot
2018-06-25 10:38 ` [PATCH net-next 2/3] rds: Enable RDS IPv6 support Ka-Cheong Poon
2018-06-25 14:52 ` kbuild test robot
2018-06-25 17:03 ` Sowmini Varadhan
2018-06-25 17:43 ` Ka-Cheong Poon
2018-06-25 17:50 ` Sowmini Varadhan
2018-06-25 18:44 ` Santosh Shilimkar
2018-06-26 5:30 ` Ka-Cheong Poon
2018-06-26 10:16 ` Sowmini Varadhan
2018-06-26 13:02 ` Ka-Cheong Poon
2018-06-26 13:08 ` Sowmini Varadhan [this message]
2018-06-27 10:07 ` Ka-Cheong Poon
2018-06-27 10:29 ` Sowmini Varadhan
2018-06-27 20:45 ` Santosh Shilimkar
2018-06-25 10:38 ` [PATCH net-next 3/3] rds: Extend RDS API for " Ka-Cheong Poon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180626130844.GD20575@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=ka-cheong.poon@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.