Re: DNSng: where to discuss/get info?
Did you follow the discussions that I initiated on a similar set of topics on the [EMAIL PROTECTED] mailing lists about two years ago? In that thread I proposed something along the lines that you are looking for. I am including my last message on that thread below. Bob Allisat [EMAIL PROTECTED] followed up on that idea and asked why we can't build on it and move towards a solution. If I remember right, the subject line of his message was: "Does IETF stand for Innovation Extermination Task Force?" Shortly after that, the IETF Chair restricted his participation in [EMAIL PROTECTED] mailing list. The problems with DNS are well known. Fixing them in the context of some next generation DNS makes good sense. I am also interested in the answer to your question. Rahmat - is there any WG, or organization, or list, or whatever Rahmat which is actively discussing the TECHNICAL (not political) Rahmat aspect of how a new DNS scheme should be? ...Mohsen. --- From: Mohsen BANAN [EMAIL PROTECTED] To: IETF Mailing List [EMAIL PROTECTED] Subject: Re: Now: Next Generation Domains and DNS -- Was: Re: No More Central Authority: Not NSI/ICAN! Not ORSC! Date: Tue, 26 Jan 1999 00:41:34 -0800 (PST) Content-Type: text/plain; charset=US-ASCII MIME-Version: 1.0 Message-Id: [EMAIL PROTECTED] [This is a summary response which covers comments which were in reply to my: [EMAIL PROTECTED] message with the subject of: Re: Now: Next Generation Domains and DNS -- Was: Re: No More Central Authority: Not NSI/ICAN! Not ORSC! dated Thu, 21 Jan 1999 22:41:13 -0800 (PST).] I ended my previous note, by saying: On Thu, 21 Jan 1999 22:41:13 -0800 (PST), Mohsen BANAN [EMAIL PROTECTED] said: Mohsen ... Mohsen Now, after all of this if there was to be an Mohsen acknowledgment that there is an architectural Mohsen problem here and that this is not a "strings Mohsen parsing" issue which can go either way, then Mohsen may be we can work on solutions Many got the point -- that there is a "notation backwardness" problem. For example: On Fri, 22 Jan 1999 08:42:32 -, "mark.paton" [EMAIL PROTECTED] said: mark I hate to admit it but he has a point! and: On Fri, 22 Jan 1999 14:50:41 +0400, Peter Dawson [EMAIL PROTECTED] said: Peter ... Peter How come the folks don't admit the mistakes and just Peter keepcontinuing.. ?? we all understand it is human to err.. !! and: Now, we just have got to leave behind those who after all of this, still don't get it and can't (or don't want to) follow. I -- and many others -- have known about this notation backwardness for more than 10 years. Prior to last week, I had never brought up this issue publicly. There is a good reason why I chose 1999 as the time to bring it up. That is because, I believe it is only now that we have an opportunity to plant the right seeds so that the "problem" can be fixed over time. Taking advantage of this opportunity to fix it is a lot more reasonable than "living" with it. On Fri, 22 Jan 1999 04:14:55 -0500 (EST), "Theodore Y. Ts'o" [EMAIL PROTECTED] said: Theodore ... Theodore Whether or not you call this a "Problem" depends on your point Theodore of view. But this is reality. Live with it. Ted, you live with it. If you want to. I am an engineer. I try to fix problems when the opportunity presents itself. Please consider what I refer to as the "opportunity to plant the right seeds", with an open mind for a moment. May be it is workable. May be it is not. Worstcase, we live with it. I want to try. Yes. This problem has widespread roots. On Fri, 22 Jan 1999 10:09:02 -0800 (PST), Ned Freed [EMAIL PROTECTED] said: Ned I am in complete agreement with Ted here. I also have issues with the way Ned things work and the way things were done, but I recognize that this stuff is Ned far too widely deployed at far too many levels to change now. Ned, I understand (and respect) the significance of the installed base as much as the next guy. That is why I don't refer to this as a "quick fix" but as a "planting of the seeds" type of an approach. In order to understand what I am proposing we have to consider it in the larger context of Domains and DNS ambiance of 1999. Let's put everything on the table and take a quick look. - We have a DNS-mess grid-lock. At least according to some (me included). The idea of expanding top level domains have gone nowhere. Introducing competition at the root-server and registration level has gone nowhere. General confidence in progress is low ... - Updates to DNS Software (both client and server) for beyond IPv4 addresses are needed. - Updates to DNS Software (both client and server) for security, public keys, certificates, ... are needed. - As phone numbers and Domains keep coming together, the domain notation's backwardness is becoming more visible and significant. - ... Since it
RE: HTML better for small PDAs
John, You make some good points; and, unlike some, I never claim to be right all the time. Would you not concede, though, that coders ( should ) write to implement requirements, which are typically not defined by the coders themselves, but by their "customers" ? The IETF publishes lots of I-Ds which give requirements, rather than coding solutions. The people who write these requirements are not necessarily coders themselves. In my, limited, coding experience, I don't recall finding ASCII diagrams as part of the code. Poor diagrammatic capability is one of the problems I have with ASCII. I am not trying to push a particular format, just to explore other possibilities. You previous point about people choosing to use a "copy that's easier for some people to read" is interesting. Doesn't it imply that we should consider other formats ? At the least, it implies to me that ASCII is far from perfect. IMHO, standards are about far more than writing code; first, and most importantly, they are about achieving agreement. ( Otherwise we could all just go off and write whatever code we want. ) This requires a common mind set, and a suitable level of understanding to form it. I am in favour of making it as easy as possible for common understanding to be reached. After all, the subjects are complex enough to understand, without being hampered by poor communication tools. Regards, Graham Travers Applications Standards Strategist * Tel: +44 1359 235086 * Mobile: 0780 8502536 *Fax: +44 1359 235087 * HW B279, P.O. Box 200, London, N18 1ZF * - Email: [EMAIL PROTECTED] -Original Message- From: John Stracke [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, February 28, 2001 5:06 PM To: [EMAIL PROTECTED] Subject: Re: HTML better for small PDAs [EMAIL PROTECTED] wrote: I have people working for me who write I-Ds, and who HATE the ASCII format that they are forced to use. So much so, that they have threatened never to write another I-D. Do we want to deprive the IETF community of the input of experienced technical people ( and, yes, they ARE ! ), because they are put off by archaic document formats ? Possibly, yes--because code is written in ASCII. A case could be made that someone who isn't comfortable with ASCII can't write code, and someone who can't write code should not be writing standards for how other people should write code. I'm aware that there are holes in this argument; but I think the same can be said of yours. For example, we don't know who these I-D authors you refer to are, so we don't know what I-Ds they've written, or whether their I-Ds have been of value to the IETF community. Unless they speak up for themselves, we don't know what kind of problems they've had, or how valid they are. -- /\ |John Stracke| http://www.ecal.com |My opinions are my own. | |Chief Scientist |===| |eCal Corp. |All I ask is a chance to prove that money can't| |[EMAIL PROTECTED]|make me happy. | \/
Re: FanPageGuide is looking for guides
Dear "Backbone" fan, While evaluating your website at http://www.cs.columbia.edu/~hgs/internet/mbone-faq.html we thought that it might be interesting for you to maintain for instance the http://backbone.fanpageguide.com guide about Backbone. Heh. I think we have a new frontrunner for the 2001 "Unclear on the Concept" Award. ;-) RGF Robert G. Ferrell, CISSP Who goeth without humor goeth unarmed.
RE: How about a 'JOB' as DOMAIN NAMES TRADER?
My Goodness. Perhaps you could find a job at www.timecube.com.
Additionally, please don't spam me again.
-carl
kysi ferul
redwingblakburdz@To: Matthew Schlegel
[EMAIL PROTECTED],
yahoo.com"'[EMAIL PROTECTED]'"
[EMAIL PROTECTED],
[EMAIL PROTECTED]
03/01/01 11:38 AM cc: [EMAIL PROTECTED]
Subject: RE: "How about a 'JOB' as
DOMAIN NAMES TRADER?"
Good Morning-
I'd like to find a receptive ("NON-RACE-BAITING-POLITICS" )firm which is
interested in forming a special dept. in which to trade STRATEGIC DOMAIN
NAMES...just like a COMMODITES TRADER or STOCK BROKERAGE FIRM, and this is
in order to 'CHECK-MATE' the trend in government and corporate hierarchies
to "PROTECT THEIR "GAYNESS" at all costs? What in the HELL does the fact
that WORLD LEADERSHIP right now is MOSTLY gay white males have to do with
the INTERNET?
Well...those same 'dinosaurs' are working with 'ROYALTY" etc...
to perform an act of 'FEUDALISM' on "YOUR" ...power-grids! DO you REALLY
want MEN in DRESSES selling you back YOUR... Inventions Inventiveness
Innovation? Screw THAT! We want a FREE AND CLEAN
INTERNET...NO CENSORS..."NO BUILT-IN 'CONFESSIONAL BOX'! "
The way to make the INTERNET a REALITY in 2001 is to ESTABLISH a
TRADER FLOOR for DOMAIN NAMES! NOW! And then allow the NETIZENS to "POLICE"
their own "NEIGHBORHOOD NETWORKS!"
Why can't US CITIZENS have "TAMPER-PROOF ID?" Why can't 'people of 'COLOR'
get FOCUSED on the FACT that WHITE QUEERS are telling you to HATE WHITEY?
IF htis isn't addressed SOON, we may have to ADOPT a CASTE SYSTEM to
protect WHITE CHILDREN from BOTH WHITE PERVERTS and Non-WHITE "AVENGERS?"
REVOLT NOW!
This Humour Letter is a SAMPLER of the LAFFS you are going to get if you
tune in to "Please Speak Into The French Bread" ( 'A Yankee Way of
Knowledge-Retrieval')
This Letter All Contents Copyright 2001 Kysi Ferul
All RIghts Reserved
[EMAIL PROTECTED]
Matthew Schlegel [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did have problems with call completion throughout most of the day
yesterday, but I think that can be safely attributed to overwelming
call volumes. Normally I do not have any problems with my PCS phone
around 425/206/360 area codes. I've also had my phone around san
jose area with no problems.
Matthew Schlegel
Network Engineer
Crossgain Corporation
- -Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 8:22 AM
To: [EMAIL PROTECTED]
Subject:
So you're saying everything's okay now?
This is consistent with results on my Sprint PCS phone in the 773/312
earthquake or no. I've learned to just not rely on the thing and take
my
measly $20 SLA discount from them on a monthly basis. Can't wait
until GSM
hits Chicago.
I have a Sprint PCS phone, all calls dialed left me with a fast busy
(when I could get carrier) until about about 30 minutes ago.
Now it rings but I get disconnected when the call tries to connect.
Regards,
Chris
- -carl hirsch
network analyst
sargent lundy llc
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use
iQA/AwUBOp58yitAKYXwpQg1EQKVpACg2Bm/fCTnGJ6QaOqspwwfapOEN8oAoJSS
dYEfc1mHRfG92j262wpAIWwT
=pH46
-END PGP SIGNATURE-
Kysi Ferul [EMAIL PROTECTED]
Do You Yahoo!?
Yahoo! Mail Personal Address - Get email at your own domain with Yahoo!
Mail.
rfc-index.txt in xml ?
Hello, i am writting documents referencing many RFCs and to manually convert the ascii of rfc-index.txt in the xml format described in rfc2629.2.4.1 isn't very effective. Where can i find the same list of RFCs in a more computer friendly format than the 'ASCII for humans' of rfc-index.txt. ps: i don't want to start any religion war, i just want not to uselessly redo a boring work if it has been already made.
Re: rfc-index.txt in xml ?
On Thu, Mar 01, 2001 at 01:30:22PM -0500, Jerome Etienne wrote: i am writting documents referencing many RFCs and to manually convert the ascii of rfc-index.txt in the xml format described in rfc2629.2.4.1 isn't very effective. Where can i find the same list of RFCs in a more computer friendly format than the 'ASCII for humans' of rfc-index.txt. See http://xml.resourc.eorg/public/rfc/bibxml/ You can copy the appropriate files to your local machine and then do this: references ... %include.reference.RFC.2629; ... /references -MM -- Michael Mealling| Vote Libertarian! | www.rwhois.net/michael Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#: 14198821 Network Solutions | www.lp.org | [EMAIL PROTECTED]
Re: rfc-index.txt in xml ?
Jerome Etienne wrote: Hello, i am writting documents referencing many RFCs and to manually convert the ascii of rfc-index.txt in the xml format described in rfc2629.2.4.1 isn't very effective. Where can i find the same list of RFCs in a more computer friendly format than the 'ASCII for humans' of rfc-index.txt. ps: i don't want to start any religion war, i just want not to uselessly redo a boring work if it has been already made. I have the entries (as well as I-Ds) as BibTex at http://www.cs.columbia.edu/~hgs/bib/ -- Henning Schulzrinne http://www.cs.columbia.edu/~hgs
Re: HTML better for small PDAs
[EMAIL PROTECTED] wrote: In my, limited, coding experience, I don't recall finding ASCII diagrams as part of the code. Poor diagrammatic capability is one of the problems I have with ASCII. Oh, ASCII art. I dunno; I've never used it. It's often not very useful; it's nice for packet formats, but a lot of the time I think it's done because people believe pictures are better, and ASCII art is the only pictures they can make. If you really can't do without it, check out http://www.sigsoftware.com/emaileffects/ (Mac and Windows) or pbmtoascii (Unix). You previous point about people choosing to use a "copy that's easier for some people to read" is interesting. Doesn't it imply that we should consider other formats ? Argh. My point was *exactly* the opposite: that, when there exist multiple formats, it is likely that some of them will be wrong; therefore, the only safe approach is to have exactly one format. plonk -- /==\ |John Stracke| http://www.ecal.com |My opinions are my own.| |Chief Scientist |=| |eCal Corp. |Round up the usual disclaimers. | |[EMAIL PROTECTED]| | \==/
Re: HTML better for small PDAs
John Stracke wrote: [EMAIL PROTECTED] wrote: In my, limited, coding experience, I don't recall finding ASCII diagrams as part of the code. Poor diagrammatic capability is one of the problems I have with ASCII. Oh, ASCII art. I dunno; I've never used it. A clarification (since somebody called me on it): I've never used it in *Drafts*. As was pointed out, my .signature has it, sort of; but that's the most I've ever done...and I don't even do that any more; I wrote a formatter to do it for me. :-) -- /\ |John Stracke| http://www.ecal.com |My opinions are my own. | |Chief Scientist |===| |eCal Corp. |A ship is safe in a harbor, but that's not what| |[EMAIL PROTECTED]|a ship is for. | \/
Re: I-D ACTION:draft-many-gmpls-architecture-00.txt
On Thu, 01 Mar 2001 23:07:52 EST, "J. Noel Chiappa" said: Wow. An I-D with 25 authors. I see we're starting to emulate the experimental physics community! But what will we do when there are too many names to fit on the first page? Umm.. let the XML DTD flow it onto the second page? ;) Sorry, I couldn't resist ;) /Valdis
