Re: [Standards] NEW: XEP-0364 (Current Off-the-Record Messaging Usage)

[Thijs Alkemade]

> However, OTR requires that messages be sent to a particular resource. 
> Therefore clients SHOULD send OTR messages to a full JID, possibly allowing 
> the user to determine which resource they wish to start an encrypted session 
> with.

This is no longer true with OTR v3. This version added “instance tags” which
can distinguish different clients signed in to the same account.

Regards,
Thijs


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Standards] NEW: XEP-0364 (Current Off-the-Record Messaging Usage)

[Sam Whited]

Thanks Thijs, I was forgetting about instance tags entirely. Will fix.

—Sam

On Wed, Sep 9, 2015 at 6:20 AM, Thijs Alkemade  wrote:
>> However, OTR requires that messages be sent to a particular resource. 
>> Therefore clients SHOULD send OTR messages to a full JID, possibly allowing 
>> the user to determine which resource they wish to start an encrypted session 
>> with.
>
> This is no longer true with OTR v3. This version added “instance tags” which
> can distinguish different clients signed in to the same account.
>
> Regards,
> Thijs



-- 
Sam Whited
pub 4096R/54083AE104EA7AD3
https://blog.samwhited.com

Re: [Standards] NEW: XEP-0364 (Current Off-the-Record Messaging Usage)

[Daniel Gultsch]

well instance tags only help the receiving client to discard garbage. if
you send your messages to a full jid you avoid unnecessary traffic.
On Sep 9, 2015 16:16, "Sam Whited"  wrote:

> Thanks Thijs, I was forgetting about instance tags entirely. Will fix.
>
> —Sam
>
> On Wed, Sep 9, 2015 at 6:20 AM, Thijs Alkemade  wrote:
> >> However, OTR requires that messages be sent to a particular resource.
> Therefore clients SHOULD send OTR messages to a full JID, possibly allowing
> the user to determine which resource they wish to start an encrypted
> session with.
> >
> > This is no longer true with OTR v3. This version added “instance tags”
> which
> > can distinguish different clients signed in to the same account.
> >
> > Regards,
> > Thijs
>
>
>
> --
> Sam Whited
> pub 4096R/54083AE104EA7AD3
> https://blog.samwhited.com
>

Re: [Standards] NEW: XEP-0364 (Current Off-the-Record Messaging Usage)

[Daniel Gultsch]

and more importantly makes the behavior (who will actually receive the
message) much more predictable
On Sep 9, 2015 20:32, "Daniel Gultsch"  wrote:

> well instance tags only help the receiving client to discard garbage. if
> you send your messages to a full jid you avoid unnecessary traffic.
> On Sep 9, 2015 16:16, "Sam Whited"  wrote:
>
>> Thanks Thijs, I was forgetting about instance tags entirely. Will fix.
>>
>> —Sam
>>
>> On Wed, Sep 9, 2015 at 6:20 AM, Thijs Alkemade  wrote:
>> >> However, OTR requires that messages be sent to a particular resource.
>> Therefore clients SHOULD send OTR messages to a full JID, possibly allowing
>> the user to determine which resource they wish to start an encrypted
>> session with.
>> >
>> > This is no longer true with OTR v3. This version added “instance tags”
>> which
>> > can distinguish different clients signed in to the same account.
>> >
>> > Regards,
>> > Thijs
>>
>>
>>
>> --
>> Sam Whited
>> pub 4096R/54083AE104EA7AD3
>> https://blog.samwhited.com
>>
>