search

ice-wg / draft-ice-pac

Other
0 stars 0 forks source link

Use 'ICE candidates' instead of 'candidate addresses' (Editorial) #4

Closed cdh4u closed 5 years ago

cdh4u commented 5 years ago

Where: Introduction

What: s/candidate addresses/ICE candidates

Why: An address is just one part of a candidate

juberti commented 5 years ago

I tend to think this is implicit, and won't confuse anyone.

cdh4u commented 5 years ago

We use "candidates" everywhere else, and it is not only the addresses that are exchanged.

juberti commented 5 years ago

8445 also uses 'candidate transport addresses' in Section 2. But open to some other text here, 'ICE candidates' feels like it doesn't explain enough to the reader.

cdh4u commented 5 years ago

8445 also uses 'candidate transport addresses' in Section 2. But open to some other text here, 'ICE candidates' feels like it doesn't explain enough to the reader.

The paragraph says:

"Typically, when using ICE, endpoints will exchange candidate addresses, form a list of candidate pairs, and then test each candidate pair to see if connectivity can be established. If the test for a given pair fails, it is marked accordingly, and if all pairs have failed, the overall ICE process is considered to have failed."

If people don't understand what an "ICE candidate" is they won't understand the rest of the text either :)

My point is that endpoints are exchanging candidates. The candidate transport addresses are then used for sending connectivity checks. So, if you want to include it, perhaps something like:

"and then test each candidate pair, by sending connectivity checks using the candidate transport addresses, to see if...."

cdh4u commented 5 years ago

Implemented in #13