Skip to main content

RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) ST 336 Encoded Data
draft-ietf-payload-rtp-klv-04

Yes

(Robert Sparks)

No Objection

(Adrian Farrel)
(Gonzalo Camarillo)
(Jari Arkko)
(Ralph Droms)
(Russ Housley)
(Sean Turner)
(Stewart Bryant)
(Wesley Eddy)

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

Robert Sparks Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Gonzalo Camarillo Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Pete Resnick Former IESG member
(was Discuss) No Objection
No Objection (2012-03-05) Unknown
[All comments addressed]
Peter Saint-Andre Former IESG member
No Objection
No Objection (2012-02-15) Unknown
Although I agree that the $100 charge to obtain a copy of SMPTE 336M is unpleasant, RFC 3497 provides a precedent of normatively referencing a specification (SMPTE 292M) for which payment is required. Therefore I am balloting "No Objection".
Ralph Droms Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection (2012-02-15) Unknown
I strongly support Adrian's DISCUSS. In fact, the IESG should probably issue guidance about this issue.
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Sean Turner Former IESG member
No Objection
No Objection () Unknown

                            
Stephen Farrell Former IESG member
No Objection
No Objection (2012-02-14) Unknown
-  What happens if the RTP packet with M=1 gets lost? It may
be in there but I either missed it or didn't get it.

- The normative [SMPTE336M] document costs $100 so I cannot
check it. Maybe that's considered ok in this space but its quite odd 
for a standards-track RFC in general. Is there no way that that 
specification could be made available for free so that people can 
implement IETF standards without having to pay? That's highly 
desirable at least.  (I assume the WG did specifically consider this 
and decided they were ok with it. Consider this an exhortation 
from outside the WG.)





Stewart Bryant Former IESG member
No Objection
No Objection () Unknown

                            
Wesley Eddy Former IESG member
No Objection
No Objection () Unknown