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 06:16:57 -0400 [thread overview]
Message-ID: <20180626101657.GA20575@oracle.com> (raw)
In-Reply-To: <43b790c2-8da6-9f18-ae23-ca55388e8b26@oracle.com>
On (06/26/18 13:30), Ka-Cheong Poon wrote:
>
> My answer to this is that if a socket is not bound to a link
> local address (meaning it is bound to a non-link local address)
> and it is used to send to a link local peer, I think it should
> fail.
Hmm, I'm not sure I agree. I dont think this is forbidden
by RFC 6724 - yes, such a packet cannot be forwarded, but
if everything is on the same link, and the dest only has
a link-local, you should not need to (create and) bind
another socket to a link-local to talk to this destination..
> This is consistent with the scope_id check I mentioned in
> the previous mail. If the socket is not bound to a link local
> address, the bound_scope_id is 0. So if the socket is used to
> send to a link local address (which has a non-zero scope_id), the
> check will catch it and fail the call. A new conn should not
> be created in this case.
next prev parent reply other threads:[~2018-06-26 10:17 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 ` kbuild test robot
2018-06-25 13:39 ` [RFC PATCH] rds: rds_rdma_cm_event_handler_cmn() can be static 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 [this message]
2018-06-26 13:02 ` Ka-Cheong Poon
2018-06-26 13:08 ` Sowmini Varadhan
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=20180626101657.GA20575@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).