Registered payload types for G.723.1/G.729

[Chip Sharp]

I'd recommend that as SG16 defines new encoding types that it register them
with IANA.

Theoretically, someone could register your codepoints for a different
algorithm.

Chip

At 01:11 PM 2/23/00 -0800, Hutton, Charles wrote:
>I have the same concerns for G.729E.
>
>
>Charles (Chuck) Hutton
>Strategic Architecture Engineering
>Wireless Local Technology Group
>AT&T Wireless Services
>PO Box 97059
>Redmond, WA 98073 (USPS only)
>9461 Willows Road
>Redmond, WA 98052 (FEDEX/UPS)
>425-702-2938 Voice
>425-702-2518 FAX
>charles.hutton at attws.com
>
> > ----------
> > From:         Frank Derks[SMTP:frank.derks at PHILIPS.COM]
> > Reply To:     Mailing list for parties associated with ITU-T Study Group
> > 16
> > Sent:         Wednesday, February 23, 2000 8:46 AM
> > To:   ITU-SG16 at mailbag.cps.intel.com
> > Subject:      Re: Registered payload types for G.723.1/G.729
> >
> > <<File: FILE0001>>
> > Tom,
> >
> > section 3 of RFC1890 indeed specifies how additional payload types have to
> > be registered with the IANA.
> > Table 2 in section 7 specifies the assigned (and unassigned) payload types
> > at the time of publication of the
> > RFC (presumably). This table is no longer in line with the table that can
> > be found at the IANA Web site
> > (http://www.isi.edu/in-notes/iana/assignments/rtp-parameters), however.
> >
> > Since G.729 is not present in either of these tables, it would seem that
> > somebody will need to undertake
> > the action to do so. Especially because H.225.0 _does_ specify a payload
> > type for G.729 and I think it is
> > desirable that the code that is being used is not assigned (inadvertently)
> > to some other codec.
> >
> > Whose responsibility would it be to do so? ITU-SG16?
> >
> > -----------------------------------------------------
> > Frank Derks                    |Tel  +31 35 6893238 |
> > Advanced Development           |Fax  +31 35 6891030 |
> > Philips Business Communications|P.O. Box 32         |
> >                                |1200 JD  Hilversum  |
> >                                |The Netherlands     |
> > ----------------------------------------------------|
> > E-mail: mailto:frank.derks at philips.com              |
> > WWW: http://www.sopho.philips.com                   |
> > -----------------------------------------------------
> >
> >
> >
> >
> >
> > taylor at NORTELNETWORKS.COM@SMTP at MAILBAG.INTEL.COM on 23/02/2000 17:24:37
> > Please respond to ITU-SG16 at MAILBAG.INTEL.COM@SMTP
> > Sent by:        ITU-SG16 at MAILBAG.INTEL.COM
> > To:     ITU-SG16 at MAILBAG.INTEL.COM@SMTP
> > cc:
> > Subject:        Re: Registered payload types for G.723.1/G.729
> > Classification: Restricted
> > As I understand it (and I'd better be right, because I have to do similar
> > things for H.248!) the stuff initially defined in the RFC that sets up the
> > registration process (RFC 1890) does not go into the IANA database -- only
> > subsequent registrations.
> >
> > > -----Original Message-----
> > > From: Frank Derks [SMTP:frank.derks at PHILIPS.COM]
> > > Sent: Tuesday, February 22, 2000 10:30 AM
> > > To:   ITU-SG16 at MAILBAG.INTEL.COM
> > > Subject:      Registered payload types for G.723.1/G.729
> > >
> > > H.225.0 specifies that the payload types for G.723.1 and G.729 are 4 and
> > > 18 respectively.
> > > When I take a look at the registered payload types at the IANA, these
> > two
> > > codecs are
> > > not listed.
> > >
> > > Does this mean that the IANA list is not up-to-date or that these codecs
> > > are not officially
> > > registered.
> > >
> > > Frank
> > >
> > > -----------------------------------------------------
> > > Frank Derks                    |Tel  +31 35 6893238 |
> > > Advanced Development           |Fax  +31 35 6891030 |
> > > Philips Business Communications|P.O. Box 32         |
> > >                                |1200 JD  Hilversum  |
> > >                                |The Netherlands     |
> > > ----------------------------------------------------|
> > > E-mail: mailto:frank.derks at philips.com              |
> > > WWW: http://www.sopho.philips.com                   |
> > > -----------------------------------------------------
> >
> >
> >
> >

Support NetAid!  http://www.netaid.org
--------------------------------------------------
Chip Sharp                 Consulting Engineering
Cisco Systems              Telco Bio-region
Reality - Love it or Leave it.
--------------------------------------------------