IETF
JMAP
jmap@jabber.ietf.org
Thursday, March 22, 2018< ^ >
Room Configuration
Room Occupants

GMT+0
[00:23:42] marclaporte leaves the room
[00:24:28] marc.laporte leaves the room
[00:32:44] marclaporte joins the room
[00:33:18] marc.laporte joins the room
[01:02:57] marc.laporte leaves the room
[01:03:13] marclaporte leaves the room
[01:07:39] marclaporte joins the room
[01:08:12] marclaporte leaves the room
[01:13:54] marclaporte joins the room
[01:14:39] marc.laporte joins the room
[01:56:33] marc.laporte leaves the room
[01:56:38] marclaporte leaves the room
[01:56:39] marclaporte joins the room
[02:00:12] marc.laporte joins the room
[02:22:55] marc.laporte leaves the room
[02:23:06] marclaporte leaves the room
[02:23:06] marc.laporte joins the room
[02:23:07] marclaporte joins the room
[02:45:30] marc.laporte leaves the room
[02:45:51] marc.laporte joins the room
[03:05:01] marc.laporte leaves the room
[03:05:06] marclaporte leaves the room
[03:05:07] marclaporte joins the room
[03:05:07] marc.laporte joins the room
[06:24:44] marclaporte leaves the room
[06:24:49] marc.laporte leaves the room
[06:26:44] marclaporte joins the room
[06:26:44] marc.laporte joins the room
[06:47:43] marclaporte leaves the room
[06:47:48] marc.laporte leaves the room
[06:49:06] marc.laporte joins the room
[06:49:07] marclaporte joins the room
[07:06:32] marc.laporte leaves the room
[07:06:32] marc.laporte joins the room
[07:06:44] marclaporte leaves the room
[07:06:57] marclaporte joins the room
[08:22:25] benoitg joins the room
[09:13:42] jeffpc joins the room
[10:00:51] marc.laporte leaves the room
[10:01:14] marclaporte leaves the room
[10:01:16] marc.laporte joins the room
[10:01:33] marc.laporte leaves the room
[10:04:15] marc.laporte joins the room
[10:07:32] marclaporte joins the room
[12:19:10] benoitg leaves the room: Connection failed: connection closed
[13:42:49] benoitg joins the room
[14:25:38] marc.laporte leaves the room
[14:39:14] marclaporte leaves the room
[14:42:24] marclaporte joins the room
[14:43:26] marclaporte leaves the room
[14:55:39] benoitg leaves the room: Connection failed: connection closed
[15:30:57] benoitg joins the room
[15:35:27] meetecho joins the room
[15:41:14] N7XVilai joins the room
[15:45:09] Federico Santandrea joins the room
[15:45:10] Jason Polis joins the room
[15:45:10] Ken Murchison joins the room
[15:46:50] Federico Santandrea leaves the room
[15:48:10] Dave Crocker joins the room
[15:48:28] Sean Leonard joins the room
[15:52:26] Ned Freed joins the room
[15:52:48] Barry Leiba joins the room
[15:55:33] brong joins the room
[16:02:03] <jeffpc> using a domain gets...ugly
[16:02:05] benoitg leaves the room: Stream reset by peer
[16:02:10] <jeffpc> because domain ownership changes
[16:02:36] <jeffpc> iSCSI naming of targets includes a year
[16:02:41] <jeffpc> to avoid this
[16:02:53] <jeffpc> Barry Leiba: ^
[16:03:16] Danny Mayer joins the room
[16:04:07] <jeffpc> is anyone reading jabber?
[16:04:12] <Ned Freed> Yes
[16:04:14] <jeffpc> ok
[16:05:15] Danny Mayer leaves the room
[16:05:28] <jeffpc> https://tools.ietf.org/html/rfc3721#section-1.1
[16:05:32] <jeffpc> turns out it's an RFC
[16:07:28] <Barry Leiba> iSCSI ?
[16:07:33] <jeffpc> yep
[16:07:46] <jeffpc> they need to name targets
[16:07:58] <jeffpc> and they use a URN style - see link
[16:08:05] <Barry Leiba> Ah, right, yes.  Missed your earlier message.
[16:09:52] marclaporte joins the room
[16:10:04] marc.laporte joins the room
[16:11:05] Barry Leiba leaves the room: Disconnected: Replaced by new connection
[16:11:05] Barry Leiba joins the room
[16:13:59] <Sean Leonard> I have some thoughts on URN, I guess will bring up to mailing list. Basically urn:ietf:params:jmap:... is good. The IETF params registry can/should also have a sub-registry for JMAP & capabilities.
[16:14:13] <Sean Leonard> urn: ietf : params : jmap : ... (no emoji)
[16:14:26] <Sean Leonard> will bring up to mailing list, topic already passed in discussion
[16:14:30] <jeffpc> no emoji? that sounds so 90's ;)
[16:14:33] <jeffpc> sounds good
[16:14:50] <Sean Leonard> emoji can be in URNs but have to be % encoded :-P
[16:16:07] <jeffpc> I guess there should be a vendor URN "prefix"
[16:21:22] <Barry Leiba> Yeh, I think it'd be… a poor idea… to put non-ASCII characters in the URNs.  They're protocol elements, not meant to be presented to humans nor internationalized.
[16:21:50] <Barry Leiba> Jeff, would you want the IETF to manage the vendor namespace?
[16:22:22] <jeffpc> I'm thinking something more like the METADATA vendor prefix
[16:22:26] <Ned Freed> I'm dubious anyone actually uses inline font objects and expects them to work.
[16:22:51] <jeffpc> I don't know if that means that we should register the prefix with IETF
[16:23:04] <Sean Leonard> not sure what the point of a "Vendor" namespace would be. first of all, anyone can register URNs, and anyone can mint URNs. As a matter of protocol slots, you could just use a URI in the capabilities protocol slot, if you are that...uh...lazy.
[16:23:25] <Barry Leiba> I'm with Sean on that.
[16:23:29] <Sean Leonard> for example if you just want a random urn you can mint urn:uuid:aaaa-......ffff
[16:23:41] <jeffpc> ok
[16:23:43] <jeffpc> fair enough
[16:25:05] <Barry Leiba> A reasonable thing for non-standardized extensions would be to publish the spec for your extension at, say, <http://banana.example.com/myJMAPext>, and then use that URI as the protocol string.
[16:25:28] <Barry Leiba> That serves both to create the necessary protocol element and to show people where the doc is.
[16:25:40] <jeffpc> in general, I don't like using URLs for specs/DTDs/etc.
[16:26:03] <Barry Leiba> In general, I agree, and we wouldn't standardize that.  But for non-standard stuff, it'd be OK.
[16:26:13] <jeffpc> yep
[16:28:11] <jeffpc> doing the simple html thing as an extension sounds nice
[16:28:39] <jeffpc> and it'll nicely demonstrate how extensions are done :)
[16:32:12] <Sean Leonard> @jeffpc and barry: yes, I agree. Vendors can have their specific ones not in urn:ietf:params:jmap. And if a vendor wants a stable one, there are a plethora of URI options to choose from, including their own HTTP/HTTPS URL, tag: URI [RFC4151], and certain urn: categories like oid, uuid, etc.
[16:35:39] <Barry Leiba> Or, my fave, ni:   (RFC 6920)
[16:36:23] <jeffpc> nope
[16:36:28] <Ned Freed> nope
[16:36:37] <Sean Leonard> nope
[16:38:27] <Ned Freed> I'm willing to author/coauthor the draft
[16:39:04] <Ned Freed> Sort of.
[16:39:17] <Barry Leiba> Ned, which draft are you volunteering for?
[16:39:32] <Barry Leiba> The one Chris is talking about now?
[16:39:39] <Ned Freed> http://www.postfix.org/XCLIENT_README.html
[16:39:45] <Barry Leiba> Righto.
[16:39:47] <Ned Freed> We implement it.
[16:39:51] <Barry Leiba> kewl
[16:40:23] <Ned Freed> Also critical for logging information like client IP.
[16:42:35] <Ned Freed> SMTP extensions have to be standards track
[16:42:36] <brong> FastMail implements and uses it too
[16:43:01] <Jason Polis> Mic: Is there an OpenAPI/Swagger for this ?
[16:44:14] <jeffpc> jmap isn't REST-ful
[16:44:45] <Ned Freed> And PROXY only addresses the need to get the client IP.
[16:45:14] <Jason Polis> thanks.
[16:47:50] <Ned Freed> Either way works for me.
[16:50:33] marc.laporte leaves the room
[16:50:45] marclaporte leaves the room
[16:51:25] marclaporte joins the room
[16:51:30] marc.laporte joins the room
[16:53:31] Barry Leiba leaves the room
[16:53:37] brong leaves the room
[16:54:09] Ken Murchison leaves the room
[16:54:30] Ned Freed leaves the room
[16:54:30] Dave Crocker leaves the room
[16:54:30] Jason Polis leaves the room
[16:54:31] Sean Leonard leaves the room
[16:56:10] meetecho leaves the room
[17:24:28] jeffpc leaves the room
[17:54:02] N7XVilai leaves the room
Powered by ejabberd - robust, scalable and extensible XMPP server Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!