[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mythtv-dev
Subject:    Re: [mythtv] [mythtv-commits] mythtv/master commit: 45a3bfcd4 by Robert McNamara (rmcnamara)
From:       Derek Atkins <warlord () MIT ! EDU>
Date:       2012-02-08 15:45:13
Message-ID: sjm4nv12ut2.fsf () mocana ! ihtfp ! org
[Download RAW message or body]

Gary Buhrmaster <gary.buhrmaster@gmail.com> writes:

> On Tue, Feb 7, 2012 at 22:40, Jean-Yves Avenard <jyavenard@gmail.com> wrote:
> ...
>> Every public APIs used over a networked protocol use numbers or code.
>
> Actually, not "every"(*), but your point has validity.
>
> Usually, however, those protocols have standards
> documents ("real" or "informational" RFCs).  I
> strongly doubt that anyone really wants to go
> through the full IETF (informational) RFC process
> for MythTV.  The experience can be, let us say,
> interesting.

If there is interest in publishing an Informational RFC there are those
of us who know the process well and can certainly help walk you through
it.

> Gary
>
> (*) Opaque blob fields come to mind.  Some of
>     the XDR fields do also.

-derek, former chair of three different IETF Working Groups

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev
[prev in list] [next in list] [prev in thread] [next in thread]