I have a "modest proposal" to solve the DSL naming crises.
I think xdsl has a place in the market along with cable, and ftth, and wireless.
Now DSL could deliver 1.3 Gbps on, say one inch of copper, or a much lower rate,
say, 1.5 Mbps, on lengths that can reach businesses or home , but recent press releases
and advancing technology claims by disinterested pre an post IPO technology
companies have invented an increasing number of ways of increasing bandwidth on
increasing lengths of copper. We shall increase forever.
However, I do think there are too many DSL types. I now note there is ADSL,
VDSL, IDSL, SDSL, ADSL-lite, G-lite DSL, DSL lite, CDSL, HDSL, HDSL2,
D.SHDSL, RADSL, BDSL, and tomorrow there may- nay will- be more. Now
most of these are four letter acronyms, and I know we were told to"go forth and
increase", but really, there are just too many. We are in danger of running out of
acronyms.
I can solve this problem.
In software many many years ago in a place far far away, that is, back when people
actually designed compilers, there were many many compilers that translated many
many languages into assembly code. Then there were many compilers that compiled
compilers. Before we all went mad continuing this trend, we were saved by a group of
clever programmers invented the ultimate compiler:
Yet Another Compiler Compiler = YACC.
I propose we create a software tool called YADLS, or "Yadisel", for Yet Another
DSL. This YADSL would not really generate any specification, but you could have it
generate press releases. As input it would take all previous DSL press releases, and
increment dates, visions, market statements, and denigrate all previous forms of DSL,
cable, HFC, and fiber.
First of all, yada-yada-yada is an American slang expression used to say "yes, yes yes,
we all know the rest". Now we can say, "yadisel yadisel yadisel" whenever anyone
bring up DSL; this will save us all a lot of time.
Here are possible keyword options for the UNIX input line.
+a x you enter the prefix letter(s) for your dsl.
* note: we must have error checking to prevent duplication of acronyms.
+y take all previous DSL press releases and increment dates by one year
+c $$$ enter the $ amount in billions you are claiming for this technology
+fu lb ub lower bound and upper bound on the upstream frequency
+fd lb ub lower bound and upper bound on the Down stream frequency
+fv lb ub lower bound and upper bound on voice frequency
+f claimed length in feet
+m claimed length in meters
Now this means we only need ONE DSL, YADSL, with a UNIX command line
parameter string,. For example:
YADSL +a A +y +l 100 +fv 0 4 +fu 30 700 +fu 1000 2200 +m 1500 >
press_release_of_(date).html
would represent ADSL, and deliver a file describing the press release.
I'm sure you will agree this text line is much more satisfactory to a UNIX programmer
or engineer. If you are not a programmer or engineer, then you only read the press
release in any case, conveniently displayed in html, and can believe or not-believe the
claims without bothering to understand the technology. Note I carefully solved the
problem that destroyed that NASA mission, by letting the user use either meters or
feet.
Another parameter would allow increments in the technology, but is somewhat
restricted.
+r n release n of the yadsl standard
This only works for HDSL, for all others it generates a null file. After all, you should be
able to think of a new acronym for an undeployed technology.
I'm sure a good perl programmer could knock this program off in a few days.
One further note- I claim ownership of the ultimate DSL, UDSL. This is delivers 1.3
Gbps dynamically allocated between voice, upstream, and downstream data, and goes
across the US with 1 inch to 3,500 miles or more reach.. I'm working on the IPO
now...well, at least the press release. Does anyone think I'm cheating if I use fiber?
justone opinion |
