mirror of https://github.com/tLDP/LDP
This has my first round of changes. My comments to Hal are included using
the DocBook3 tag <comment>.
This commit is contained in:
parent
d18e3848ae
commit
f3f32d8b07
|
@ -128,8 +128,7 @@ back daily :)
|
|||
|
||||
|
||||
|
||||
<ULink URL="mailto:hal@foobox.net">Hal Burgiss</ULink>
|
||||
|
||||
<email>hal@foobox.net</email>
|
||||
|
||||
****************************************************************
|
||||
|
||||
|
@ -163,11 +162,15 @@ back daily :)
|
|||
|
||||
<Para>
|
||||
DSL, or Digital Subscriber Line, is a high-speed Internet access technology
|
||||
|
||||
<comment>I always prefered Digital Subscriber Loop, as that
|
||||
would be the telco terminology.</comment>
|
||||
|
||||
that uses a common copper telephone line (a.k.a. 'loop' in telco parlance).
|
||||
DSL provides a direct, dedicated connection to an ISP via the existing telco
|
||||
network. Designed to run on up to 80% of the telephones available in the
|
||||
United States, and utilizing line-adaptive modulation, DSL provides data
|
||||
speeds up to 8 Mbps.
|
||||
network. DSL is designed to run on up to 80% of the telephones available in the
|
||||
United States, and by using line-adaptive modulation, it is capable of
|
||||
providing data speeds up to 8 Mbps.
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
|
@ -175,25 +178,24 @@ back daily :)
|
|||
use. DSL is typically priced below ISDN, and well below T1 service, yet can
|
||||
provide potentially even greater speeds than T1 without the
|
||||
cost/complexity/availability issues of T1. Since DSL is a dedicated, often
|
||||
'always on' service, it avoids the delays and use charges inherent with ISDN
|
||||
service.
|
||||
'always on' service, it avoids the delays and use charges inherent with ISDN.
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
This HOWTO starts with an overview of the technology surrounding DSL.
|
||||
And includes discussions on qualifying, installing, configuring,
|
||||
troubleshooting and securing a DSL connection. Also included is an Appendix
|
||||
with a <Link LinkEnd="faq">FAQ</Link> a listing of <Link
|
||||
LinkEnd="links">related Links</Link>, and a <Link
|
||||
LinkEnd="glossary">Glossary</Link>.
|
||||
troubleshooting and securing a DSL connection.
|
||||
|
||||
There are also Appendixes including <link linkend="faq">Frequently Asked
|
||||
Questions</link>, a listing of <link linkend="links">related
|
||||
links</link>, and a <link linkend="glossary">glossary</link>.
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
Due to the fast pace of change in the telco and DSL industries, please make
|
||||
sure you have the latest version of this document. The current official
|
||||
version can always be found at <Ulink
|
||||
url="http://www.linuxdoc.org/HOWTO/mini/DSL.htm">http://www.linuxdoc.org/HOWTO/mini/DSL.html</Ulink>
|
||||
url="http://www.linuxdoc.org/HOWTO/">http://www.linuxdoc.org/HOWTO/</Ulink>
|
||||
</Para>
|
||||
|
||||
|
||||
|
@ -345,10 +347,9 @@ back daily :)
|
|||
original ADSL mini HOWTO was published. Originally, ADSL was the primary DSL
|
||||
technology being deployed, but more and more some of the other DSL flavors are
|
||||
entering the picture -- IDSL, SDSL, and RADSL. Thus the renaming from 'ADSL
|
||||
mini HOWTO' to the 'DSL mini HOWTO'. Many other changes as well like PPPoE/A
|
||||
encapsulation becoming more and more common as many ISPs are jumping on
|
||||
this bandwagon too.
|
||||
|
||||
mini HOWTO' to the 'DSL HOWTO'. There have been many other changes in DSL
|
||||
technology as well. PPPoE/A encapsulation has become more and more
|
||||
common, and many ISPs are jumping on that bandwagon.
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
|
@ -361,6 +362,8 @@ back daily :)
|
|||
The latest version of this document can be found at <Ulink
|
||||
URL="http://feenix.eyep.net/ldp/adsl/">http://feenix.eyep.net/ldp/adsl/</Ulink>.
|
||||
|
||||
<comment>You should decide on 1, one, location to list as the home of this HOWTO.</comment>
|
||||
|
||||
</Para>
|
||||
|
||||
</Sect2>
|
||||
|
@ -377,8 +380,7 @@ back daily :)
|
|||
<Para>
|
||||
Any and all comments on this document are most welcomed. Please make sure you have
|
||||
the most current version before submitting corrections! These can be sent to
|
||||
<Ulink url="mailto:hal@foobox.net">hal@foobox.net</Ulink>
|
||||
|
||||
<email>hal@foobox.net</email>
|
||||
</Para>
|
||||
|
||||
</Sect2>
|
||||
|
@ -400,8 +402,8 @@ back daily :)
|
|||
DSL, there are so many 'ifs, ands, and buts' that it is difficult to say
|
||||
anything with any degree of certainty and have it stick. What is true today,
|
||||
may not be quite so true tomorrow. And there are exceptions to almost every
|
||||
rule. And sometimes exceptions to the exceptions. So we will be dealing with
|
||||
generalities to a large degree here. Please keep that in mind.
|
||||
rule. And sometimes exceptions to the exceptions. We will be dealing with
|
||||
generalities to a large degree here, please keep that in mind.
|
||||
|
||||
</Para>
|
||||
|
||||
|
@ -416,6 +418,8 @@ back daily :)
|
|||
it is important to differentiate one type of DSL from another, the full
|
||||
proper name will be used: e.g. RADSL. xDSL also is also commonly used to
|
||||
refer to the various DSL technologies as a group.
|
||||
|
||||
<comment>You should clearly state which you will use in this document, either xDSL or DSL. The last sentence can easily be extended... , but we will be using DSL in this document or something similar.</comment>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -427,17 +431,19 @@ back daily :)
|
|||
companies), and CLECs (Competitive Local Exchange Carriers), or independent
|
||||
providers such as Covad and Rhythms. The latter group is playing a growing
|
||||
role. Both are providing DSL services over existing copper lines.
|
||||
|
||||
<comment> The last two sentences there need a bit of work, but I wasn't sure what to do with them. I'll take a look again later.</comment>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
'CO' is the telco acronym for 'Central Office'. Traditionally a building
|
||||
'CO' is the telco acronym for 'Central Office'. Traditionally this is a building
|
||||
where one end of your phone line physically terminates. The other end
|
||||
terminating at your home, office, or wherever. It will be used here to
|
||||
refer to the termination point regardless of whether it is a traditional
|
||||
Central Office building or other, smaller remote structure, or device.
|
||||
terminates at your home, office, or wherever. It will be used here to
|
||||
refer to the termination point NOT at your home, or office. regardless of whether it is a traditional
|
||||
Central Office building or another, smaller, remote structure or device.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -459,7 +465,7 @@ back daily :)
|
|||
'DSLAM' is the sophisticated hardware device in the telco's CO to which the
|
||||
phone line physically connects, and thus makes DSL happen. Increasingly,
|
||||
telcos are making use of smaller devices like the 'mini-RAM' in remote
|
||||
locations. We'll use 'DSLAM' as a catchall for any device that enables a
|
||||
locations. We'll use 'DSLAM' as a catchall for any device that enables
|
||||
DSL service from a telco.
|
||||
|
||||
</Para>
|
||||
|
@ -470,10 +476,10 @@ back daily :)
|
|||
'Modem' will be used to refer to the end user device that enables a DSL
|
||||
connection to the DSLAM. 'Modem' is indeed the correct terminology since
|
||||
there is MOdulation and DEModulation of the signal. These modems typically
|
||||
have other features too. But some ISPs and manufacturers may be marketing
|
||||
have other features too. Some ISPs and manufacturers may be marketing
|
||||
simply 'routers', 'bridges', or even 'brouters' for this purpose. These are
|
||||
essentially DSL modems with enhancements. A compatible 'modem' of some kind
|
||||
is the minimum hardware requirement from the customer's end of the
|
||||
essentially DSL modems with some enhancements. A compatible 'modem' of some kind
|
||||
is the minimum hardware requirement at the customer's end of the
|
||||
connection.
|
||||
|
||||
</Para>
|
||||
|
@ -503,8 +509,8 @@ back daily :)
|
|||
<Para>
|
||||
Previous versions of this document referred to the modem as an 'ANT' (ADSL
|
||||
Network Termination). While this may be technically correct terminology, it
|
||||
is not used by ISPs, manufacturers, telcos, or most users for that matter,
|
||||
to any extent. So the 'modem' will be just called a modem, regardless of
|
||||
is not used by ISPs, manufacturers, telcos, or most users to any extent.
|
||||
The 'modem' will be just called a modem, regardless of
|
||||
whatever other features it may have (i.e. router or bridge).
|
||||
|
||||
</Para>
|
||||
|
@ -515,6 +521,8 @@ back daily :)
|
|||
PPPoX will be used to refer to PPPoE (PPP over Ethernet) and PPPoA
|
||||
(PPP over ATM) collectively. These protocols are being used by many DSL
|
||||
providers now.
|
||||
|
||||
<comment>Is a scream of agony warranted here?</comment>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -524,8 +532,8 @@ back daily :)
|
|||
The information provided in this document is based on the current state of
|
||||
DSL in the U.S. I would assume there are enough similarities with
|
||||
DSL services outside of the US that this document would still have some
|
||||
merit for everyone. <ULink URL="mailto:hal@foobox.net">Correct
|
||||
me</ULink> if I am wrong!
|
||||
merit for everyone. Correct me if I am wrong by emailing
|
||||
<email>hal@foobox.net</email>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -533,7 +541,7 @@ back daily :)
|
|||
<ListItem>
|
||||
<Para>
|
||||
A '#' will be used to denote a command that typically is run by the root
|
||||
user. Otherwise, a '$' will be used for non-privileged users.
|
||||
user. Otherwise, a '$' will be used as the prompt for non-privileged users.
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
|
@ -604,6 +612,8 @@ back daily :)
|
|||
of DSL compared to traditional telco services, such as T1, is attractive and
|
||||
substantially more affordable for home and small business users.
|
||||
|
||||
<comment> DSL generally does not offer service contracts for home users, while DSL for buisness offers similar SLA (service level agreements) to that offered when getting a T1 line.</comment>
|
||||
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
|
@ -626,9 +636,11 @@ back daily :)
|
|||
|
||||
<ListItem>
|
||||
<BridgeHead renderas=sect3>ADSL</BridgeHead>
|
||||
|
||||
<comment>I tend to think that these would flow better as complete sentences, rather than sentence fragments. The rendering does not lend itself to the partial sentences leading into these paragraphs. Check out both <markup>segmententedlist</markup> and <markup>variablelist</markup> as alternatives to the current markup.</comment>
|
||||
|
||||
<Para>
|
||||
or Asymmetric Digital Subscriber Line. Currently supports downstream rates
|
||||
or Asymmetric Digital Subscriber Line. This DSL type currently supports downstream rates
|
||||
up to 8 Mbps, and upstream of 1024 Kbps, hence the 'asymmetric'. The most
|
||||
widely deployed form of xDSL at this time, and was specifically developed
|
||||
for the home and SOHO markets. The higher downstream rates lends itself to
|
||||
|
@ -675,6 +687,8 @@ back daily :)
|
|||
some providers may be marketing a 'SDSL' service that is really ADSL pinched
|
||||
so that upstream/downstream are the same. Wasn't all this confusing enough
|
||||
already?
|
||||
|
||||
<comment> Why is Symmetric DSL wrong? It IS always symmetric...</comment>
|
||||
|
||||
</Para>
|
||||
|
||||
|
@ -692,6 +706,8 @@ back daily :)
|
|||
provides an additional 16 Kbps over traditional ISDN. It is being marketed
|
||||
by some DSL providers as a low end bit rate option, where line quality is
|
||||
not sufficient for higher speeds such as that of ADSL.
|
||||
|
||||
<comment> What in the HECK is 2B1Q? I've got a total of 8 fiber T1s, and 4 copper t1s coming into our office, and I've NEVER heard of that. Out basic DSS trunks for voice are using AMI, while our internet circuts are using B8ZS. Where can I get more information on this 1B2Q thing?</comment>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
|
Loading…
Reference in New Issue