Re: meeting in Yokohama

"xiaodong lee" <[email protected]>
Newsgroups gmane.ietf.idn
Organization CAS&CNIC&CNNIC
Message-ID <00cc01c1fd43$3f5fbe80$4607e29f@xiaodonglee>
Dear John,

Thank you for the suggestion, I see.
I think there are one point to be make clear.
Just shut it down? how about the four drafts?

xiaodong
________________________________________
----- 原始邮件 ----- 
发件人: "John C Klensin" <[email protected]>
收件人: "Xiaodong LEE" <[email protected]>; "James Seng" <[email protected]>; "IETF/IDN WG" <[email protected]>
发送时间: 2002年5月17日 上午 09:28
主题: Re: [idn] meeting in Yokohama


| 
| 
| --On Friday, 17 May, 2002 08:47 +0800 xiaodong lee
| <[email protected]> wrote:
| 
| > I think it is necessary to meet each other, coz there maybe
| > some other things to be decided in face to face meeting for so
| > many  active persons in IDN WG, e.g. next step for IDN.
| > And with that, we should absorb more people to complete the
| > idn-admin which is the great job.
| 
| For whatever it is worth, and with the understanding that I'm
| speaking only for myself, I'd suggest a different model.  We
| should finish the small amount of work that is clearly on IDN's
| agenda and shut it down.  The WG has just dragged on too long
| and accumulated too much baggage and debris.  Then, if you (or
| others) have other agenda items (I know I do), it would be good
| write the ideas down in the form of a proposal for a BOF or a
| draft charter for another WG.  In other words, shutting IDN down
| doesn't terminate all of the work that will now have to be done
| with these names, including examining how they fit into
| applications and how selected applications protocols should be
| extended or modified.  That work is important and should be done
| somewhere.  But there are few, if any, advantages of trying to
| fit it into the IDN WG and we have all observed the
| disadvantages of trying to do so.
| 
| regards,
|     john
| 
|
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.