netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Grover <andy.grover@oracle.com>
To: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	RDS Devel <rds-devel@oss.oracle.com>
Subject: Re: RDS: no freely available protocol specification?
Date: Tue, 10 Mar 2009 16:10:00 -0700	[thread overview]
Message-ID: <49B6F348.8010507@oracle.com> (raw)
In-Reply-To: <7i63ihm3pq.fsf@lanthane.pps.jussieu.fr>

Juliusz Chroboczek wrote:
> I am a little worried about the Reliable Datagram Sockets (RDS), which are
> currently in the process of being merged into the kernel.  I've checked the
> latest Interned-Drafts index, I've tried searching the web, and I cannot
> find a freely available protocol specification.  (I've been unable to check
> the documentation section of the oss.oracle.com site, which requires
> a password with no way to register visible to my tired eyes.)

Look in net-next tree, Documentation/networking/rds.txt.

> I am wondering whether we wish to encourage the use of proprietary
> (undocumented) protocols, and I wish that the kernel crowd should really
> try to put some pressure on the Oracle guys to get the RDS protocol spec
> published as an RFC, or at the very least submitted as an Internet Draft,
> before it is released as part of the Linux kernel.

I thought "rough consensus and running code" was the IETF credo? We've
provided running code, some documentation, and an active maintainer and
mailing list. If you're interested in getting an RFC drafted for RDS,
then I invite you to start work on one. I also will accept patches to
improve the documentation.

See how this works?

Regards -- Andy


  reply	other threads:[~2009-03-10 23:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 22:07 RDS: no freely available protocol specification? Juliusz Chroboczek
2009-03-10 23:10 ` Andy Grover [this message]
2009-03-11  0:04   ` Juliusz Chroboczek
2009-03-11  8:02 ` David Miller

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=49B6F348.8010507@oracle.com \
    --to=andy.grover@oracle.com \
    --cc=Juliusz.Chroboczek@pps.jussieu.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.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).