Re: [rtcweb] Results of call for consensus on ICE transport parameter issue

[Christer Holmberg <[e-mail]>]

Hi,

I am not sure what other document you refer to, but it really depends on what the text is talking about: the semantics of the <proto> field, which is a transport protocol, or whatever is used as a transport protocol (e.g., an RTP profile).

Having said that, I am aware that documents unfortunately don’t use consistent terminology, so I wouldn’t be surprised if the 4566bis terminology isn’t used everywhere (also, there have been discussions about the 4566bis terminology itself…).

My personal preference would be to be aligned with 4566bis, but as long as we are consistent within JSEP I can live with it.

Regards,

Christer


From: Justin Uberti <[e-mail]>
Date: Monday, 25 February 2019 at 19.54
To: Christer Holmberg <[e-mail]>
Cc: Roman Shpount <[e-mail]>, Ted Hardie <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: [rtcweb] Results of call for consensus on ICE transport parameter issue

Sure, but I think it makes sense to use the same terminology (i.e., "profile") as is used in other RTP-related documents.

On Sun, Feb 24, 2019 at 11:58 PM Christer Holmberg <[e-mail]<mailto:[e-mail]>> wrote:
Hi,

In 4566bis, <proto> defines a transport protocol.

In case of RTP, the text refers to RTP/AVP as an “RTP profile”, but it is still a transport protocol.

Regards,

Christer

From: Justin Uberti <[e-mail]<mailto:[e-mail]>>
Date: Monday, 25 February 2019 at 6.10
To: Roman Shpount <[e-mail]<mailto:[e-mail]>>
Cc: Ted Hardie <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Christer Holmberg <[e-mail]<mailto:[e-mail]>>
Subject: Re: [rtcweb] Results of call for consensus on ICE transport parameter issue

Found a way to address this with minor changes to the existing PR.

On Fri, Feb 22, 2019 at 5:46 PM Justin Uberti <[e-mail]<mailto:[e-mail]>> wrote:
Roman, thanks for raising this. I looked into this a bit and it's kind of ambiguous; https://tools.ietf.org/html/rfc7850 uses "profile", "proto", and "protocol" (although "protocol" is used most frequently).

JSEP actually uses both profile and protocol to refer to the transport, depending on the section; if we make a change here, we should hit all usages, which probably means that it is outside of the scope of this particular issue.

On Tue, Feb 19, 2019 at 1:19 PM Roman Shpount <[e-mail]<mailto:[e-mail]>> wrote:
Hi Justin,

I did provide editorial feedback to the change on github:

1. This document refers to SDP protocol as profile. If you look at the referenced documents that define "profiles" in JSEP, they all refer to them as protocols. Also, in case of SRTP, profile is actually something different and refers to SRTP key parameters.

2. Default candidate does not have profile (or protocol), it has transport, port, and (connection-)address. So each "m=" and "c=" MUST be filled in with port, protocol, and address to match port, transport, and address of the default candidate for the m= section, as described in ice-sip-sdp.

Regards,
_____________
Roman Shpount


On Tue, Feb 19, 2019 at 3:05 PM Christer Holmberg <[e-mail]<mailto:[e-mail]>> wrote:
Looks good.

Regards,

Christer

From: rtcweb <[e-mail]<mailto:[e-mail]>> on behalf of Justin Uberti <juberti=[e-mail]<mailto:[e-mail]>>
Date: Saturday, 16 February 2019 at 3.57
To: Ted Hardie <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: Re: [rtcweb] Results of call for consensus on ICE transport parameter issue

I have updated this PR to incorporate minor feedback that was received during the consensus call. Those who had feedback, please take another look and comment on the PR if you are satisfied.

On Fri, Feb 15, 2019 at 2:56 PM Ted Hardie <[e-mail]<mailto:[e-mail]>> wrote:
The chairs believe that there was rough consensus among those responding to make the change in:

https://github.com/rtcweb-wg/jsep/pull/863

Given the state of the document, it will be the Area Director's call as to how much of the post-working group approval process must be re-done.  Authors, please wait on his direction before publishing a new version with this merged.

Regards,
Ted and Sean
_______________________________________________
rtcweb mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/rtcweb
_______________________________________________
rtcweb mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/rtcweb