[Standards] UPDATED: XEP-0186 (Invisible Command)

[Sam Whited]

Version 0.13 of XEP-0186 (Invisible Command) has been released and the
Last Call has been extended until 2017-12-12.

Abstract:
This document specifies an XMPP protocol extension for user
invisibility.

Changelog:
Addressed Last Call feedback: (1) clarified conformance requirements for
'probe' attribute and (2) removed text about using the same server
backend for privacy lists because XEP-0016 is now deprecated.
(psa)

URL: https://xmpp.org/extensions/xep-0186.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] LAST CALL: XEP-0234 (Jingle File Transfer)

[Daniel Gultsch]

2017-11-29 20:16 GMT+01:00 Jonas Wielicki :
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?

yes

> 2. Does the specification solve the problem stated in the introduction
> and requirements?

There is some unaddressed feedback in this thread:
https://mail.jabber.org/pipermail/standards/2017-May/032610.html

> 3. Do you plan to implement this specification in your code? If not,
> why not?

I have.

> 4. Do you have any security concerns related to this specification?

No

>
> 5. Is the specification accurate and clearly written?

See (2)
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] 2017-11-29 XMPP Council Meeting Minutes

[Ruslan N. Marchenko]

On 29.11.2017 17:42, Jonas Wielicki wrote:

Present: Dave (Chair), Kevin, Georg, Daniel, Sam
Minutes: Yours truly.

Chat logs: http://logs.xmpp.org/council/2017-11-29#15:55:08

...

2. Vote on deprecating XEP-0095 (Stream Initiation)
---

Sam did research on this one. It appears of the clients he inspected, not any
client *only* supported Stream Initiation (they all supported either
[XEP-0234] (Jingle File Transfer), Jingle *and* SI, or neither). (see the
Trello card [1] for details)ft-manager tp

Daniel thinks that there are clients which can only do SI, but doesn’t recall
any off the top of his head.
Telepathy-gabble for one supports only SI. I'm currently looking if i 
can monkeypatch existing ft-manager to handle jingle but this is in 
early PoC phase as of yet.
(telepathy-gabble:1776): gabble-DEBUG: emit_capabilities_update 
(presence-cache.c:1125): Emitting caps update for handle 1

  --added--
  Feature: http://www.google.com/xmpp/protocol/session
  Feature: urn:xmpp:jingle:transports:raw-udp:1
  Feature: http://jabber.org/protocol/jingle
  Feature: http://jabber.org/protocol/nick
  Feature: http://jabber.org/protocol/si
  Feature: http://jabber.org/protocol/ibb
  Feature: http://telepathy.freedesktop.org/xmpp/tubes
  Feature: http://jabber.org/protocol/bytestreams
  Feature: jabber:iq:last
  Feature: http://jabber.org/protocol/jingle/description/audio
  Feature: urn:xmpp:jingle:apps:rtp:1
  Feature: urn:xmpp:jingle:apps:rtp:audio
  Feature: urn:xmpp:jingle:apps:rtp:rtp-hdrext:0
  Feature: urn:xmpp:jingle:apps:rtp:rtcp-fb:0
  --end--


___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] LAST CALL: XEP-0363 (HTTP File Upload)

[XSF Editor]

This message constitutes notice of a Last Call for comments on
XEP-0363.

Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file can later be
downloaded again.

URL: https://xmpp.org/extensions/xep-0363.html

This Last Call begins today and shall end at the close of business on
2017-12-12.

Please consider the following questions during this Last Call and send
your feedback to the standards@xmpp.org discussion list:

1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?

2. Does the specification solve the problem stated in the introduction
and requirements?

3. Do you plan to implement this specification in your code? If not,
why not?

4. Do you have any security concerns related to this specification?

5. Is the specification accurate and clearly written?

Your feedback is appreciated!
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] LAST CALL: XEP-0234 (Jingle File Transfer)

[XSF Editor]

