{"action":"created","issue":{"url":"https://api.github.com/repos/openpeer/ortc/issues/350","labels_url":"https://api.github.com/repos/openpeer/ortc/issues/350/labels{/name}","comments_url":"https://api.github.com/repos/openpeer/ortc/issues/350/comments","events_url":"https://api.github.com/repos/openpeer/ortc/issues/350/events","html_url":"https://github.com/openpeer/ortc/issues/350","id":126751348,"number":350,"title":"Should the spec detail \"RTCP matching rules\"?","user":{"login":"ibc","id":16191,"avatar_url":"https://avatars.githubusercontent.com/u/16191?v=3","gravatar_id":"","url":"https://api.github.com/users/ibc","html_url":"https://github.com/ibc","followers_url":"https://api.github.com/users/ibc/followers","following_url":"https://api.github.com/users/ibc/following{/other_user}","gists_url":"https://api.github.com/users/ibc/gists{/gist_id}","starred_url":"https://api.github.com/users/ibc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ibc/subscriptions","organizations_url":"https://api.github.com/users/ibc/orgs","repos_url":"https://api.github.com/users/ibc/repos","events_url":"https://api.github.com/users/ibc/events{/privacy}","received_events_url":"https://api.github.com/users/ibc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openpeer/ortc/labels/1.1","name":"1.1","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2016-01-14T21:25:15Z","updated_at":"2016-01-14T22:39:50Z","closed_at":null,"body":"Similar to section 8.3 \"RTP matching rules\", should the spec also mention RTCP matching rules?"},"comment":{"url":"https://api.github.com/repos/openpeer/ortc/issues/comments/171804621","html_url":"https://github.com/openpeer/ortc/issues/350#issuecomment-171804621","issue_url":"https://api.github.com/repos/openpeer/ortc/issues/350","id":171804621,"user":{"login":"ibc","id":16191,"avatar_url":"https://avatars.githubusercontent.com/u/16191?v=3","gravatar_id":"","url":"https://api.github.com/users/ibc","html_url":"https://github.com/ibc","followers_url":"https://api.github.com/users/ibc/followers","following_url":"https://api.github.com/users/ibc/following{/other_user}","gists_url":"https://api.github.com/users/ibc/gists{/gist_id}","starred_url":"https://api.github.com/users/ibc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ibc/subscriptions","organizations_url":"https://api.github.com/users/ibc/orgs","repos_url":"https://api.github.com/users/ibc/repos","events_url":"https://api.github.com/users/ibc/events{/privacy}","received_events_url":"https://api.github.com/users/ibc/received_events","type":"User","site_admin":false},"created_at":"2016-01-14T22:39:50Z","updated_at":"2016-01-14T22:39:50Z","body":"> transport.createAssociatedTransport() does create RTCP transport, but you don't need to call it. It's optional.\r\n\r\nOf course, and it obviously exists for interoperability reasons. But it opens the door to stupid scenarios and implementers must be ready to handle multiple RTP streams over transport X and their related RTCP streams over transport Y."}}