Coder Social home page Coder Social logo

ice-drafts's People

Contributors

suhashere avatar

Watchers

 avatar  avatar

ice-drafts's Issues

Clarify RFC4091 and RFC4092 status in Section 9

The text in section 9, read literally, deprecates RFCs 4091 and 4092. If that is the actual intention, the abstract and "obsoletes" metadata need to be updated to reflect this fact. If the deprecation is qualified (e.g., the RFCs are still okay in other contexts, but should not be used in conjunction with ICE), then the text in section 9 needs to be much clearer.

Clarify the relationship between ice-sip-sdp and RFC5245 + RFC6544

It's not clear to me what the relationship is between this document and RFC 5245 (and, for that matter, 6544). Is this supposed to obsolete RFC 5245? That appears to be the intention. It's also not clear why we would obsolete 5245 without also incorporating 6544 -- it seems that doing so leaves the use of ICE TCP with SIP to be kind of in limbo.

Assuming the intention is to replace RFC 5245, the structure of this document seems to leave non-SIP uses of RFC3264 (e.g., WebRTC) stranded. If the intention is not to replace RFC 5245, the replication of all of the SDP syntax seems to be problematic: the the case of a conflict, which specification is intended to govern?

In short, I think the relationship between this document, the contemporary work (e.g., ICE-BIS), and the historical work on which it is based needs to be made much clearer in the document itself, and we need to have a clear picture about how to handle SDP for non-SIP uses of ICE (e.g., by splitting this document into an SDP part and a SIP part, similar to how we split 3264 from 3261).

Default Candidate Handling

From Roman

  1. Move general requirements from https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-26#section-12.2 into ICE-SIP-SDP.

This section keeps repeating in protocol drafts and mostly represent generic ICE offer/answer requirements. Key points here are:

a. any protocol running over ICE transport SHOULD implement UDP based protocol version

b. when multiple candidates are sent in offer or answer during nomination process UDP based candidate SHOULD be included in the candidate list and SHOULD be selected as default candidate

c. proto value MUST match the protocol of the default candidate

d. for subsequent answer sent when ICE nomination process is not running, default candidate and proto in m= line MUST match the nominated candidate.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.