CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Collier-Brown <davecb@spamcop.net>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] missing part of section 6.2 of draft-nichols-tsvwg-codel-02, (Kathleen Nichols)
Date: Wed, 12 Mar 2014 20:23:03 +0000	[thread overview]
Message-ID: <CAA93jw4kp9ChCaybjbVQ17zO_zO18ecS8O4G53StieV0HtBDXw@mail.gmail.com> (raw)
In-Reply-To: <5320BF5B.2090303@rogers.com>

[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]

On Mar 12, 2014 1:11 PM, "David Collier-Brown" <davec-b@rogers.com> wrote:
>
> [Off-topic]
> Someone with classic-typesetting-tools experience might wish to
> volunteer a pandoc-based process. See, for example,
> http://lwn.net/SubscriberLink/589196/0e8f212d7a59f556/

The fq codel rfc was written in pandoc, and converted via pandoc2rfc. The
raw texts are managed in git and in github.

It took me a year of fiddling to get to acceptable output from this.

The amount of effort required was comparable to getting a paper formatted
for the IEEE with TeX, with far less pleasing results than TeX.

Certainly you have to be committed if you want to write an rfc. The present
process is a major barrier to entry.

>
>  --dave
>
>
> On 03/12/2014 03:00 PM, codel-request@lists.bufferbloat.net wrote:
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 11 Mar 2014 15:32:29 -0700
> > From: Kathleen Nichols <nichols@pollere.com>
> > To: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
> > Subject: [Codel] missing part of section 6.2 of
> >       draft-nichols-tsvwg-codel-02
> > Message-ID: <531F8EFD.5010807@pollere.com>
> > Content-Type: text/plain; charset=windows-1252
> >
> >
> > It has come to my attention that part of section 6.2 of the draft is
> > missing, apparently due
> > to passing through several programs in order to conform to the holy
> > Internet Draft format.
> > Since the missing part is quite interesting, here it is.
> >
> > When people without time to mess around with this archaic stuff stop
> > doing Internet Drafts, the IETF will then only have drafts by people
> > with time to mess around with this
> > archaic stuff.
> [snip]
>
> --
> David Collier-Brown,         | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net           |                      -- Mark Twain
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel

[-- Attachment #2: Type: text/html, Size: 3185 bytes --]

  reply	other threads:[~2014-03-12 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1394650801.32519.codel@lists.bufferbloat.net>
2014-03-12 20:11 ` David Collier-Brown
2014-03-12 20:23   ` Dave Taht [this message]
2014-03-12 21:32     ` David Collier-Brown
2014-03-13  8:32     ` Eggert, Lars

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw4kp9ChCaybjbVQ17zO_zO18ecS8O4G53StieV0HtBDXw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=davecb@spamcop.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