Internet Low Bit Rate Codec (iLBC)
draft-ietf-avt-ilbc-codec-05

[Note]: 'Codecs are not an area of strong expertise for IETF, so the AVT charter states that any codec specification would be taken only on a case-by-case basis.? The review of the charter in 2003 admitted this codec, and it did receive both AVT and external review.? From the chairs'' request to publish:? "The codec has been reviewed by the AVT working group and several outside experts (Vladimir Cuperman, Niftybox LLB; Frank Mertz, Christoph Erdmann and Peter Vary, Aachen University; and Gernot Kubin, Graz University of Technology) suggested by the codec authors.? We believe it to be stable and useful, but recommend it be pubished as an Experimental RFC while further experience is gained."
' added by Amy Vezza

[Ballot discuss]
Since both documents on this ballot are Experimental, no IETF
Standards-Track document is involved.  The posted IPR Statement

offers royalty-free access to the technology if it is needed to
implement a standard.  If we do not make a standard, they are
not obligated to provide royalty-free access to the codec.

[Note]: 'Codecs are not an area of strong expertise for IETF, so the AVT charter states that any codec specification would be taken only on a case-by-case basis.  The review of the charter in 2003 admitted this codec, and it did receive both AVT and external review.  From the chairs'' request to publish:  "The codec has been reviewed by the AVT working group and several outside experts (Vladimir Cuperman, Niftybox LLB; Frank Mertz, Christoph Erdmann and Peter Vary, Aachen University; and Gernot Kubin, Graz University of Technology) suggested by the codec authors.  We believe it to be stable and useful, but recommend it be pubished as an Experimental RFC while further experience is gained."
' added by Allison Mankin

[Note]: 'Included as a companion doc in the ilbc payload last call.
Can it be a normative ref for the ilbc payload? Codecs are not an area of strong expertise for IETF, so the AVT charter states that any codec specification would be taken only on a case-by-case basis.  The review of the charter in 2003 admitted this codec, and it did receive both AVT and external review.  From the chairs'' request to publish:  "The codec has been reviewed by the AVT working group and several outside experts (Vladimir Cuperman, Niftybox LLB; Frank Mertz, Christoph Erdmann and Peter Vary, Aachen University; and Gernot Kubin, Graz University of Technology) suggested by the codec authors.  We believe it to be stable and useful, but recommend it be pubished as an Experimental RFC while further experience is gained."
' added by Allison Mankin

[Note]: 'Included as a companion doc in the ilbc payload last call.
Can it be a normative ref for the ilbc payload?

Codecs are not an area of strong expertise for IETF, so the AVT charter states that any codec specification would be taken only on a case-by-case basis.  The review of the charter in 2003 admitted this codec, and it did receive both AVT and external review.  From the chairs'' request to publish:  "The codec has been reviewed by the AVT working group and several outside experts (Vladimir Cuperman, Niftybox LLB; Frank Mertz, Christoph Erdmann and Peter Vary, Aachen University; and Gernot Kubin, Graz University of Technology) suggested by the codec authors.  We believe it to be stable and useful, but recommend it be pubished as an Experimental RFC while further experience is gained."
' added by Allison Mankin

[Note]: 'Included as a companion doc in the ilbc payload last call.
Can it be a normative ref for the ilbc payload?' added by Allison Mankin