This message constitutes notice of a Last Call for comments on
XEP-0234.

Title: Jingle File Transfer
Abstract:
This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular
framework that enables the exchange of information about the file to
be transferred as well as the negotiation of parameters such as the
transport to be used.

URL: https://xmpp.org/extensions/xep-0234.html

This Last Call begins today and shall end at the close of business on
2017-12-12.

Please consider the following questions during this Last Call and send
your feedback to the standards@xmpp.org discussion list:

1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?

2. Does the specification solve the problem stated in the introduction
and requirements?

3. Do you plan to implement this specification in your code? If not,
why not?

4. Do you have any security concerns related to this specification?

5. Is the specification accurate and clearly written?

Your feedback is appreciated!
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] DEPRECATED: XEP-0095 (Stream Initiation)

[XSF Editor]

Version 1.2 of XEP-0095 (Stream Initiation) has been released.

Abstract:
This specification defines an XMPP protocol extension for initiating a
data stream between any two XMPP entities. The protocol includes the
ability to include metadata about the stream and provides a pluggable
framework so that various profiles of stream initiation can be defined
for particular use cases (such as file transfer).

Changelog:
Deprecated by vote of the council. (XEP Editor (ssw))

URL: https://xmpp.org/extensions/xep-0095.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] DEPRECATED: XEP-0096 (SI File Transfer)

[XSF Editor]

Version 1.3 of XEP-0096 (SI File Transfer) has been released.

Abstract:
This specification defines a profile of the XMPP stream initiation
extension for transferring files between two entities. The protocol
provides a modular framework that enables the exchange of information
about the file to be transferred as well as the negotiation of
parameters such as the transport to be used.

Changelog:
Deprecated by vote of the council. (XEP Editor (ssw))

URL: https://xmpp.org/extensions/xep-0096.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] 2017-11-29 XMPP Council Meeting Minutes

[Jonas Wielicki]

Present: Dave (Chair), Kevin, Georg, Daniel, Sam
Minutes: Yours truly.

Chat logs: http://logs.xmpp.org/council/2017-11-29#15:55:08


1. XEP-0387 (Compliance Suites 2018), vote to move to Draft
---

The Last Call expired at 2017-11-15. Kevin objects that the Council may have 
to re-issue the Last Call because the current Last Call was issued by the 
previous Council and no decision on advancement was made subsequently.

Since it is not clear that there is any process requiring Council to do so and 
no value is seen in re-issuing the LC, no new LC is issued and the vote is on 
advancement to Draft.

Sam, Daniel, Georg, and Dave vote +1.
Kevin will vote on-list.


2. Vote on deprecating XEP-0095 (Stream Initiation)
---

Sam did research on this one. It appears of the clients he inspected, not any 
client *only* supported Stream Initiation (they all supported either 
[XEP-0234] (Jingle File Transfer), Jingle *and* SI, or neither). (see the 
Trello card [1] for details)

Daniel thinks that there are clients which can only do SI, but doesn’t recall 
any off the top of his head.

(Some technical details of SI and Jingle have been omitted in the minutes. 
Please refer to the logs [2] if you are interested in those details.)

Kevin mentions that Jingle is still Experimental and that an LC on Jingle may 
provide useful input on the deprecation decision (without wanting to gate 
deprecation of SI on advancement of Jingle).

Sam agrees with pushing Jingle forward, but thinks that SI is functionally 
deprecated in any case. Sam does not see much value in seeking feedback on the 
deprecation; it would just document what the community has already decided.

Dave, Kevin, Daniel, Georg, and Sam vote +1.


3. Vote on deprecating XEP-0096 (SI File Transfer)
--

(This has pretty much been discussed in agendum 2.)

Dave, Kevin, Daniel, Georg, and Sam vote +1.


4. Issue Last Call for XEP-0363 (HTTP File Upload) for advancement to Draft
---

Sam, Kevin, Daniel, Dave and Georg vote +1

