441 lines
26 KiB
HTML
441 lines
26 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}Pages/meeting54.html{% endblock %}
|
|
{% block content %}<div class="irclog">
|
|
<p>--- Log opened Tue Aug 19 16:56:12 2003</p>
|
|
<p>17:00 -!- logger [logger@anon.iip] has joined #iip-dev</p>
|
|
<p>17:00 -!- Topic for #iip-dev: Weekly IIP development meetings, and other</p>
|
|
<p> conversations among developers are held here.</p>
|
|
<p>17:00 [Users #iip-dev]</p>
|
|
<p>17:00 [ cohesion] [ leenookx ] [ mihi] [ shardy_ ] [ UserXClone]</p>
|
|
<p>17:00 [ Ehud ] [ logger ] [ nop ] [ thecrypto] [ velour ]</p>
|
|
<p>17:00 [ hezekiah] [ lonelynerd] [ Rain] [ UserX ] [ WinBear ]</p>
|
|
<p>17:00 -!- Irssi: #iip-dev: Total of 15 nicks [0 ops, 0 halfops, 0 voices,</p>
|
|
<p>15 normal]</p>
|
|
<p>17:00 -!- Irssi: Join to #iip-dev was synced in 7 secs</p>
|
|
<p>17:00 < hezekiah> Alright! :)</p>
|
|
<p>17:00 < hezekiah> Both loggers are in place. :)</p>
|
|
<p>17:01 < thecrypto> yah!</p>
|
|
<p>17:03 < hezekiah> Hmmm ...</p>
|
|
<p>17:03 < hezekiah> This meeting was supposed to start 3 minutes ago.</p>
|
|
<p>17:03 < hezekiah> I wonder what's up.</p>
|
|
<p>17:04 < thecrypto> well, whose idle</p>
|
|
<p>17:04 < hezekiah> jrand0m's not even online.</p>
|
|
<p>17:04 < hezekiah> nop's been idle 15 minutes.</p>
|
|
<p>17:05 < nop> hi</p>
|
|
<p>17:05 < nop> sorry</p>
|
|
<p>17:05 < nop> I'm super busy at work</p>
|
|
<p>17:05 < mihi> [22:36] * jrand0m is off to dinner but i'll be back within</p>
|
|
<p> the half hour for the meeting</p>
|
|
<p>17:05 -!- jrand0m [~jrandom@anon.iip] has joined #iip-dev</p>
|
|
<p>17:05 < hezekiah> Hi, jrand0m.</p>
|
|
<p>17:05 < nop> hi</p>
|
|
<p>17:05 < nop> ok, here's the thing</p>
|
|
<p>17:05 < nop> I can't be seen on IIP at work right now</p>
|
|
<p>17:05 < nop> so I'll check in with yall later</p>
|
|
<p>17:05 < nop> got slack about it yesterday</p>
|
|
<p>17:05 < nop> so</p>
|
|
<p>17:05 < hezekiah> Bye, nop.</p>
|
|
<p>17:05 < thecrypto> bye</p>
|
|
<p>17:06 < nop> I'll hang in the channel</p>
|
|
<p>17:06 < nop> just won't be obvious :)</p>
|
|
<p>17:06 < hezekiah> jrand0m? Since you do the most talking these days, is</p>
|
|
<p> there anything you want on the agenda for this meeting?</p>
|
|
<p>17:07 < jrand0m> back</p>
|
|
<p>17:08 < jrand0m> ok, the pesto pasta was good.</p>
|
|
<p>17:08 < jrand0m> lemmie pull up the agenda-ish stuff</p>
|
|
<p>17:09 -!- Lookaround [~chatzilla@anon.iip] has joined #iip-dev</p>
|
|
<p>17:09 < jrand0m> x.1) i2cp sdk mods x.2) i2np review x.3) polling http</p>
|
|
<p> transport x.4) dev status x.5) todo x.6) plan for next two weeks</p>
|
|
<p>17:09 < jrand0m> (place x at whatever # in the agenda it fits)</p>
|
|
<p>17:10 < thecrypto> you are the agencda</p>
|
|
<p>17:10 < hezekiah> jrand0m: I don't have anything to say, and nop can</p>
|
|
<p>17:10 < hezekiah> can't talk.</p>
|
|
<p>17:10 < jrand0m> lol</p>
|
|
<p>17:10 < hezekiah> UserX most likely won't be adding anything (he usually</p>
|
|
<p> doesn't), so as far as I'm concerned it's all yours. :0</p>
|
|
<p>17:10 < hezekiah> :)</p>
|
|
<p>17:10 < jrand0m> 'k. we logging?</p>
|
|
<p>17:10 < jrand0m> heh</p>
|
|
<p>17:10 < hezekiah> I'm logging everything.</p>
|
|
<p>17:10 < jrand0m> cool. ok. 0.1) welcome.</p>
|
|
<p>17:10 < jrand0m> hi.</p>
|
|
<p>17:11 < jrand0m> 0.2) mailing list</p>
|
|
<p>17:11 < jrand0m> the list is down atm, back asap. you'll know when it is :)</p>
|
|
<p>17:11 < jrand0m> for the meantime, wiki or use iip to convo.</p>
|
|
<p>17:11 < jrand0m> 1.1) i2cp sdk mods</p>
|
|
<p>17:12 < jrand0m> the SDK has been updated with some bugfixes, plus some new</p>
|
|
<p> things in the spec have been introduced.</p>
|
|
<p>17:12 < jrand0m> I posted to the list yesterday with the info.</p>
|
|
<p>17:13 < jrand0m> hezekiah/thecrypto/jeremiah> any questions on what I posted,</p>
|
|
<p> or thoughts on a plan to implement the changes? (or other alternatives I</p>
|
|
<p> haven't considered?)</p>
|
|
<p>17:13 < hezekiah> I've been running around like the chicken with my head</p>
|
|
<p> cut off getting ready for college.</p>
|
|
<p>17:13 < jrand0m> word, understood.</p>
|
|
<p>17:13 < hezekiah> I had a cursory look at what you wrote, but haven't actually</p>
|
|
<p> looked at the changes to the spec.</p>
|
|
<p>17:13 < jrand0m> we barely have any more of your time left, do we...</p>
|
|
<p>17:13 < hezekiah> Not until I get to college.</p>
|
|
<p>17:14 < hezekiah> Once I do, then I will probably be unheard from for at</p>
|
|
<p> least a week while I adjust.</p>
|
|
<p>17:14 < jrand0m> and once you get there you'll have a lot of settling in to do</p>
|
|
<p> (iirc from when i went to school ;)</p>
|
|
<p>17:14 < jrand0m> heh word.</p>
|
|
<p>17:14 < hezekiah> Then by then, I should be a bit more efficient and have</p>
|
|
<p> more time so I can code.</p>
|
|
<p>17:14 < jrand0m> cool</p>
|
|
<p>17:14 < thecrypto> i'm just doing crypto, so the data structures are my real</p>
|
|
<p> worry, once i have the CTS mode done, i'll go work on that prolly</p>
|
|
<p>17:14 < hezekiah> Anyway, that's my guess.</p>
|
|
<p>17:14 < jrand0m> awesome thecrypto</p>
|
|
<p>17:15 < jrand0m> ok, the good thing is the SDK works perfectly fine (with</p>
|
|
<p> the bugs mihi found being fixed [yay mihi!]) without the update to the spec.</p>
|
|
<p>17:15 -!- arsenic [~none@anon.iip] has joined #iip-dev</p>
|
|
<p>17:16 < jrand0m> ok, on to 1.2) i2np review</p>
|
|
<p>17:16 < jrand0m> anyone read the doc?</p>
|
|
<p>17:16 < jrand0m> ;)</p>
|
|
<p>17:16 < hezekiah> Not I, yet.</p>
|
|
<p>17:16 < hezekiah> As I said, I'm currently a chicken with its head cut off.</p>
|
|
<p>17:17 < hezekiah> BTW jrand0m, it appears you like sending PDF's.</p>
|
|
<p>17:17 < jrand0m> can everyone read openoffice .swx?</p>
|
|
<p>17:17 < hezekiah> I can.</p>
|
|
<p>17:17 < jrand0m> [if so, I'll send swx]</p>
|
|
<p>17:17 -!- abesimpson [~k@anon.iip] has joined #iip-dev</p>
|
|
<p>17:17 < thecrypto> i can</p>
|
|
<p>17:17 < hezekiah> I can't search for text in a PDF with KGhostView.</p>
|
|
<p>17:17 < hezekiah> So that really hurts.</p>
|
|
<p>17:17 < jrand0m> that sucks hezekiah</p>
|
|
<p>17:17 -!- mrflibble [mrflibble@anon.iip] has joined #iip-dev</p>
|
|
<p>17:17 < hezekiah> The linux version of Adobe Acrobat isn't very friendly eiter.</p>
|
|
<p>17:18 < jrand0m> ok, openoffice format it is instead of pdf.</p>
|
|
<p>17:18 < hezekiah> Cool.</p>
|
|
<p>17:18 < jrand0m> um, ok. i2np has a few minor changes to the LeaseSet</p>
|
|
<p> structure (reflecting the i2cp change posted earlier), but other than that,</p>
|
|
<p> largely in place.</p>
|
|
<p>17:19 < hezekiah> jrand0m: Are all these docs in cathedral's CVS?</p>
|
|
<p>17:19 < nop> oh</p>
|
|
<p>17:19 < nop> can I interject</p>
|
|
<p>17:19 < hezekiah> i.e. copies of the PDF files you've been sending to the</p>
|
|
<p> list, etc.</p>
|
|
<p>17:19 < hezekiah> nop: Go ahead.</p>
|
|
<p>17:19 < nop> this is offtopic but important</p>
|
|
<p>17:19 -!- ChZEROHag [hag@anon.iip] has joined #iip-dev</p>
|
|
<p>17:19 < nop> IIP-dev and the mail are kind of screwy right now</p>
|
|
<p>17:19 < hezekiah> I noticed.</p>
|
|
<p>17:19 < nop> so bear with us for a bit</p>
|
|
<p>17:20 < nop> we're trying to get it up and going</p>
|
|
<p>17:20 < nop> but it has spam assassin built in</p>
|
|
<p>17:20 < nop> which is the good news</p>
|
|
<p>17:20 < nop> :)</p>
|
|
<p>17:20 < nop> and a lot of other features</p>
|
|
<p>17:20 < jrand0m> any eta nop for the list?</p>
|
|
<p>17:20 * ChZEROHag pokes his nose in</p>
|
|
<p>17:20 < jrand0m> (i know you're busy, not nagging, just wondering)</p>
|
|
<p>17:20 < nop> hopefully by tomorrow</p>
|
|
<p>17:20 < jrand0m> cool</p>
|
|
<p>17:20 < nop> the mail admin is working on it</p>
|
|
<p>17:21 * hezekiah notes that jrand0m _really_ likes the iip-dev list. ;-)</p>
|
|
<p>17:21 < nop> haha</p>
|
|
<p>17:21 < hezekiah> Go delta407!</p>
|
|
<p>17:21 < nop> anyway</p>
|
|
<p>17:21 < jrand0m> its best to document decisions publicly hezekiah ;)</p>
|
|
<p>17:21 < nop> back to our regularly scheduled meeting</p>
|
|
<p>17:21 < jrand0m> heh</p>
|
|
<p>17:21 -!- nop is now known as nop_afk</p>
|
|
<p>17:21 < hezekiah> jrand0m: So where were we?</p>
|
|
<p>17:21 < jrand0m> ok, to your equestion hezekiah> some are, but the latest</p>
|
|
<p> aren't. I'll switch to placing in the openoffice format.</p>
|
|
<p>17:21 < jrand0m> rather than the pdfs</p>
|
|
<p>17:22 < hezekiah> OK.</p>
|
|
<p>17:22 < hezekiah> It'd be really cool if all the docs were in CVS.</p>
|
|
<p>17:22 < jrand0m> definitely, and they will be</p>
|
|
<p>17:22 < hezekiah> Then I can just update, and I know I have the latest edition.</p>
|
|
<p>17:22 < jrand0m> (there are the three drafts that aren't so far)</p>
|
|
<p>17:22 < hezekiah> (BTW, a little off topic, but is anonymous access to</p>
|
|
<p> cathedral up yet?)</p>
|
|
<p>17:23 < jrand0m> not yet.</p>
|
|
<p>17:23 < jrand0m> ok, by friday, I hope to have another draft of I2NP in</p>
|
|
<p> full form [aka no more ... for the kademlia explanation sections, and sample</p>
|
|
<p> implementation details]</p>
|
|
<p>17:24 < jrand0m> there are no significant changes. just more filling</p>
|
|
<p> clarifying things.</p>
|
|
<p>17:24 < hezekiah> Sweet.</p>
|
|
<p>17:24 < hezekiah> Will there be byte layout for data structures avalible in it?</p>
|
|
<p>17:24 < jrand0m> 1.3) I2P Polling HTTP Transport spec.</p>
|
|
<p>17:24 < jrand0m> no, byte layouts go in the data structures spec, which</p>
|
|
<p> should be converted to the standard format instead of html</p>
|
|
<p>17:25 < jrand0m> (though I2NP already has all the necessary byte layouts)</p>
|
|
<p>17:25 < jrand0m> ((if you read it *cough* ;)</p>
|
|
<p>17:25 < hezekiah> Good.</p>
|
|
<p>17:25 < hezekiah> lol</p>
|
|
<p>17:25 < hezekiah> Sorry about that.</p>
|
|
<p>17:25 < hezekiah> As I said, I've been really busy.</p>
|
|
<p>17:25 < jrand0m> heh no worry, you're heading off to college shortly, you're</p>
|
|
<p> supposed to be partying :)</p>
|
|
<p>17:25 < hezekiah> Partying?</p>
|
|
<p>17:25 < jrand0m> ok, 1.3) I2NP Polling HTTP Transport spec</p>
|
|
<p>17:25 < hezekiah> Hmmm ... I guess I'm just odd.</p>
|
|
<p>17:25 < jrand0m> heh</p>
|
|
<p>17:26 < jrand0m> ok, I tried sending this out earlier, but I'll commit</p>
|
|
<p> it shortly. its a quick and dirty transport protocol fitting in with I2NP</p>
|
|
<p> to allow routers to send data back and forth without direct connections</p>
|
|
<p> (e.g. firewalls, proxies, etc)</p>
|
|
<p>17:27 < jrand0m> I'm *hoping* someone can see how this works and build</p>
|
|
<p> similar transports (e.g. bidirectional TCP, UDP, direct HTTP, etc)</p>
|
|
<p>17:27 -!- mihi [none@anon.iip] has quit [Ping timeout]</p>
|
|
<p>17:27 < hezekiah> Hmmm, well I don</p>
|
|
<p>17:27 < jrand0m> before putting I2NP out for review, we need to include</p>
|
|
<p> sample transports so people can see the full picture</p>
|
|
<p>17:27 < hezekiah> don't think _I'll_ be building any transports soon. ;-)</p>
|
|
<p>17:27 -!- WinBear_ [~WinBear@anon.iip] has joined #iip-dev</p>
|
|
<p>17:27 < hezekiah> TCP is working for Java and Python.</p>
|
|
<p>17:27 < hezekiah> (At least client-to-router is.)</p>
|
|
<p>17:27 < jrand0m> no worry, I'm just putting it out there as a todo for people</p>
|
|
<p> who want to contribute</p>
|
|
<p>17:28 < hezekiah> Right.</p>
|
|
<p>17:28 < jrand0m> right, client-router has different requirements than the</p>
|
|
<p> router-router.</p>
|
|
<p>17:28 < jrand0m> ok, anyway, 1.4) dev status</p>
|
|
<p>17:28 < jrand0m> how we doing with CBC thecrypto?</p>
|
|
<p>17:28 < thecrypto> CBC is committed</p>
|
|
<p>17:28 < jrand0m> w00000t</p>
|
|
<p>17:28 < thecrypto> CTS is almost done</p>
|
|
<p>17:28 < hezekiah> thecrypto: What's CTS?</p>
|
|
<p>17:29 < thecrypto> i just have to figure out how to implement i nicely</p>
|
|
<p>17:29 < jrand0m> cts being cyphertext stealing :)</p>
|
|
<p>17:29 < hezekiah> Ah!</p>
|
|
<p>17:29 < thecrypto> CipherText Stealing</p>
|
|
<p>17:29 -!- WinBear [WinBear@anon.iip] has quit [EOF From client]</p>
|
|
<p>17:29 < jrand0m> did you pull nop's reference on that?</p>
|
|
<p>17:29 < hezekiah> OK. We're using CBC with CTS instead of padding.</p>
|
|
<p>17:29 < hezekiah> Hmm.</p>
|
|
<p>17:29 < thecrypto> basically, it makes the message exaclty right length</p>
|
|
<p>17:29 < jrand0m> is that workable for the python side hezekiah?</p>
|
|
<p>17:29 < hezekiah> I might need to slap the Python crypto lib I'm using upside</p>
|
|
<p> the head to make it us CTS properly.</p>
|
|
<p>17:30 < hezekiah> I've always prefered CTS over padding, but I don't know</p>
|
|
<p> what PyCrypt does.</p>
|
|
<p>17:30 < jrand0m> what can python do out of the box to allow exact message</p>
|
|
<p> size recovery?</p>
|
|
<p>17:30 < thecrypto> all you need to do is change how you process the last</p>
|
|
<p> two blocks</p>
|
|
<p>17:30 < hezekiah> I have a feeling that library is going to get some serious</p>
|
|
<p> rewritting.</p>
|
|
<p>17:30 < hezekiah> jrand0m: The CBC stuff in python is transparent. You just</p>
|
|
<p> send the buffer to the AES objects encrypt function.</p>
|
|
<p>17:31 < hezekiah> It spits out cipher text.</p>
|
|
|
|
<p>17:31 < hezekiah> End of story.</p>
|
|
<p>17:31 < jrand0m> does D(E(data,key),key) == data, byte for byte, exact</p>
|
|
<p> same size?</p>
|
|
<p>17:31 < hezekiah> So if it has the wacky idea of using padding instead of CTS,</p>
|
|
<p> then I might need to get in its guts and fix it.</p>
|
|
<p>17:31 < jrand0m> (regardless of input size?)</p>
|
|
<p>17:31 -!- mihi [~none@anon.iip] has joined #iip-dev</p>
|
|
<p>17:31 < hezekiah> jrand0m: Yes. It should.</p>
|
|
<p>17:31 < jrand0m> hezekiah> if you could look into exactly what algorithm it</p>
|
|
<p> uses to do the padding, that'd be great</p>
|
|
<p>17:32 < hezekiah> Right.</p>
|
|
<p>17:32 * jrand0m is hesitant at requiring a mod to a python crypto lib if</p>
|
|
<p> the lib already uses a standard and useful mechanism</p>
|
|
<p>17:32 < hezekiah> One way or another, CBC with CTS sounds good.</p>
|
|
<p>17:32 < hezekiah> jrand0m: This python crypto lib stinks.</p>
|
|
<p>17:32 < jrand0m> heh 'k</p>
|
|
<p>17:33 < thecrypto> i just have to calculate how to mess with the two blocks</p>
|
|
<p>17:33 < hezekiah> jrand0m: ElGamal will need to be completely rewritten in</p>
|
|
<p> C just to make it fast enough to use.</p>
|
|
<p>17:33 < jrand0m> hezekiah> whats the benchmark for python elg of 256bytes?</p>
|
|
<p> its only done once per dest-dest comm...</p>
|
|
<p>17:34 < jrand0m> (if you know offhand, that is)</p>
|
|
<p>17:34 < hezekiah> I'd have to test it.</p>
|
|
<p>17:34 < hezekiah> Encryption is only a second or two I think</p>
|
|
<p>17:34 < jrand0m> < 5 sec, < 2 sec, > 10 sec, > 30 sec?</p>
|
|
<p>17:34 < thecrypto> i'll prolly do some work with it</p>
|
|
<p>17:34 < hezekiah> Decrypton might be some place between 5 or 10 seconds.</p>
|
|
<p>17:34 < jrand0m> cool.</p>
|
|
<p>17:35 < jrand0m> hezekiah> have you spoken with jeremiah or do you have any</p>
|
|
<p> news about the status of the python client api?</p>
|
|
<p>17:35 < hezekiah> thecrypto: All you should need to do is write a C module</p>
|
|
<p> that works with Python.</p>
|
|
<p>17:35 < hezekiah> I have no clue what he's been up to.</p>
|
|
<p>17:35 < hezekiah> I haven't spoken to him since I got back.</p>
|
|
<p>17:35 < jrand0m> 'k</p>
|
|
<p>17:35 < jrand0m> any other dev status thoughts?</p>
|
|
<p>17:36 < hezekiah> Um, not really from me.</p>
|
|
<p>17:36 < hezekiah> I've already explained my current free time status.</p>
|
|
<p>17:36 < jrand0m> word. understood</p>
|
|
<p>17:36 < hezekiah> My only plans are to get the C API up and the python router</p>
|
|
<p> back up to spec.</p>
|
|
<p>17:37 < jrand0m> 'k</p>
|
|
<p>17:37 < hezekiah> Oh my goodness!</p>
|
|
<p>17:37 < jrand0m> 1.4) todo</p>
|
|
<p>17:37 < jrand0m> si sr?</p>
|
|
<p>17:37 < hezekiah> The Python crypto lib doesn't implement CTS or padding!</p>
|
|
<p>17:37 < hezekiah> I'll have to do that manually.</p>
|
|
<p>17:37 < jrand0m> hmm? it requires data to be mod 16 bytes?</p>
|
|
<p>17:37 < hezekiah> Yup.</p>
|
|
<p>17:38 < jrand0m> heh</p>
|
|
<p>17:38 < jrand0m> oh well.</p>
|
|
<p>17:38 < hezekiah> Currently the Python router uses padding.</p>
|
|
<p>17:38 < jrand0m> ok. here are some oustanding items that need to get done.</p>
|
|
<p>17:38 < hezekiah> I remember that now.</p>
|
|
<p>17:38 < hezekiah> Well, let</p>
|
|
<p>17:38 < hezekiah> let's be frank about one thing.</p>
|
|
<p>17:38 < hezekiah> The Python router is never really meant to be used.</p>
|
|
<p>17:39 < hezekiah> It's primarily meant for me to be very familiar with the</p>
|
|
<p> spec and it also accomplishes something else:</p>
|
|
<p>17:39 < hezekiah> It forces the Java router to comply _exactly_ with the spec.</p>
|
|
<p>17:39 < jrand0m> both very important goals.</p>
|
|
<p>17:39 < hezekiah> Sometimes the Java router doesn't quite comply, and then</p>
|
|
<p> the Python router screams bloody murder.</p>
|
|
<p>17:39 < hezekiah> So it doesn't really need to be fast or stable.</p>
|
|
<p>17:39 < jrand0m> plus I'm not sure it won't ever be used in the sdk</p>
|
|
<p>17:39 < jrand0m> right. exactly.</p>
|
|
<p>17:39 < jrand0m> the python client api is a different thing though</p>
|
|
<p>17:39 < hezekiah> The Python client API on the other hand needs to be decent.</p>
|
|
<p>17:40 < jrand0m> exactly.</p>
|
|
<p>17:40 < hezekiah> But that's jeremiah's problem. :)</p>
|
|
<p>17:40 < hezekiah> I've left that to him.</p>
|
|
<p>17:40 < jrand0m> the SDK local only routers are client dev use only</p>
|
|
<p>17:40 < jrand0m> lol</p>
|
|
<p>17:40 < jrand0m> ok, as I was saying... ;)</p>
|
|
<p>17:40 < hezekiah> ;-)</p>
|
|
<p>17:41 < jrand0m> - we need someone to start working on a small web page</p>
|
|
<p> for i2p that will be used for putting out the various I2P related specs for</p>
|
|
<p> peer review.</p>
|
|
<p>17:41 < jrand0m> I'd like this to be ready before 9/1.</p>
|
|
<p>17:41 < hezekiah> OK. I am stating right now that you don't want me to do that.</p>
|
|
<p>17:41 < hezekiah> I'm not a good webpage designer. :)</p>
|
|
<p>17:41 < jrand0m> nor I, if anyone here has seen my flog ;)</p>
|
|
<p>17:41 < jrand0m> cohesion? ;)</p>
|
|
<p>17:41 < hezekiah> lol</p>
|
|
<p>17:42 < hezekiah> Poor cohesion, always stuck with the dirty work. :-)</p>
|
|
<p>17:42 * cohesion reads the back log</p>
|
|
<p>17:42 < hezekiah> ;)</p>
|
|
<p>17:42 < jrand0m> heh</p>
|
|
<p>17:42 < cohesion> jrand0m: I will do it</p>
|
|
<p>17:42 < cohesion> me@jasonclinton.com</p>
|
|
<p>17:42 < cohesion> send me the specs</p>
|
|
<p>17:42 < jrand0m> 'k, gracias.</p>
|
|
<p>17:42 < jrand0m> the specs aren't all done yet.</p>
|
|
<p>17:43 < jrand0m> but the contents that will need to be there are:</p>
|
|
<p>17:43 < cohesion> well, what you have an what you would like to have put up</p>
|
|
<p>17:43 < jrand0m> -I2CP spec, I2NP spec, Polling HTTP Transport spec, TCP</p>
|
|
<p> Transport spec, Security analysis, Performance analysis, Data structure spec,</p>
|
|
<p> and a readme/intro</p>
|
|
<p>17:44 < jrand0m> (those 7 documents will be in pdf and/or text format)</p>
|
|
<p>17:44 < cohesion> k</p>
|
|
<p>17:44 < jrand0m> barring the readme/intro</p>
|
|
<p>17:45 < jrand0m> I'm hoping that all of those docs will be ready by next week</p>
|
|
<p> (8/26). will that give you enough time to get together a small page for a</p>
|
|
<p>9/1 release?</p>
|
|
<p>17:46 < jrand0m> ok. another thing that will need to come down the pipe is</p>
|
|
<p> an I2P network simulator.</p>
|
|
<p>17:46 < jrand0m> do we have anyone looking for a CS project? ;)</p>
|
|
<p>17:46 < hezekiah> lol</p>
|
|
<p>17:46 < cohesion> jrand0m: yea, that's doable</p>
|
|
<p>17:47 < hezekiah> I'm not for another few years. ;-)</p>
|
|
<p>17:47 < jrand0m> cool cohesion</p>
|
|
<p>17:47 < thecrypto> not for a year</p>
|
|
<p>17:47 * cohesion goes back to work</p>
|
|
<p>17:47 < jrand0m> tnx cohesion</p>
|
|
<p>17:48 < jrand0m> ok, 1.6) next two weeks. on my plate is getting these specs,</p>
|
|
<p> docs, and analysis up. I'll post & commit as soon as I can.</p>
|
|
<p>17:48 < jrand0m> PLEASE READ THE SPECS AND COMMENT</p>
|
|
<p>17:48 < jrand0m> :)</p>
|
|
<p>17:48 < hezekiah> jrand0m: Right. Once I get time, I will start reading. :)</p>
|
|
<p>17:48 < jrand0m> I'd prefer people to post comments to the list, but if</p>
|
|
<p> people want to be anon, send me comments privately and I'll post replies to</p>
|
|
<p> the list anonymously.</p>
|
|
<p>17:49 < hezekiah> (What do you think the eta for OpenOffice files for the</p>
|
|
<p> docs being on CVS is?)</p>
|
|
<p>17:49 < jrand0m> I can commit the latest revs within 10 minutes of this</p>
|
|
<p> meeting being over.</p>
|
|
<p>17:49 < hezekiah> Awesome. :)</p>
|
|
<p>17:50 < jrand0m> ok, thats it for 1.*.</p>
|
|
<p>17:50 < jrand0m> 2.x) comments/questions/concerns/rants?</p>
|
|
<p>17:50 < jrand0m> how's the sdk mod working out mihi?</p>
|
|
<p>17:51 < jrand0m> or anyone else? :)</p>
|
|
<p>17:51 < hezekiah> jrand0m: What is this sdk mod you're talking about?</p>
|
|
<p>17:52 < jrand0m> hezekiah> two bugfixes to the sdk, commited (& posted)</p>
|
|
<p> the other day</p>
|
|
<p>17:52 < hezekiah> Ah</p>
|
|
<p>17:52 < hezekiah> Neato.</p>
|
|
<p>17:52 < jrand0m> (rotate the message IDs, synchronize writes)</p>
|
|
<p>17:52 < hezekiah> Just the java side, or the python side too?</p>
|
|
<p>17:52 < jrand0m> yo no hablo python.</p>
|
|
<p>17:53 < hezekiah> lol</p>
|
|
<p>17:53 < jrand0m> not sure if the bugs exist there. do you rotate message</p>
|
|
<p> ids every 255 messages, and synchronize your writes?</p>
|
|
<p>17:54 < hezekiah> I think the Python router does both</p>
|
|
<p>17:54 < jrand0m> cool.</p>
|
|
<p>17:54 < jrand0m> we'll let you know if it doesn't ;)</p>
|
|
<p>17:54 < hezekiah> What exactly do you mean by "synchronize your writes"?</p>
|
|
<p>17:55 < jrand0m> aka make sure multiple messages aren't written to a client</p>
|
|
<p> at the same time if there are multiple clients trying to send messages to</p>
|
|
<p> it at the same time.</p>
|
|
<p>17:55 < hezekiah> All the data sent over the TCP connection gets sent in</p>
|
|
<p> the order it originated.</p>
|
|
<p>17:56 < hezekiah> So you won't be 1/2 of message A and then 1/3 of message B.</p>
|
|
<p>17:56 < jrand0m> 'k</p>
|
|
<p>17:56 < hezekiah> You'll get message A and then message B.</p>
|
|
<p>17:56 < hezekiah> OK ... if no one else is going to talk, I suggest we</p>
|
|
<p> adjurne the meeting.</p>
|
|
<p>17:56 < mihi> my simple TCP/IP over I2p seems to work...</p>
|
|
<p>17:56 < jrand0m> niiiiice!!</p>
|
|
<p>17:56 * mihi was idling a bit sorry</p>
|
|
<p>17:57 < hezekiah> Anyone else have anything to say?</p>
|
|
<p>17:57 < jrand0m> mihi> so we'll be able to run pserver over that?</p>
|
|
<p>17:57 < mihi> as long as you do not try to create lotas connections at once.</p>
|
|
<p>17:57 < mihi> jrand0m: i guess so - i could ge tgoogle through it</p>
|
|
<p>17:57 < jrand0m> niiiice</p>
|
|
<p>17:57 < jrand0m> mihi++</p>
|
|
<p>17:57 < mihi> jrand0m-ava</p>
|
|
<p>17:57 < jrand0m> so you have an outproxy and an inproxy?</p>
|
|
<p>17:58 < mihi> exactly.</p>
|
|
<p>17:58 < jrand0m> cool</p>
|
|
<p>17:58 < mihi> the destination needs keys, the source generates them on demand</p>
|
|
<p>17:58 * hezekiah hands jrand0m the *baf*er. Smash the thing when you're</p>
|
|
<p> done, man.</p>
|
|
<p>17:58 < jrand0m> right. hopefully co's naming service could help with that</p>
|
|
<p> once its ready.</p>
|
|
<p>17:59 < jrand0m> ok cool. mihi, let me or anyone else know if there's</p>
|
|
<p> anything we can do to help :)</p>
|
|
<p>17:59 < mihi> fix that thing with the 128 msgids or build a better GUARANTEED</p>
|
|
<p> support</p>
|
|
<p>17:59 * jrand0m *baf*s nop_afk over the head for having a real job</p>
|
|
<p>18:00 < mihi> jrand0m: baf abuse costs 20 yodels</p>
|
|
<p>18:00 < jrand0m> lol</p>
|
|
<p>18:00 < jrand0m> better guaranteed support?</p>
|
|
<p>18:00 < jrand0m> (aka better performance than the one described? we'll fix</p>
|
|
<p> that in impl)</p>
|
|
<p>18:00 < mihi> did you test my test case with start_thread=end_thread=300?</p>
|
|
<p>18:01 < mihi> it generates lots of messages in one direction, and that causes</p>
|
|
<p> all msgids to be eaten...</p>
|
|
<p>18:01 < jrand0m> hmm, no, hadn't seen that message</p>
|
|
<p>18:01 < hezekiah> jrand0m: Would it be reasonable to make msgid 2 bytes?</p>
|
|
<p>18:01 * jrand0m tried the 200 / 201, but thats fixed with the latest</p>
|
|
<p>18:01 -!- cohesion [cohesion@anon.iip] has quit [off to the lug meeting]</p>
|
|
<p>18:01 < mihi> which latest?</p>
|
|
<p>18:01 < hezekiah> Then they would have 65535 msgids (if you don't could</p>
|
|
<p> msgid 0)</p>
|
|
<p>18:01 < hezekiah> .</p>
|
|
<p>18:02 < jrand0m> 2 byte message ids wouldn't hurt. I'm comfortable with</p>
|
|
<p> that change.</p>
|
|
<p>18:02 < jrand0m> mihi> the one I mailed you</p>
|
|
<p>18:02 < mihi> if you have a more latest than the one you sent me, send it</p>
|
|
<p> (or give me cvs access)</p>
|
|
<p>18:03 < mihi> hmm, that one fails for me with 200/201 (as well as with 300)</p>
|
|
<p>18:03 < jrand0m> hmm. I'll do some more testing and debugging and mail you</p>
|
|
<p> what I come up with.</p>
|
|
<p>18:03 < mihi> thx.</p>
|
|
<p>18:04 < jrand0m> ok.</p>
|
|
<p>18:04 * jrand0m declares the meeting</p>
|
|
<p>18:04 < jrand0m> *baf*'ed</p>
|
|
<p>18:04 * hezekiah hangs the *baf*er reverantly on its special rack.</p>
|
|
<p>18:05 * hezekiah then spins around walks out the door, slamming it behind</p>
|
|
<p> him. The baffer falls off the rack.</p>
|
|
<p>18:05 < hezekiah> ;-)</p>
|
|
<p>--- Log closed Tue Aug 19 18:05:36 2003</p>
|
|
</div>
|
|
{% endblock %} |