Opened 8 years ago

#31 new defect

Miscellaneous

Reported by: bernard_aboba@… Owned by: draft-ietf-rtcweb-use-cases-and-requirements@…
Priority: minor Milestone: milestone1
Component: use-cases-and-requirements Version: 1.0
Severity: In WG Last Call Keywords:
Cc:

Description

Section 3.2.1.1

"The application gives the users the opportunity to stop it from exposing the host IP address to the application of the other user."

[BA] This text suggests a requirement for the browser to ask user
consent, which seems different from what is in F39:

"The browser must make it possible to set up a call between two parties without one party learning the other party's host IP address."

IMHO, F39 seems somewhat closer to the requirement we want.

Section 3.2.10.1

"NOTE: More profiling of what this means may be needed."

[BA] Section 3.3.1.1 already describes a telephony gateway scenario,
but for some reason that section doesn't cite requirement F27 (SIP)
or A20. FWIW, I'm not sure what this scenario adds, because RFC 3261
inter-domain federation isn't widely deployed, as opposed to E.164
inter-connect.

Change History (0)

Note: See TracTickets for help on using tickets.