I agree with Dale. I have subscriber database of with around 30,000 records and the "churn" in e-mail addresses is much higher than changes in postal information. Of course in (some parts of) the real world, the concept of forwarding, address correction etc exists so that I (sometimes) get notified of the new postal address. In most e-mail cases all I get is a mailer-daemon message. I don't think there is any simple solution to the author contact information problem. Like most things, it will be correct at the time of publication but subject to change in the future. Given that RFCs are archival documents this could only be solved with some large dynamic errata database that nobody is prepared to maintain I am sure. Ole Ole J. Jacobsen Editor and Publisher, The Internet Protocol Journal Cisco Systems Tel: +1 408-527-8972 Mobile: +1 415-370-4628 E-mail: ole@xxxxxxxxx URL: http://www.cisco.com/ipj On Thu, 13 Jan 2011, Worley, Dale R (Dale) wrote: > ________________________________________ > From: ietf-bounces@xxxxxxxx [ietf-bounces@xxxxxxxx] On Behalf Of > Mykyta Yevstifeyev [evnikita2@xxxxxxxxx] > > Mentioning my full contact data makes no sense. I can hardly imagine > that somebody will come to Ukraine, search Kotovsk (that is rather small > town) and than particular street, etc. to ask me about the URI scheme. > Those who want that would prefer to contact me by email. > _______________________________________________ > > In many cases, a person's postal address is more stable and easier > to translate into other contact information than the person's e-mail > address. > > Dale _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf