1 / 3

RFC 2833bis

This document outlines minor clean-up and editorial changes in RFC 2833bis, providing a full example for redundancy and editorial improvements. Discusses open issues in interop, event name testing, timing mechanisms, and submission plans.

thane-mccullough
Download Presentation

RFC 2833bis

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. RFC 2833bis Henning Schulzrinne Columbia University IETF 57 - AVT

  2. Changes • No major technical changes • clean-up of MF description (SS#5, R-1, etc.) based on Telcordia and ITU documents • full example for redundancy and other editorial improvements • believed to be ready for WG last call, but … IETF 57 - AVT

  3. Open issues • No interop statement success – delegation did not work • Unclear whether support for particular events need testing – can trivially generate implementations that print out event name • does removing event names benefit anyone? • Sufficient to show use of • basic timing mechanism • RFC 2198 • Will submit brief feature list after IETF • Calling for volunteers • Alternative: cycle at Proposed • Suggestion: decision deadline by next IETF IETF 57 - AVT

More Related