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

> 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.

A rather patronizing view of the world. Are you saying this
specification can only be implemented by people who run Windows?

> 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.

If the spec changes, does the URL become invalid? If so, the URL
isn't useful as a reference.

If the URL is static, but the underlying document can change, then the
URL is no good as a reference. A change in the document could lead to
ambiguities in the spec (or even break it outright).  Things work much
better if the reference is to the title of (a specific revision if
applicable) of a standards document.  That type of reference is
immutable, and you can always include a URL to the document as a
_hint_ if you really think it's necessary.  (I doubt that's the case
given the availability of web search engines.)

--lyndon
----------------------------------------------------------
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