Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)
RFC 4712

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

(David Kessens) Yes

(Bert Wijnen) Yes

(Ross Callon) No Objection

(Brian Carpenter) (was Discuss) No Objection

Comment (2006-02-14)
No email
send info

(Margaret Cullen) No Objection

(Lisa Dusseault) No Objection

(Bill Fenner) No Objection

(Ted Hardie) (was Discuss) No Objection

(Sam Hartman) (was Discuss) No Objection

(Scott Hollenbeck) No Objection

(Cullen Jennings) No Objection

(Allison Mankin) No Objection

Comment (2006-02-16 for -)
No email
send info
Framework:
  Change real phone number from Bangladesh to a valid example phone number.
  RFC 3761's example +44-116-496-0348 is a set-aside number that is usable.

*** I don't require any action on comment below - it is a non-blocking
comment.  It is also not related to any Last Call comment received.
It is just for information:

Similar to Ted's Discuss - the framework says it can collect a measurement
of the RTP traffic and "application" traffic which is the related
signaling traffic for the RTP stream.  But there is no way here to
associate the two and know which signaling PDUs go with which RTP PDUs
in the measured stream.  The SDP exchanges which establish these bindings
are not captured, just as the SDP information about binding of port numbers
to codec types is not captured.

(Jon Peterson) No Objection

(Mark Townsley) No Objection

Magnus Westerlund No Objection

(Alex Zinin) No Objection

(Dan Romascanu) Recuse