Skip to main content

The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
draft-ietf-sipping-transc-conf-03

Yes

(Jon Peterson)

No Objection

(David Kessens)
(Jari Arkko)
(Lisa Dusseault)
(Mark Townsley)
(Ross Callon)
(Russ Housley)
(Sam Hartman)
(Ted Hardie)

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

Jon Peterson Former IESG member
Yes
Yes () Unknown

                            
Brian Carpenter Former IESG member
No Objection
No Objection (2006-07-31) Unknown
From Gen-ART review:

nit:
The last paragraph of section 3.2 states that the transcode should return an error if it receives a URI List with more than one URI.  Earlier sections indicated that such multi-party requests were permitted.  Should this paragraph say "If a transcode which supports only two party transcoding receives an INVITE request with a URI-list with more than one URI, it SHOULD ..."

Section 3.4 begins "Figure 3 shows a similar message flow as the one in Figure 3."  I believe that the second "Figure 3" is supposed to be "Figure 2".

Yours,
Joel M. Halpern
Cullen Jennings Former IESG member
No Objection
No Objection (2006-08-17) Unknown
This is basically just a call flow usage of existing SIP stuff (and I love that). The question is, should this be PS or BCP?
David Kessens Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection (2006-08-15) Unknown
INTRODUCTION, paragraph 12:

>    This way of invocation meets the
>    requirements for SIP regarding transcoding services invocation to
>    support deaf, hard of hearing and speech-impaired individuals.

  Nit: s/hard of hearing/hard-of-hearing/


Section 1., paragraph 1:

>    The Framework for Transcoding with SIP [8] describes how two SIP [3]
>    UAs (User Agents) can discover imcompatibilities that prevent them

  Nit: s/imcompatibilities/incompatibilities/


Section 1., paragraph 3:

>    The UAs do not exchange any traffic (signalling or media) directly
>    between them.

  Nit: s/them/themselves/


Section 3.2., paragraph 5:

>    If a trancoder receives an INVITE request with a URI-list with more

  Nit: s/trancoder/transcoder/
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Mark Townsley Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Sam Hartman Former IESG member
No Objection
No Objection () Unknown

                            
Ted Hardie Former IESG member
No Objection
No Objection () Unknown