Skip to main content

RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
RFC 4733

Yes

(Cullen Jennings)

No Objection

(Bill Fenner)
(Brian Carpenter)
(David Kessens)
(Jon Peterson)
(Lisa Dusseault)
(Mark Townsley)
(Ross Callon)
(Sam Hartman)
(Ted Hardie)

Recuse

(Magnus Westerlund)

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

Lars Eggert
Yes
Comment (2006-05-22)
INTRODUCTION, para. 15:

>    Companion documents add event codes to this registry relating to
>    modem, fax, text telephony, and channel-associated signalling events.
>    The remainder of the event codes defined in RFC 2833 are deprecated.

        What are the companion documents? I'm guessing at least
        draft-ietf-avt-rfc2833bisdata-06, which isn't cited. Are there others?
        Without this information, it's hard to know what the "remainder of the
        event codes defined in RFC 2833" that are being deprecated actually are.
Cullen Jennings Former IESG member
Yes
Yes ()

                            
Bill Fenner Former IESG member
No Objection
No Objection ()

                            
Brian Carpenter Former IESG member
No Objection
No Objection ()

                            
Dan Romascanu Former IESG member
No Objection
No Objection (2006-05-23)
1. idnits complains wrt. 2119 boilerplate on both documents. The reason seems to be that the recommended 2119 bolerplate text is not reproduced ad-literam.

2. The abbreviations list in draft-ietf-avt-rfc2833bisdata-06.txt is not complete. PBX and MIME are being used in the document and not included in the list
David Kessens Former IESG member
No Objection
No Objection ()

                            
Jari Arkko Former IESG member
No Objection
No Objection (2006-05-25)
> If the specification is created by an outside body, the IETF-appointed expert must ...

Trying to understand if the rules are clear enough to be followed.
What's "an outside body"? Does it cover only other SDOs, companies,
persons? What about individual submissions through the RFC Editor?
And wouldn't the same checks need to be done even if the document
was an IETF product?

I'd suggest dropping the "if" part and just saying what the
expert needs to do.

Nits (I get these from a script that I run for all documents):

s/occurence/occurrence/
s/occuring/occurring/
two ways to write echo canceller / cancellor
s/renable/re-enable/
Jon Peterson Former IESG member
No Objection
No Objection ()

                            
Lisa Dusseault Former IESG member
No Objection
No Objection ()

                            
Mark Townsley Former IESG member
No Objection
No Objection ()

                            
Ross Callon Former IESG member
No Objection
No Objection ()

                            
Russ Housley Former IESG member
(was Discuss) No Objection
No Objection (2006-05-22)
  s/IPSEC/IPsec/
Sam Hartman Former IESG member
(was Discuss) No Objection
No Objection ()

                            
Ted Hardie Former IESG member
No Objection
No Objection ()

                            
Magnus Westerlund Former IESG member
Recuse
Recuse ()