Re: draft-ietf-avt-rtp-amr-13.txt -- please include link to source code

Magnus,

Thank you for your reply:

> I am not convinced that a informative reference to the implementation 
> directly from the payload format is necessary. There exist ways of 
> finding the reference implementation, it is for example referenced in 
> the AMR main spec TS 26.090. If the draft was not approved and in the 
> rfc-editors queue I would be less inclined to avoid doing this change.

The worst that can happen is that you will be the author of two RFCs 
instead of one.  Would you rather ask the editors for an additional 
reference included (not a huge request) or would you rather be the 
author of a mime type registration that could have had a pointer to 
working code but didn't?  Trust me, including working code is something 
that the rfc editors really like, because the audience loves it.

Imagine these two scenarios.  Joe Random Tech gets a message with MIME 
type Audio/AMR or audio/amrnb and so he goes to the MIME type registration 
and sees that [scenario 1:] the source code may or may not be available 
or [scenario 2:] the source code is a few (dozen key)clicks away.  Which 
is the superior RFC user experience?  Which is the superior 
interoperability experience for your company's products?

> A direct link to to the specification is anyway out of the question. The 
> reason is that the specification may be changed in the future and then a 
> new version number will be given. Somebody may find a bug in the 
> reference implementation (not that unlikely) and a change request is 
> sent in. It that change request is approved the updated specification 
> will be given the version number 4.2.0 which will result in that the 
> filename becomes 26073-420.zip. Due to this a direct link can not be used.

Unless the old versions are going to be deleted, it would be nice to get
the reference code.  The idea of a multi-rate vocoder is a very important 
one, and I feel it is very important to allow quick access to code for 
those who might have any influence on its development, e.g., most people.

Best wishes,
James
 
> Regards
> 
> Magnus Westerlund
> 
> James Salsman wrote:
> 
> >Magnus,
> >
> >Hold on, I've changed my mind
> >
> >The way 
> >>http://www.3gpp.org/specs/titles-numbers.htm
> >is written now, there is no click-path through to the source code.
> >
> >Please explain to me why 
> >>>> ftp://ftp.3gpp.org/Specs/latest/Rel-4/26_series/26073-410.zip
> >can't be used, again?
> >
> >Best wishes,
> >James
> >
> 
> -- 
> 
> Magnus Westerlund 
> 
> Multimedia Technologies, Ericsson Research ERA/T/VA
> ----------------------------------------------------------------------
> Ericsson Radio Systems AB  | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: [email protected]
----------------------------------------------------------
This message was sent to you, since you are subscribed to
[email protected]. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo