1 / 9

CLUE DATA CHANNEL

CLUE DATA CHANNEL. CHRISTER HOLMBERG IETF#90 Toronto, Canada. ( 2 ) Q1: Keith Richard’s draft. OPEN ISSUE:

posy
Download Presentation

CLUE DATA CHANNEL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CLUE DATA CHANNEL CHRISTER HOLMBERG IETF#90 Toronto, Canada.

  2. (2) Q1: Keith Richard’s draft • OPEN ISSUE: • It is FFS whether the SDP-based WebRTC Data Channel Negotiation mechanism [I-D.ejzak-dispatch-webrtc-data-channel-sdpneg] will be used with the CLUE Data Channel. It depends on whether the draft will progress in MMUSIC, and whether it will be finalized before the publication of the CLUE mechanism. • STATUS: • Nothing has happened since London.

  3. (3) Q4: Version • OPEN ISSUE: • We need to determine whether we shall include a version number in the DCEP DATA_CHANNEL_OPEN message'protocol' field value for CLUE. • SUGGESTION: • ?

  4. (4) Q3: bundle-only • OPEN ISSUE: • We need to determine whether an "m=" line describing an SCTPoDTLS association can be used together with bundle-only, in which case there will be cases where an offer with a zero port value will create a corresponding answer with a non-zero port value. • SUGGESTION: • Allow usage of bundle-only • No need to talk about BUNDLE at all • Generic usage of BUNDLE for CLUE should be in the CLUE protocol spec

  5. (5) Q2: Offer/Answer • OPEN ISSUE: • As the SDP offer/answer procedures are generic to SCTPoDTLS association, it is FFS whether we need to specify them, or whether we can simply refer to draft-ietf-mmusic-sctp-sdp. • SUGGESTION: • Refer to draft-ietf-mmusic-sctp-sdp. • Generic CLUE Offer/Answer procedures in draft-ietf-clue-signalling.

  6. (6) DEPENDENCY IMPACTS • draft-ietf-mmusic-sctp-sdp-07: • SDP sctpmap attribute has been removed • SDP sctp-port attribute introduced • With DTLS/SCTP, indicates actual SCTP port • Suggestion: No need to define fixed port value for CLUE • SDP fmtp attribute used to indicate max message size • Message size indication optional • Suggestion: No need to define max message size for CLUE m=application 12345 DTLS/SCTP webrtc-datachannel a=fmtp: webrtc-datachannelmax-message-size=100000 a=sctp-port 4060

  7. (7) DEPENDENCY IMPACTS • draft-ietf-rtcweb-data-channel-11: • No changes • draft-ietf-rtcweb-data-protocol-07: • No changes

  8. (8) NEXT STEPS • Update draft based on closed open issues and changes in dependencies • Need to wait for dependencies to be finalized before WGLC

  9. THE END THANK YOU FOR LISTENING!

More Related