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

Magnus,

Thanks for your message.  I agree that 
  http://www.3gpp.org/specs/titles-numbers.htm
is the superior reference link.

> I haven't seem the need of including a reference to the reference 
> implementation of AMR that is available from 3GPP, due to the fact that 
> it simply is one possible implementation.

True, but it is the *reference* implementation.

> Also to go find the reference implementation using the payload format
> specification as starting point seems backwards.

Perhaps your web browser or mail reader has something like a 
mime-types or mailcap file with such a general mapping.

> A direct link to a file in the 3GPP repository is not 
> possible due to the fact that the version number is part of the 
> filename. Future possible update actions will make the link invalid.

Yes, I agree.  Please cite "3GPP TS 26.073" and link to 
  http://www.3gpp.org/specs/titles-numbers.htm

> I can see that you have problems locating the document if you tried it 
> directly without reading some of the information on the 3GPP site. To 
> locate the necessary specification you need to know in which release the 
> document is available, and also have some understanding of the concept 
> of releases. As example, the release 6 directory structure exist but is 
> very empty, this is due to the fact that no document has been approved, 
> at least not in the 26 series. This is also very understandable as the 
> release 6 shall be finalized by summer 2003. Also the numbering scheme 
> regarding versions is good to know.
> 
> One way of finding a specification and in which releases it exist use 
> the title and spec document which can be found here: 
> http://www.3gpp.org/specs/titles-numbers.htm
> 
> 
> Lyndon Nerenberg wrote:
> 
> >>I ask that draft-ietf-avt-rtp-amr and the included Audio/AMR MIME 
> >>type registration please include a direct link to the AMR source code:
> >>
> > 
> >
> >>  3GPP TS 26.073     AMR speech Codec; C-source code
> >>  ftp://ftp.3gpp.org/Specs/latest/Rel-4/26_series/26073-410.zip
> >>
> >
> >This is a bad idea:
> >
> >1) A zip file doesn't make sense as a (possibly normative) reference.
> >
> Lyndon, I could disagree on this, the format for a reference is not that 
> important as long it is possible for people to easy obtain the necessary 
> applications. In this case the zip file contains a word document and the 
> source code. Having this in a single file seem necessary for simple 
> retrieval.
> 
> >
> >2) A URL with a component named "latest" can't be considered a
> >   stable reference.
> >
> This is a stable and by 3GPP approved document. "Latest" refers to that 
> this is the latest approved version of the document. In 3GPP it is 
> possible to change the standards document if the changes is deemed 
> necessary and approved by the community. The pointer is to the version 
> 4.1.0 which is the release 4 version with one update affecting the 
> technical content of the specification. For better understanding on how 
> 3GPP numbers their documents please see: 
> "http://www.3gpp.org/specs/numbering.htm".
> 
> Regards
> 
> 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