Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [homenet] draft-chroboczek-babel-doesnt-care-00
Date: Sat, 4 Apr 2015 16:05:07 -0700	[thread overview]
Message-ID: <CAA93jw6ZZ6xLT-1dcN64RU3Ys1g3n18SFhCzkYiP5QL5=zJ6PQ@mail.gmail.com> (raw)
In-Reply-To: <87fv8f4l3g.wl-jch@pps.univ-paris-diderot.fr>

one of the more enjoyable internet drafts I have read lately.




---------- Forwarded message ----------
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Date: Sat, Apr 4, 2015 at 2:52 PM
Subject: [homenet] draft-chroboczek-babel-doesnt-care-00
To: Alia Atlas <akatlas@gmail.com>
Cc: homenet@ietf.org, babel-users@lists.alioth.debian.org


Dear Alia,

[Homenet and babel-users in copy of this mail.]

In a previous conversation, you suggested I write down an applicability
statement for Babel.  However, I got bored in the middle, and ended up
writing this:

  Babel doesn't care.
  https://tools.ietf.org/html/draft-chroboczek-babel-doesnt-care-00

Please don't let the somewhat flippant title put you off -- somewhere
within the verbiage, you will find an applicability statement (in Section
1.1).

For people who are not familiar with Babel, I've done my best to give
a protocol outline in Section 2 that might be easier to digest than RFC
6126.  To my knowledge, there is nothing outright incorrect in this
document, and I've removed almost all the jokes before submitting.

-- Juliusz

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet


-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

           reply	other threads:[~2015-04-04 23:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87fv8f4l3g.wl-jch@pps.univ-paris-diderot.fr>]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw6ZZ6xLT-1dcN64RU3Ys1g3n18SFhCzkYiP5QL5=zJ6PQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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