Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
RFC 4856

Note: This ballot was opened for revision 02 and is now closed.

(Cullen Jennings) Yes

(Jari Arkko) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lisa Dusseault) (was Yes) No Objection

(Lars Eggert) No Objection

Comment (2006-08-29 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  Inconsistent use of RFC2119 terms in draft-ietf-avt-rfc3555bis-04 in
  the beginning of Section 2, i.e., before Section 2.1. There are many
  lowercase instances of these terms that should be uppercased IMO. I
  included one example below, there are several other cases.

Section 2., paragraph 2:
>      Required parameters
>           If the payload format does not have a fixed RTP timestamp
>           clock rate, then a "rate" parameter is required to specify the
>           RTP timestamp clock rate.  A particular payload format may
>           have additional required parameters.


(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

(Russ Housley) (was Discuss) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

Magnus Westerlund Recuse