Re: [codec] Summary of codec specification

There been a bit of discussion suggesting that we should put into the draft both the machine readable base 64 version in that is easy to extract, and a version in human readable text that is easy for people to read. This seems like a reasonable idea to me. Just to get a rough idea of what this would look like, I took the current GIT repository and had a look at the code in it. It' a bit over 50k lines including both encoder and decoder. You get 48 lines of real text per page of RFC so the human readable version would be over a 1000 pages. If you take the code, tar it, gzip it, and base64 encode it, you get a bit over 180 pages. This sounds big but given it's some bits on a web server, I don't particularly see any problem with it. I also have no idea how the repository compares to what would be needed to specify the normative parts of the decoder. I may have including in the 50k lines of code all kinds of stuff that was not needed. 

Cullen

On Oct 2, 2010, at 8:28 AM, Cullen Jennings wrote:

> 
> On Oct 1, 2010, at 11:27 AM, Cullen Jennings wrote:
> 
>> 1) The code will be in the appendix of the draft base64 encoded. We can sort out later if it is gziped tar file of whatever but it will be some easy to extract format. This has been done on other documents. I have talked to the AD about this before. I have not talked to RFC Ed but do not foresee any issues there. 
> 
> 
> I'd like to encourage people interested in this point to look at Appendix B of RFC 4474. 
> 
> http://tools.ietf.org/rfc/rfc4474.txt
> 
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec

Re: [codec] Summary of codec specification - Code in RFC