Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-09-17 Thread Justin Karneges
On 09/16/2013 02:43 PM, Peter Saint-Andre wrote: On 6/13/13 11:47 AM, Justin Karneges wrote: On 06/13/2013 10:18 AM, Peter Saint-Andre wrote: On 6/13/13 8:40 AM, Matt Miller wrote: I don't necessarily have a problem with this as a protocol-level diagnostic tool; it can help users (or rather, t

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-09-16 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [ old thread alert ] On 6/13/13 11:47 AM, Justin Karneges wrote: > On 06/13/2013 10:18 AM, Peter Saint-Andre wrote: >> On 6/13/13 8:40 AM, Matt Miller wrote: >>> >>> On Jun 12, 2013, at 8:41 PM, Peter Saint-Andre >>> wrote: >>> -BEGIN PGP

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-13 Thread Justin Karneges
On 06/13/2013 10:18 AM, Peter Saint-Andre wrote: On 6/13/13 8:40 AM, Matt Miller wrote: On Jun 12, 2013, at 8:41 PM, Peter Saint-Andre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/6/13 6:40 AM, Matthew Wild wrote: On 6 June 2013 10:21, Simon Tennant wrote: End to end encrypt

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-13 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/13/13 11:33 AM, Philipp Hancke wrote: > Am 13.06.2013 19:18, schrieb Peter Saint-Andre: >> Yes, that is true, and I too don't want people to read more into >> the results than is justified. I will keep that very much in mind >> as I work on the ne

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-13 Thread Philipp Hancke
Am 13.06.2013 19:18, schrieb Peter Saint-Andre: Yes, that is true, and I too don't want people to read more into the results than is justified. I will keep that very much in mind as I work on the next revision. It seems that this could be easily achieved by splitting this up: 1) a query for ask

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-13 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/13/13 8:40 AM, Matt Miller wrote: > > On Jun 12, 2013, at 8:41 PM, Peter Saint-Andre > wrote: > >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 6/6/13 6:40 AM, Matthew Wild wrote: >>> On 6 June 2013 10:21, Simon Tennant >>> wrote:

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-13 Thread Matt Miller
On Jun 12, 2013, at 8:41 PM, Peter Saint-Andre wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 6/6/13 6:40 AM, Matthew Wild wrote: >> On 6 June 2013 10:21, Simon Tennant wrote: >>> End to end encryption is a worth goal. This is very cool for >>> getting information on the s2s c

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-12 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/6/13 6:40 AM, Matthew Wild wrote: > On 6 June 2013 10:21, Simon Tennant wrote: >> End to end encryption is a worth goal. This is very cool for >> getting information on the s2s connection. > > Perhaps on first sight. However this kind of usage i

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-06 Thread Matthew Wild
On 6 June 2013 21:12, Kurt Zeilenga wrote: > I personally think trying to answer of a question about user-to-user security > when security relies on non-E2E security mechanisms is a futile exercise. > But I do think my cringe can largely be dealt with through appropriately > stated security c

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-06 Thread Kurt Zeilenga
On Jun 5, 2013, at 7:14 PM, Peter Saint-Andre wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been thinking I'd like to resurrect the Hop Check proposal > (because after further reflection I think it would be useful, even if > not perfect): > > http://xmpp.org/extensions/xep-

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-06 Thread Matthew Wild
On 6 June 2013 10:21, Simon Tennant wrote: > End to end encryption is a worth goal. This is very cool for getting > information on the s2s connection. Perhaps on first sight. However this kind of usage is exactly why the XEP died last time around. It isn't suitable for anything except purely info

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-06 Thread Simon Tennant
End to end encryption is a worth goal. This is very cool for getting information on the s2s connection. XEP-0219 makes a lot of assumptions about the network topology always involving the traditional c2s design. How might this XEP report meaningful information back to the user in the following si

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-06 Thread Dave Cridland
On Thu, Jun 6, 2013 at 6:11 AM, Philipp Hancke wrote: > I've been thinking I'd like to resurrect the Hop Check proposal >> (because after further reflection I think it would be useful, even if >> not perfect): >> > > for debugging/support? +1 > > I've not checked back to see whether I liked this o

Re: [Standards] resurrecting Hop Check (XEP-0219)

2013-06-05 Thread Philipp Hancke
I've been thinking I'd like to resurrect the Hop Check proposal (because after further reflection I think it would be useful, even if not perfect): for debugging/support? +1 [...] Before I post an updated version, does anyone have requests for data they'd like to see included in the data forma

[Standards] resurrecting Hop Check (XEP-0219)

2013-06-05 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been thinking I'd like to resurrect the Hop Check proposal (because after further reflection I think it would be useful, even if not perfect): http://xmpp.org/extensions/xep-0219.html Before I post an updated version, does anyone have requests f