Minutes IETF104: avtcore
minutes-104-avtcore-00

Meeting Minutes Audio/Video Transport Core Maintenance (avtcore) WG
Title Minutes IETF104: avtcore
State Active
Other versions plain text
Last updated 2019-04-03

Meeting Minutes
minutes-104-avtcore

   AVTCORE Audio/Video Transport Core Maintenance WG Meeting

====================================================
Announcement: Barry taking over as responsible AD for WG from Ben

1. Note Well, Note Takers, Agenda Bashing - (Chairs)

Status of working group drafts:

      draft-ietf-avtcore-multi-media-rtp-session-13

      draft-ietf-avtcore-rtp-multi-stream-optimisation-12

      draft-ietf-avtext-rid-09

      draft-ietf-avtext-lrr-07

            [RFC Editor Queue]

      draft-ietf-avtcore-multiplex-guidelines-08 [AD Evaluation]

         Ben will try to get it reviewed before he steps down

      draft-ietf-avtext-framemarking-08

         One clarification needed and then publish.

2. draft-ietf-avtcore-cc-feedback-message-02   - Colin

    Re: RFC6679 relationship: Jonathan says, must not offer both, answer picks
    one

    Bundle Discussion from Hackathon, needs some expertise to verify, but
    probably should send to all.  Zahed volunteered to get such an expert.

    Negotiation of feedback mechanisms - many feel answer selects one, but some
    believe answers with more than one should be allowed. Noted that subsequent
    offer may come from another entity so, send the list again, but don't
    gratituitously change the answer.  Someone should send text to Colin

    Mo wants NACK text (if not ACK, NACK)  CCFB does not imply a retransmission
    request, NACK is required.

3. Payload status - Roni

   flexible-fec has a problem, was discussed with authors, and will have more
   discussionm in the evening.It may need a substantive change that could not
   reasonably be done with an editors note. AD changeover affects this.  Have
   to see what comes out of the discussion.

   Media types should also be registered in rtp-parameters but are not actually
   syncronized.There are differences in policy between media-types and
   rtp-parameters. Needs to be addressed. Possible that the rtp-parameter
   registration is not necessary, but RTP experts need to be engaged if it is
   to be used with RTP. Problem is how to do that. Possibly the "framing"
   option was intended to be that, and isn't working.  Barry and Colin to
   investigate.

4. Adjourned