IETF 94
XRBLOCK WG Meeting 
Date and Time: 2015.11.5 17:40-18:40

Meeting chaired by Dan Romascanu (Shida had to leave earlier)
Notes taken by Rachel Huang

* Action Items ***********************************


2. Status Update

- Rachel - fix nits in draft-ietf-xrblock-rtcp-xr-video-lc and submit update
- Dan- update shepherd write-up and submit to the IESG

3. Updates to Various Drafts
3.1 RFC6958 errata
- Alissa - reject the RFC6958 errata
- Varun - file new errata for RFC 6598
3.2 RFC7509 errata
- Varun - file errata
3.3 
- Dan - update milestones
- Dan - confirm adoption on mail list
- Varun - submit as WG item after confirmation
- Dan - send to WGLC after submission as WG item

4. draft-ietf-xrblock-rtcweb-rtcp-xr-metrics
- Shida - send to WGLC
- Shida - inform RTCWEB about the WGLC, send liaison to W3C about the WGLC


* Detailed Notes ****************************************

1. Note Well, Note Takers, Jabber Scribes, Agenda Bashing - Chair (5 min)

2. XRBLOCK WG Status Update - Chairs (5 min) 

  https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-video-lc/ - - fix the nits (Rachel), take 05 version, and then request for publication

3. Updates to Various Drafts (Varun)
    
    3.1 RFC6958, errata need to be update.
    How: AD reject the errata, and file a new one.

    3.2 RFC7509 - reporting an errata about block length.

    3.3 NEW DRAFT - http://datatracker.ietf.org/doc/draft-singh-xrblock-independent-burst-gap-discard/
       - number of bursts - 16bit ok
       - milestone on the charter and call for adoption in the list, after
       - submit it as a WG draft, will go to the WGLC.


4. RTCWEB Statistics I-D (including errata to RFC 7003) - Varun (20 min)
https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/

- WebRTC use the W3C statistics document. W3C will not use an IANA registry. People can send recommendation to w3c's specification for new metrics if they think useful. Up to W3C to decide to incorporate any identifiers defined in other SDO. 
- What is the timeline on the publication of W3C's spec? April 2016 or November 2016,version 1.
- continue progressing the draft. Send liaison statement to WEBRTC. should we do it before WGLC? No need to get late on the WGLC. 
- one way coordinate W3C with updating the wiki to add the metrics informed. Another way is do not use the same identifier if having similar but not the same metrics.
- AD: progressing the draft, sending the liaison statement, the draft becomes RFC, there'll be IANA registry.
- ready for WGLC. Do we need to send the document to W3C in WGLC? earlier is better. 




5. Next Steps