[Standards] Fwd: [Uta] Last Call: draft-ietf-uta-xmpp-05.txt (Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)) to Proposed Standard
It's not too late to provide feedback! This document is now in IETF Last Call. Peter Forwarded Message Subject: [Uta] Last Call: draft-ietf-uta-xmpp-05.txt (Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)) to Proposed Standard Date: Mon, 30 Mar 2015 07:24:06 -0700 From: The IESG iesg-secret...@ietf.org Reply-To: i...@ietf.org To: IETF-Announce ietf-annou...@ietf.org CC: u...@ietf.org The IESG has received a request from the Using TLS in Applications WG (uta) to consider the following document: - 'Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)' draft-ietf-uta-xmpp-05.txt as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2015-04-13. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document provides recommendations for the use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP). This document updates RFC 6120. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-uta-xmpp/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-uta-xmpp/ballot/ No IPR declarations have been submitted directly on this I-D. ID nits says some references are out of date, we'll fix that as we go. ___ Uta mailing list u...@ietf.org https://www.ietf.org/mailman/listinfo/uta -- Peter Saint-Andre https://andyet.com/
Re: [Standards] wiki for xeps
On 29 Mar 2015, at 02:36, Jefry Lagrange jefry.re...@gmail.com wrote: Hello everyone, I found myself thinking about the process of proposing and editing xeps that the xsf implements. I think there are some improvements that could be made in order to make the process easier. These are the main areas which I think are problematic with the current way of doing things: • git has a learning curve. • xml has a learning curve. • scripts are necessary to convert the xml to readable documents. • Everything is tracked in the same project (scripts, templates, xeps). XEPs aren't tracked as individual projects. These problems aren't that grave, after all, most of us are developers. However, I think it is worthwhile to explore alternatives to make it easier. I spent the past week working on a wiki page that closely resembles the look and feel of xeps. Here is the url: http://jlagrange.net/wiki/index.php/Category:Extensions In that week, I learned that by developing your own mediawiki skins and extensions, you are able to make a wiki look however you like. Because wikis were made specifically to track and modify documents, they have some features could be useful for us. • view and compare history of changes online • user management to allow authors to modify their xeps and nothing more. Or to allow trusted users to help Peter. • rss of changes • easier to edit and see the results without using scripts to convert it to html • discussion pages for each xep At the very least it could serve a way to make quick prototypes and get feedback. Hi Jefry, What’s your expected response to this? That is - are you posting it as a FYI thing for folks to look at, or are you proposing this as an update to XSF procedures? /K
Re: [Standards] wiki for xeps
Just as an experiment to see how the procedure could be improved. Of course, xsf could implement it if you are inclined to do it. Although, you'd have to be aware of the costs of doing that. On 30/03/15 16:55, Kevin Smith wrote: On 29 Mar 2015, at 02:36, Jefry Lagrange jefry.re...@gmail.com wrote: Hello everyone, I found myself thinking about the process of proposing and editing xeps that the xsf implements. I think there are some improvements that could be made in order to make the process easier. These are the main areas which I think are problematic with the current way of doing things: • git has a learning curve. • xml has a learning curve. • scripts are necessary to convert the xml to readable documents. • Everything is tracked in the same project (scripts, templates, xeps). XEPs aren't tracked as individual projects. These problems aren't that grave, after all, most of us are developers. However, I think it is worthwhile to explore alternatives to make it easier. I spent the past week working on a wiki page that closely resembles the look and feel of xeps. Here is the url: http://jlagrange.net/wiki/index.php/Category:Extensions In that week, I learned that by developing your own mediawiki skins and extensions, you are able to make a wiki look however you like. Because wikis were made specifically to track and modify documents, they have some features could be useful for us. • view and compare history of changes online • user management to allow authors to modify their xeps and nothing more. Or to allow trusted users to help Peter. • rss of changes • easier to edit and see the results without using scripts to convert it to html • discussion pages for each xep At the very least it could serve a way to make quick prototypes and get feedback. Hi Jefry, What’s your expected response to this? That is - are you posting it as a FYI thing for folks to look at, or are you proposing this as an update to XSF procedures? /K
