IETF
roll@jabber.ietf.org
Saturday, January 9, 2016< ^ >
Thomas Watteyne has set the subject to: IETF93 ROLL WG meeting
Room Configuration
Room Occupants

GMT+0
[01:34:04] mcr2 leaves the room: Disconnected: Replaced by new connection
[01:34:04] mcr2 joins the room
[03:49:40] Michael Richardson joins the room
[11:36:01] eintopf joins the room
[11:36:05] <eintopf> hi mcr
[11:38:45] <eintopf> too much party, yesterday :(
[11:39:05] <eintopf> but I need some context switch to making linux things
[12:13:12] <eintopf> http://wpan.cakelab.org/doc/aring_poster.pdf
[12:13:46] <eintopf> This is my poster for my study work with stateful compression.
[12:14:47] <eintopf> maybe you can take a fast look and can say if this makes sense or not sense
[12:17:39] <eintopf> it's first draft, I will broadcast it on several ways when it will be printed
[12:36:51] <eintopf> and I will send the last RFC
[12:37:00] <eintopf> for supporting stateful compression
[12:38:12] <eintopf> but for radvd, I could try to send it mainline to radvd... it supports more than the actual state. But I asking myself is "radvd" right here when context information is also used in RPL and you want to put RA handling inside unstrung.
[14:09:39] Michael Richardson leaves the room: Disconnected: No route to host
[14:26:27] eintopf leaves the room: Disconnected: closed
[14:28:03] Michael Richardson joins the room
[15:08:07] Michael Richardson leaves the room: Disconnected: closed
[16:41:11] eintopf joins the room
[17:09:30] Michael Richardson joins the room
[17:12:37] <eintopf> ping!
[19:16:59] eintopf leaves the room: Disconnected: closed
[20:31:35] <Michael Richardson> pong?
[20:31:47] <Michael Richardson> looking at your poster.
[20:34:31] <Michael Richardson> your poster looks all factually correct.  I think it has too many words, too many sentences... I think in the poster context, that explaining what 6C0 in a diagram would be better than the text in the Introduction.
[20:36:09] <Michael Richardson> i think the space for DAM/SAM is not a good use of space... instead draw a picture of an IPv6 packet, show it being compressed, and the DAM/SAM pointers indexing into the figure 4 table... i.e. on the whole, I suggest fewer words, and more pictures...
[20:37:03] <Michael Richardson> I haven't gotten back to the radvd / RPL situation yet... I think that a node running unstrung will *NOT* run radvd on those interfaces at all. ..
[20:37:21] <Michael Richardson> how big will the poster be?  50cm x 1m or something?  or A4 sized?
[21:22:12] eintopf joins the room
[21:23:09] <eintopf> thanks for the mail!
[21:23:25] <eintopf> yes, it's too many texts...
[21:26:28] <eintopf> (. I think that a node running unstrung will *NOT* run radvd on those interfaces at all. ...) Okay, I can understand that. I will explain the situation to the visitors and will say the radvd shows hat it's working only. The "Router Advertisment Daemon" in "Concept" can replaced by any other userspace software which handles RA messages
[21:26:42] <eintopf> (how big will the poster be?): A0
[21:27:05] <eintopf> and my professor gave me a pptx file only, I redraw the complete poster template in tex
[21:28:59] <eintopf> I will try draw a new picture, what you suggest in the mail. Deadline is at 18th January but need to do a lot of other stuff :-)
[22:02:04] <eintopf> s/try draw/try to draw/
[22:43:10] eintopf leaves the room: Disconnected: closed
[23:44:10] <Michael Richardson> the radvd would be useful for anything running mesh-under... of course we have no *devices* that do that, but actually odds are they would be some kind of microcontroller attached by USB...
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!