[rtcweb] RTCWEB milestones (was: Protesting the QoS document decision)

[SM <[e-mail]>]

Hello,
At 09:43 20-12-2013, Dave Crocker wrote:
>That's not what you've got in rtcweb.  Quite the opposite.  Just 
>look at the wg statistics.  Lots of documents.  1.5 years.  Nothing 
>published. Blocked on a decision about a component.   I also hear 
>continuing reports of mutual suspicion amongst participants.

 From the RTCWEB minutes:

   The milestones were quickly reviewed, primarily noting that we are late with
   everything.  The WG was asked if they think it is a reasonable 
goal to finish
   all the core documents before the end of 2014.  This will be a challenge and
   people need to help by actually reviewing the documents and send comments.

   The dependencies was also reviewed.  Authors, consider if our normative
   references make sense. Are they really needed?  Waiting on references slows
   down publication.  WG please contribute to finish up these references also."

Currently, the goals and milestones are as follows:

   Oct 2012 - Send Security and Privacy Problem Statement
     (draft-ietf-rtcweb-security) to IESG for publication as Informational

   Oct 2012 - Complete Overview (and hold for dependency resolution)
     (draft-ietf-rtcweb-overview)

   Oct 2012 - Send Use Cases document 
(draft-ietf-rtcweb-use-cases-and-requirements)
    to IESG for publication as Informational

   Jan 2013 - Send Media Transport (draft-ietf-rtcweb-rtp-usage) to IESG for
     publication as Proposed Standard

   Jan 2013 - Send Security Solution (draft-ietf-rtcweb-security-arch) to IESG
    for publication as Proposed Standard

   Jan 2013 - Send Signalling Negotiation and NAT Traversal 
(draft-ietf-rtcweb-jsep)
     to IESG for publication as Proposed Standard

   Jan 2013 - Audio Processing and Audio Codecs 
(draft-ietf-rtcweb-audio) to IESG
     for publication as Proposed Standard

   Jan 2013 - Video Processing and Video Codecs 
(draft-ietf-rtcweb-video) to IESG
     for publication as Proposed StandardVideo Processing and Video Codecs
    (draft-ietf-rtcweb-video) to IESG for publication as Proposed Standard

   May 2013 - Send Quality of Service markings of RTCWeb packets
    (draft- ietf-rtcweb-qos) to IESG for publication as Proposed Standard

   Mar 2014 - Send STUN Usage for Consent Freshness to IESG for publication
     as proposed standard

   May 2103 - Send Data Stream Transport for non-media data
     (draft-ietf- rtcweb-data-channel) to IESG for publication as 
Proposed Standard

The "2103" could be a typo or RTCWEB could have been chartered for a 
100 years. :-)

Could the milestones be updated?  It might help to provide a sense of 
what the goals are and to assess whether the goals are being met.

Regards,
-sm