Repository navigation
docs(rtc): specify provider-neutral media negotiation profile - #28
Draft
jpelaez-23blocks wants to merge 1 commit into
Draft
jpelaez-23blocks wants to merge 1 commit into
jpelaez-23blocks wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Companion draft to #26. Review and merge the base protocol proposal before retargeting to main.
What changes
15 — RTC Media Interoperability Profile
Status: Draft. Companion to 13 — Real-Time Sessions.
Separation of responsibilities
AMP delivers authenticated and signed call control events. A media adapter transports low-latency audio and does not alter AMP message semantics. A provider MUST NOT require LiveKit, Twilio, AI Maestro or any proprietary SDK to understand the AMP-RTC extension.
Proposed minimum profile
rtc:v1; media:audio; media profile:webrtc-audio-v1(provisional).Validation
Specification-only; normative details and interoperability tests remain open. This PR is intentionally stacked on the base proposal.