On 2009/05/27 10:06, Phillips, Addison wrote:
Well then somebody ;-) decide that the consensus
[chair hat on]On the comments received recently (issues 48-54), I plan to evaluate consensus in the next few days. However, I'd appreciate if there were more people contributing to the technical discussion or expressing their preferences (please do so on each issue separately!).
is to remove it and let's be done with it. But at this particular point in the document's development (after after last call), I tend to be allergic to changes, especially ones that a) have never hurt in the past and b) apparently don't hurt anything.
I agree, except that these comments come from our AD (or via our AD, which is essentially the same).
[chair hat off]We may as well agree with this one, which is harmless, so that the commenter feels s/he achieved something :-).
Regards, Martin.
Addison Phillips Globalization Architect -- Lab126 Internationalization is not a feature. It is an architecture.-----Original Message----- From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of Randy Presuhn Sent: Tuesday, May 26, 2009 5:19 PM To: LTRU Working Group Subject: Re: [Ltru] Issue #52: Delete reference to RFC 2860 (Apps #5) Hi -From: "Phillips, Addison"<addison at amazon.com> To: "Randy Presuhn"<randy_presuhn at mindspring.com>; "LTRU WorkingGroup"<ltru at ietf.org>Sent: Tuesday, May 26, 2009 4:41 PM Subject: RE: [Ltru] Issue #52: Delete reference to RFC 2860 (Apps#5)As a technical contributor... Whole-heartedly agree. The reference should be deleted. RandyI agree, although I note it is something that we (in this or previous incarnations as a WG) have never modified: we inheritedit from RFC 3066. Both as co-chair and as contributor.. There *have* been previous requests to get rid of it. I find "we inherited it" rather unconvincing for a bit of text that adds no value whatsoever to the document. Randy
-- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.