*> *> (Rename the relevant links under http://www.rfc-editor.org/ to use *> ftp.rfc-editor.org instead of ftp.isi.edu, and that *> 'RFC editor publishes' argument becomes less quibbly and arguably *> more futureproof.) *> The RFC Editor agrees with the futureproofing, and the renaming you suggest has in fact been in progress for some time now. However, the RFC Editor cannot soon remove the original names, because lots of folks have them buried in scripts, and pragmatic continuity is more valuable to the IETF membership than quibbling. Bob Braden
- Re: Acronims' ambiquity Pete Loshin
- Re: Acronims' ambiquity Salvador Vidal
- RE: Acronims' ambiquity bindignavile . srinivas
- RE: Acronims' ambiquity Dawson, Peter D
- RE: Acronims' ambiquity Scott Bradner
- RE: Acronims' ambiquity Dawson, Peter D
- RE: Acronims' ambiquity Pete Loshin
- RE: Acronims' ambiquity Pete Loshin
- RE: Acronims' ambiquity J. Noel Chiappa
- RE: Acronims' ambiquity Bob Braden
- Re: Acronims' ambiquity Bob Braden
- Re: Acronims' ambiquity Matt Crawford
- Re: Acronims' ambiquity Brian E Carpenter
- Re: Acronims' ambiquity Joe Touch
- Re: Acronims' ambiquity Brian E Carpenter