[Fwd: Re: Wiki Syntax RFC]

2004-02-12 Thread Franck Martin
My apologies... Below is the correct link -Forwarded Message- From: Chris Yarnell <[EMAIL PROTECTED]> I think you really wanted to post: http://tikiwiki.org/tiki-index.php?page=RFCWiki ? :-) > http://tikiwiki.org/tiki-editpage.php?page=RFCWiki Franck Martin [EMAIL PROTECTED] SOP

Wiki Syntax RFC

2004-02-12 Thread Franck Martin
http://tikiwiki.org/tiki-editpage.php?page=RFCWiki I have updated the page toward an RFC. Please look, comment and modify (you may need to register). I'm particularly interested to know if the page is RFC formatted. Cheers Franck Martin [EMAIL PROTECTED] SOPAC, Fiji GPG Key fingerpri

Re: proposal for built-in spam burden & email privacy protection

2004-02-12 Thread Franck Martin
On Fri, 2004-02-13 at 12:46, Ed Gerck wrote: Dean Anderson wrote: > Then using the IETF list as an example, you would need the entire list of > recipients and their public keys, and you would need to send a message > either directly to each of them, one by one, or send a single message with >

Re: proposal for built-in spam burden & email privacy protection

2004-02-12 Thread Ed Gerck
Dean Anderson wrote: > Then using the IETF list as an example, you would need the entire list of > recipients and their public keys, and you would need to send a message > either directly to each of them, one by one, or send a single message with > a session key for each recipient (thousands). T

Multiplication, specifically large numbers by small ones

2004-02-12 Thread Dan Kolis
>Further, any cost increase in email that is less than the cost of bulk >postal mail will not deter genuine spammers. But even the regular user >would feel the crunch if each email cost $0.37. If the IETF had to pay >$0.37 per email, or even $0.15 per email, its 2 million/yr or so budget >would no

Re: going off-list, Re: proposal for built-in spam burden & email privacy protection

2004-02-12 Thread Dean Anderson
On Thu, 12 Feb 2004, Ed Gerck wrote: > Someday, however, users will want to stop using postcards for all > their electronic conversations. At that time, at zero added cost, > we can easily introduce a mandatory per-message burden to spammers > and make it backward compatible (so that we don't d

News Item : US FCC rules 'Pure' VoIP not a phone service

2004-02-12 Thread Richard Shockey
Handing a partial victory to providers of Internet phone services, federal regulators ruled Thursday that voice communications that flow entirely over the Internet are not subject to traditional government regulations. http://news.com.com/2100-7352_3-5158105.html >>>

going off-list, Re: proposal for built-in spam burden & email privacy protection

2004-02-12 Thread Ed Gerck
Folks, Thanks for the diverse and interesting feedback. I'm replying to each message off-list, not to burden the entire ietf.org discussions. I'm also collecting all comments for an Internet draft to be submitted to the IETF. If you have further comments, I suggest you send them to me privately

Re: [secdir] [New-work] WG Review: New IETF Standards Track (newtrk)

2004-02-12 Thread Sam Hartman
One item in the proposed charter concerns me greatly: The working group should also take into account other issues raised by the problem working group and during the newtrk BOF as needed. That does not sound narrowly scoped at all. It might be reasonable to take into account these items as

RE: Visa for Korea

2004-02-12 Thread Ash, Gerald R (Jerry), ALABS
Thanks a lot Gene, for your persistence and follow-through! You've done a real service for the IETF community. It is appreciated. Regards, Jerry -Original Message- From: Gene Gaines [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 7:44 PM To: [EMAIL PROTECTED] Subject: Vis

RE: proposal for built-in spam burden & email privacy protection

2004-02-12 Thread Rod . Walsh
> The real problem isn't from companies who send bulk email and allow you to opt out. Not true (amymore). Opting out involves either a click or and email response. Both are well know methods for the "bad guys" to harvest better email lists and thus this behaviour is a bad idea - even for the "po