Kevin notes that he’ll have feedback on-list.


5. Trello Triage


Dave mentions that the proposed agenda has grown over time and much of it has 
been there for a long time.

The [XEP-0280] (Message Carbons) item is briefly discussed. Georg still wants 
to have his changes merged, but also notes that he thinks there isn't much 
sense to move on with XEP-0280 or [XEP-0313] (Message Archive Management) 
without having a general discussion about message routing and persistence in 
general.

There are apparently some changes to [XEP-0186] (Invisible Command) (which is 
currently in Last Call) which were supposed to be made by Peter. Nobody seems 
to know which changes and where they went.

Likewise, the LC on [XEP-0352] (Client State Indication) has expired. Dave 
proposes to re-start the LC on both XEP-0186 and XEP-0352. He will put them on 
the agenda for next weeks meeting.

Agenda about [XEP-0084] (User Avatars), [XEP-0048] (Bookmarks), [XEP-0071] 
(XHTML-IM) deprecation, [XEP-0286] (Mobile Considerations on LTE Networks) are 
put on next weeks agenda.


6. AOB -- Vote on issuing a Last Call for XEP-0234 (Jingle File Transfer)
-

(The discussion happened while discussing agendum 2.)

Dave, Daniel, Sam, Georg and Kevin vote +1


7. Time of next
---

Next week, same time. Dave won’t be able to make it and asks Kevin to chair, 
who agrees.


EOM.


   [1]: https://trello.com/c/Gy5PecaQ/227-deprecate-xep-0095-stream-initiation
   [2]: http://logs.xmpp.org/council/2017-11-29#16:00:54
   [3]: http://logs.xmpp.org/council/2017-11-29#16:12:38
   [XEP-0048]: https://xmpp.org/extensions/xep-0048.html
   [XEP-0071]: https://xmpp.org/extensions/xep-0071.html
   [XEP-0084]: https://xmpp.org/extensions/xep-0084.html
   [XEP-0095]: https://xmpp.org/extensions/xep-0095.html
   [XEP-0096]: https://xmpp.org/extensions/xep-0096.html
   [XEP-0186]: https://xmpp.org/extensions/xep-0186.html
   [XEP-0234]: https://xmpp.org/extensions/xep-0234.html
   [XEP-0280]: https://xmpp.org/extensions/xep-0280.html
   [XEP-0286]: https://xmpp.org/extensions/xep-0286.html
   [XEP-0313]: https://xmpp.org/extensions/xep-0313.html
   [XEP-0352]: https://xmpp.org/extensions/xep-0352.html
   [XEP-0363]: https://xmpp.org/extensions/xep-0363.html
   [XEP-0387]: https://xmpp.org/extensions/xep-0387.html


signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] XMPP Council Meeting tomorrow

[Kevin Smith]

On 28 Nov 2017, at 17:53, Dave Cridland  wrote:
> * Vote on deprecating XEP-0085 (Stream Initiation)

Isn’t 85 CSN. Did you mean 85 CSN, or 95 SI?

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] XMPP Council Meeting tomorrow

[Kevin Smith]

> On 28 Nov 2017, at 17:53, Dave Cridland  wrote:
> 
> Folks,
> 
> The XMPP Council will be holding it's first "business" meeting
> tomorrow at 1600 UTC. While we organise the agenda on Trello at
> https://trello.com/b/ww7zWMlI/xmpp-council-agenda, there's quite a few
> old cards, so I'm proposing dedicating some of tomorrow's meeting to
> having a quick check to see what's relevant and what's overtaken by
> events. There are also three voting items, all advancements:
> 
> * Vote on moving XEP-0387 to Draft [Reboot voting from last session]

I think that’s a vote to issue a new last call, as they get cancelled on the 
Council change-over, isn’t it?

/K

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] NEW: XEP-0395 (Atomically Compare-And-Publish PubSub Items)

[XSF Editor]

Version 0.1 of XEP-0395 (Atomically Compare-And-Publish PubSub Items)
has been released.

