From: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
To: Andy Grover <andy.grover@oracle.com>
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: Wed, 11 Mar 2009 01:04:28 +0100 [thread overview]
Message-ID: <7iprgolyb7.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <49B6F348.8010507@oracle.com> (Andy Grover's message of "Tue\, 10 Mar 2009 16\:10\:00 -0700")
Thanks for your reply, Andy.
>> I've tried searching the web, and I cannot find a freely available
>> protocol specification.
> Look in net-next tree, Documentation/networking/rds.txt.
I cannot find a protocol description, let alone a full specification, in
this document.
>> I am wondering whether we wish to encourage the use of proprietary
>> (undocumented) protocols,
> I thought "rough consensus and running code" was the IETF credo?
I'm not the IETF, but it is my understanding that rough consensus is
achieved by writing protocol specifications, and submitting them as
Internet-Drafts. (While some Internet-Drafts are destined to become
standards track RFCs after IETF consensus has been reached, many are only
submitted in order to stimulate discussion, and some only get submitted so
that they may become Informational RFCs.)
>From what I can gather from the very sparse documentation, RDS in its
current state cannot possibly achieve IETF consensus, for multiple reasons
(many of which I happen to disagree with -- but I'm not the IETF). Still,
if Oracle find it useful, I'd like to see it published as an informational
RFC.
I'd have no objection to RDS being included in the Linux kernel without
IETF consensus, as long as the protocol is fully documented.
> 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?
Andy, please don't bully me.
Juliusz
next prev parent reply other threads:[~2009-03-11 0:04 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
2009-03-11 0:04 ` Juliusz Chroboczek [this message]
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=7iprgolyb7.fsf@lanthane.pps.jussieu.fr \
--to=juliusz.chroboczek@pps.jussieu.fr \
--cc=andy.grover@oracle.com \
--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).