Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Tobias M]

> On 30.12.2015, at 22:48, Lance Stout  wrote:
> 
> The prose has the original  but the example shows 
> .
> 
> 
> Aside from that nit, I'm +1 on publishing this version.

Same goes for me. Also +1 on publishing.

Cheers,
Tobias

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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Dave Cridland]

On 6 January 2016 at 15:38, Philipp Hancke 
wrote:

> before publication


What?

Why on earth do we want to make changes before publication as a XEP?

Prior to publication as a XEP, this is not an XSF document. After, we
discuss it, make changes, and so on. I can understand making sure we fix
things prior to advancement as Draft or Final, but really - if it's worth
making changes to, it's worth publishing as an Experimental XEP first.

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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Philipp Hancke]

Am 06.01.2016 um 17:00 schrieb Dave Cridland:

On 6 January 2016 at 15:38, Philipp Hancke 
wrote:


before publication



What?

Why on earth do we want to make changes before publication as a XEP?


wouldn't such a change to the schema need a namespace bump?
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Philipp Hancke]

Am 06.01.2016 um 17:15 schrieb Dave Cridland:

On 6 January 2016 at 16:13, Philipp Hancke 
wrote:


Am 06.01.2016 um 17:00 schrieb Dave Cridland:


On 6 January 2016 at 15:38, Philipp Hancke 
wrote:

before publication





What?

Why on earth do we want to make changes before publication as a XEP?



wouldn't such a change to the schema need a namespace bump?



Yes. And that happens in Experimental. Its why we designed the namespace
structure that way; to make that easy and relatively painless.


that is the theory. In practice it is hard enough to make me want to 
avoid it for such a small change ;-)

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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Matthew Wild]

and my +1 also.

On 6 January 2016 at 14:33, Tobias M  wrote:
>
> On 30.12.2015, at 22:48, Lance Stout  wrote:
>
> The prose has the original  but the example shows
> .
>
>
> Aside from that nit, I'm +1 on publishing this version.
>
>
> Same goes for me. Also +1 on publishing.
>
> Cheers,
> Tobias
>
>
> ___
> Standards mailing list
> Info: http://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Philipp Hancke]

Am 17.12.2015 um 11:50 schrieb XMPP Extensions Editor:

The XMPP Extensions Editor has received a proposal for a new XEP.

Title: Jingle ICE Transport Method

Abstract: This specification defines a Jingle transport method that results in sending 
media data using datagram associations via the User Datagram Protocol (UDP) or using 
end-to-end connections via the Transport Control Protocol (TCP). This transport method is 
negotiated via the Interactive Connectivity Establishment (ICE) methodology (which 
provides robust NAT traversal for media traffic) and also supports the ability to 
exchange candidates throughout the life of the session, consistent with so-called 
"Trickle ICE" (draft-ietf-ice-trickle).

URL: http://xmpp.org/extensions/inbox/jingle-ice.html


before publication, can we make a minor schema change:
   
shoulld be optional. I'm not sure about whether the type as unsignedByte 
makes sense either. I seem to recall a network type (ethernet, wifi, 3g) 
in libjingle, but can't find it right now.

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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Dave Cridland]

On 6 January 2016 at 16:13, Philipp Hancke 
wrote:

> Am 06.01.2016 um 17:00 schrieb Dave Cridland:
>
>> On 6 January 2016 at 15:38, Philipp Hancke 
>> wrote:
>>
>> before publication
>>>
>>
>>
>> What?
>>
>> Why on earth do we want to make changes before publication as a XEP?
>>
>
> wouldn't such a change to the schema need a namespace bump?
>
>
Yes. And that happens in Experimental. Its why we designed the namespace
structure that way; to make that easy and relatively painless.

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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Peter Saint-Andre]

On 1/6/16 9:19 AM, Philipp Hancke wrote:

Am 06.01.2016 um 17:15 schrieb Dave Cridland:

On 6 January 2016 at 16:13, Philipp Hancke 
wrote:


Am 06.01.2016 um 17:00 schrieb Dave Cridland:


On 6 January 2016 at 15:38, Philipp Hancke 
wrote:

before publication





What?

Why on earth do we want to make changes before publication as a XEP?



wouldn't such a change to the schema need a namespace bump?



Yes. And that happens in Experimental. Its why we designed the namespace
structure that way; to make that easy and relatively painless.


that is the theory. In practice it is hard enough to make me want to
avoid it for such a small change ;-)


In any case I made the change and off we go, eh?

Peter


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

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Lance Stout]

The prose has the original  but the example shows 
.


Aside from that nit, I'm +1 on publishing this version.


/Lance



smime.p7s
Description: S/MIME cryptographic signature
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Philipp Hancke]

oh... just noticed this introduces types for tcp-active etc.
This is rather unfortunate as there can be candidates of type host with 
protocol udp and a tcptype active. Mapping this seems complicated, i'd 
prefer to have a separate tcptype attribute.


