IETF
6lo
6lo@jabber.ietf.org
Monday, July 20, 2015< ^ >
Room Configuration
Room Occupants

GMT+0
[15:30:55] Meetecho joins the room
[15:40:01] HUB LACNIC Uruguay LACNIC HUB joins the room
[15:44:58] james woodyatt joins the room
[15:46:29] mcr joins the room
[15:46:47] <mcr> hi. I'm remote just finding the right meetecho.
[15:47:18] <Meetecho> http://www.meetecho.com/ietf93/6lo
[15:47:38] Michael Richardson joins the room
[15:48:36] <mcr> got it, I'm in.
[15:48:49] Goeran Selander joins the room
[15:48:54] <Michael Richardson> audio is good!
[15:48:58] <Michael Richardson> (Y)
[15:50:47] <james woodyatt> I am here to bring comments to the mic.
[15:51:29] <mcr> thank you James. I will prefix with mic: if it's not just idle chatter.
[15:51:46] <james woodyatt> I can't seem to get into the Jabber room.
[15:52:11] <mcr> but... you *are* in the Jabber Room?  or is that your connection via Meetecho? Might be handle collision.
[15:52:34] Ines Robles joins the room
[15:52:41] <james woodyatt> Oh... is the Meetecho chat bridged to Jabber? If so, then that's handy.
[15:52:57] <Michael Richardson> yes, IETF standards rule :-)
[15:53:38] <mcr> you can't join the same room with the same handle twice.... if your client, look for the "resource" extra that you can add to make your handle unique in the room.
[15:53:44] Goeran Selander leaves the room
[15:53:46] <Meetecho> yep, the chatroom you see is the Jabber room
[15:53:59] Ines Robles leaves the room
[15:54:38] <james woodyatt> I think I have it figured out.
[15:54:42] Ines Robles joins the room
[15:54:55] Simon Romano joins the room
[15:55:12] <mcr> okay. so Friday/Saturday/Sunday.  
[15:58:55] <Michael Richardson> mic: the weekend after the meeting will be harder to get network support from the IETF secretariat.
[15:59:17] <Ines Robles> ok
[15:59:57] <Michael Richardson> mic: personally, I will be more tired afterwards, and from a family point of view I have to miss Halloween regardless.  I see no advantage to moving to the weekend afterwards, but I will make it either way.
[16:01:39] <Ines Robles> James are you going to mention the mics dialog?
[16:02:26] ob joins the room
[16:02:27] <james woodyatt> Thanks Ines.
[16:03:04] <Ines Robles> ok
[16:15:20] cabo joins the room
[16:15:23] <cabo> http://www.ietf.org/mail-archive/web/6lo/current/msg01155.html
[16:15:52] Robert Cragie joins the room
[16:16:53] <Ines Robles> https://datatracker.ietf.org/liaison/1415/
[16:18:01] rdroms joins the room
[16:20:26] Dave Thaler joins the room
[16:22:01] ob leaves the room
[16:22:52] <cabo> Two mikes are on (red).  Waiting mikes are green. The next waiting mike blinks green.
[16:24:03] Thomas Watteyne joins the room
[16:24:40] <Michael Richardson> mic: are we reserving 255 for a second ESC byte, and if so, would it be worth specifying that up-front?
[16:25:01] <cabo> (No, just as it wasn't worth specifying ESC in 2007)
[16:25:32] <Michael Richardson> I wonder if it might be best o say this now.
[16:25:52] Thomas Watteyne_4876 joins the room
[16:25:57] <cabo> The important thing is that the code point is reserved; how we use it is best defined when we know how we want to use it.
[16:26:03] <Thomas Watteyne_4876> test
[16:26:14] Thomas Watteyne leaves the room
[16:27:15] Thomas Watteyne_4876 leaves the room
[16:27:40] Thomas Watteyne joins the room
[16:27:42] Ines Robles leaves the room
[16:27:59] ludwig.seitz joins the room
[16:28:02] Ines Robles joins the room
[16:30:51] <rdroms> Just to be clear, the proposal is to reserve a second ESC dispatch code, as listed in RFC4944, Fig. 2.  This second ESC dispatch code could be 0x255.
[16:31:51] Thomas Watteyne leaves the room
[16:32:12] Thomas Watteyne joins the room
[16:34:06] ob joins the room
[16:34:31] <mcr> rdroms, I'm saying that you'd have ESC <byte>. And we might have ESC ESC(0x255) <byte2>
[16:35:34] Ines Robles leaves the room
[16:36:46] <cabo> mcr: Yes, but maybe we want to use 16-bit dispatch values after ESC ESC.  Don't define that now.
[16:37:32] <mcr> ah. I don't have a problem with that possibility; I'm saying that therefore we might need to say implementations, if you see ESC ESC(0x255) that you really can't understand it, and you should drop the packet.
[16:37:37] <rdroms> The proposal is ESC<byte> and ESC1<byte>
[16:38:51] <cabo> rdroms: Fine, but a new usage might need to use 2 or more base values; calling all these ESCn is not that meaningful.
[16:39:36] <Thomas Watteyne> I'm missing why we could not chain ESC bytes with the same value as today's ESC byt
[16:39:39] <cabo> But since we haven't exhausted ESC yet, there is no need to define any ESC1 structure (we may still want to reserve another value).
[16:39:43] <rdroms> ESC and ESC1 was just a handy name for now.
[16:39:53] <cabo> You don't want to code numbers in unary code.
[16:39:56] Ines Robles joins the room
[16:41:46] <Michael Richardson> yes, let's adopt this document. I read it this morning.
[16:41:49] <Michael Richardson> hummmmm
[16:42:10] <Ines Robles> ok
[16:42:52] <Michael Richardson> yes, to the Friday deadline on Liason statement.
[16:42:58] <Ines Robles> ok
[16:43:09] ob leaves the room
[16:43:29] <rdroms> I agree with Gabriel that we should just document what is in G.9903/G.9905 now.
[16:43:39] Robert Cragie leaves the room
[16:43:39] <Michael Richardson> thank you!
[16:43:52] <Michael Richardson> enjoy the beer!!!! drink 2-3 for me.
[16:44:02] Michael Richardson leaves the room
[16:44:10] ludwig.seitz leaves the room: offline
[16:44:15] james woodyatt leaves the room
[16:44:29] Thomas Watteyne leaves the room
[16:44:45] Ines Robles leaves the room
[16:45:25] Meetecho leaves the room
[16:48:07] HUB LACNIC Uruguay LACNIC HUB leaves the room
[16:50:21] Simon Romano leaves the room
[16:54:49] Dave Thaler leaves the room
[17:04:28] cabo leaves the room
[17:39:10] cabo joins the room
[17:49:34] mcharlesr joins the room
[17:54:58] cabo leaves the room
[18:10:28] rdroms leaves the room
[18:15:34] mcharlesr leaves the room
[18:15:44] mcharlesr joins the room
[18:36:59] mcharlesr joins the room
[21:13:35] cabo joins the room
[21:23:59] cabo leaves the room
[21:26:22] rdroms joins the room
[21:27:59] rdroms leaves the room
[21:28:31] rdroms joins the room
[21:28:59] rdroms leaves the room
[22:07:46] cabo joins the room
[22:41:36] cabo leaves the room
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!