Abstract:
This specification provides a mechanism to atomically Compare-And-
Publish items to a PubSub node.

Changelog:
Accepted by Council as Expremental XEP (XEP Editor (jwi))

URL: https://xmpp.org/extensions/xep-0395.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] NEW: XEP-0396 (Jingle Encrypted Transports - OMEMO)

[XSF Editor]

Version 0.1 of XEP-0396 (Jingle Encrypted Transports - OMEMO) has been
released.

Abstract:
Extension for JET introducing OMEMO End-to-End Encrypted Jingle
Transports.

Changelog:
Accepted by Council as Expremental XEP (XEP Editor (jwi))

URL: https://xmpp.org/extensions/xep-0396.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] UPDATED: XEP-0060 (Publish-Subscribe)

[XSF Editor]

Version 1.14 of XEP-0060 (Publish-Subscribe) has been released.

Abstract:
This specification defines an XMPP protocol extension for generic
publish-subscribe functionality. The protocol enables XMPP entities to
create nodes (topics) at a pubsub service and publish information at
those nodes; an event notification (with or without payload) is then
broadcasted to all entities that have subscribed to the node. Pubsub
therefore adheres to the classic Observer design pattern and can serve
as the foundation for a wide variety of applications, including news
feeds, content syndication, rich presence, geolocation, workflow
systems, network management systems, and any other application that
requires event notifications.

Changelog:
Add pubsub#multi-items to features. (jt)

URL: https://xmpp.org/extensions/xep-0060.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] UPDATED: XEP-0392 (Consistent Color Generation)

[XSF Editor]

Version 0.4 of XEP-0392 (Consistent Color Generation) has been
released.

Abstract:
This specification provides a set of algorithms to consistently
generate colors given a string. The string can be a nickname, a JID or
any other piece of information. All entities adhering to this
specification generate the same color for the same string, which
provides a consistent user experience across platforms.

Changelog:
Use different formulas for Color Vision Deficiency correction, as
suggested by Marcus Waldvogel.
Update test vectors.
Clarify generation of the angle.
Prioritize nicknames over bare JIDs.
Add rationale for new palette mapping algorithm introduced in 0.3.
(jwi)

URL: https://xmpp.org/extensions/xep-0392.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] XEP-0392 angle generation

[Jonas Wielicki]

Hi Marcel and others,

First of all, thank you for your valuable feedback. I have incorporated
it into an update of XEP-0392 which I’ll publish soon.


On 23.11.2017 18:22, Marcel Waldvogel wrote:
>>> * 5.5 Adapting the Color for specific Background Colors I presume
>>> this "inverse alpha" calculation should be applied always, even on
>>> white backgrounds? 
>>
>>
>> Maybe™. We need deployment experience with that (I only played around with 
>> it 
>> on some uniformly colored backgrounds for testing, and there the effect was 
>> quite useful). Another way I am thinking of is to fully saturize the 
>> background color for the "inverse alpha" calculation and separate the color 
>> (hue) from a to-be-specified brightness adaption.
>>
>>
>>> Otherwise, there is a discontinuity. It would be good to explain the
>>> rationale behind this part. 
>>
>>
>> Can you specify what is unclear here?
>>
> 
> With discontinuity, I meant that there will be a different color chosen
> for those that use the color before 5.5 and after 5.5. So it would be
> good to state to always apply 5.5 (or to never apply it or …).

Yes, 5.5 MAY be applied to grayscale backgrounds, but does not have to
be  applied. It doesn’t change the hue and it is up to the client
(developer) to decide whether adaption is necessary. It does not harm
either way.

For coloured backgrounds, applying 5.5 is RECOMMENDED because it
provides contrast even in extreme situations. Alternatively, a border or
similar mechanism can be used.

I’ll add wording with respect to that to the next update.

kind regards,
Jonas



signature.asc
Description: OpenPGP digital signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___