Also, the 6544 reference is not work in progress ;-)

And since i'm currently dealing with ice-lite:
For the purposes of the Jingle ICE-UDP Transport Method, both
parties are full ICE implementations and therefore the
controlling role MUST be assumed by the initiator and the
controlled role MUST be assumed by the responder.
We might want to introduce a way to use ice-lite.
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Ashley Ward]

> On 17 Dec 2015, at 12:49, Philipp Hancke  wrote:
> 
> Also, the 6544 reference is not work in progress ;-)

Thanks Philipp,

I’ve updated the reference to 6544 in the entities file and rebuilt the html.


—
Ash

smime.p7s
Description: S/MIME cryptographic signature
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Peter Saint-Andre]

The trickle reference needs to point to draft-ietf-ice-trickle too.

Sent from mobile, might be terse 

> On Dec 17, 2015, at 5:49 AM, Philipp Hancke  wrote:
> 
> oh... just noticed this introduces types for tcp-active etc.
> This is rather unfortunate as there can be candidates of type host with 
> protocol udp and a tcptype active. Mapping this seems complicated, i'd prefer 
> to have a separate tcptype attribute.
> 
> Also, the 6544 reference is not work in progress ;-)
> 
> And since i'm currently dealing with ice-lite:
>For the purposes of the Jingle ICE-UDP Transport Method, both
>parties are full ICE implementations and therefore the
>controlling role MUST be assumed by the initiator and the
>controlled role MUST be assumed by the responder.
> We might want to introduce a way to use ice-lite.
> ___
> Standards mailing list
> Info: http://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Lance Stout]

Regarding the  end-of-candidates signal:

>  id='xv39z423'
> to='romeo@montague.example/dr4hcr0st3lup4c'
> type='set'>
>  action='transport-info'
>   initiator='romeo@montague.example/dr4hcr0st3lup4c'
>   sid='a73sjjvkla37jfea'>
> 
>   
> 
>   
> 


Placing a new element as a direct child of  is a bit more difficult 
for an implementation to process (it requires a new special case to look for it 
as opposed to being carried along in the  element data already). It 
also would be better to drop the :info: namespace and just include it in the 
new ice:0 namespace, especially since there is already the remote-candidate 
signal.


So something like:

>  id='xv39z423'
> to='romeo@montague.example/dr4hcr0st3lup4c'
> type='set'>
>  action='transport-info'
>   initiator='romeo@montague.example/dr4hcr0st3lup4c'
>   sid='a73sjjvkla37jfea'>
> 
>   
> 
>   
> 
>   
> 



- Lance




smime.p7s
Description: S/MIME cryptographic signature
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Ashley Ward]

> On 17 Dec 2015, at 15:15, Peter Saint-Andre  wrote:
> 
> The trickle reference needs to point to draft-ietf-ice-trickle too.
> 
> Sent from mobile, might be terse 

Yeah, I noticed and corrected that shortly after I published it (My bad, 
although I’m going to blame it on Google’s result order!) :)

https://github.com/xsf/xeps/commit/c69a042e882863836a814f2e9cbac62c890cd3b0 


Is is okay now?

—
Ash

smime.p7s
Description: S/MIME cryptographic signature
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[Peter Saint-Andre]

Oh and a separate tcptype attribute seems fine. 

Not so sure about ice-lite yet...

Sent from mobile, might be terse 

> On Dec 17, 2015, at 5:49 AM, Philipp Hancke  wrote:
> 
> oh... just noticed this introduces types for tcp-active etc.
> This is rather unfortunate as there can be candidates of type host with 
> protocol udp and a tcptype active. Mapping this seems complicated, i'd prefer 
> to have a separate tcptype attribute.
> 
> Also, the 6544 reference is not work in progress ;-)
> 
> And since i'm currently dealing with ice-lite:
>For the purposes of the Jingle ICE-UDP Transport Method, both
>parties are full ICE implementations and therefore the
>controlling role MUST be assumed by the initiator and the
>controlled role MUST be assumed by the responder.
> We might want to introduce a way to use ice-lite.
> ___
> Standards mailing list
> Info: http://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
___
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] Proposed XMPP Extension: Jingle ICE Transport Method

[XMPP Extensions Editor]

The XMPP Extensions Editor has received a proposal for a new XEP.

Title: Jingle ICE Transport Method

Abstract: This specification defines a Jingle transport method that results in 
sending media data using datagram associations via the User Datagram Protocol 
(UDP) or using end-to-end connections via the Transport Control Protocol (TCP). 
This transport method is negotiated via the Interactive Connectivity 
Establishment (ICE) methodology (which provides robust NAT traversal for media 
traffic) and also supports the ability to exchange candidates throughout the 
life of the session, consistent with so-called "Trickle ICE" 
(draft-ietf-ice-trickle).

URL: http://xmpp.org/extensions/inbox/jingle-ice.html

The XMPP Council will decide in the next two weeks whether to accept this 
proposal as an official XEP.

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