North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Verizon Offering Naked DSL in Northeast...

  • From: Bill Stewart
  • Date: Sun Apr 24 04:24:06 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jb5Y/+Nrz9jdB5lo81cTzAGCMn7pNQTvqxh7MiHVcdE8JwXKVNjKONxQ8vGJHgyXNor00pLE/RqSBnz2dv7dAzF7UtviQxhBgbTB0oOIj4XhYj8V8AVZVNs7is2B8stdHO2WtSF+WgxolWaQIPqiZ/NPVcdZAeeazAU621Ypqnk=

> .... PPPoEoL2TPoIPSECoLANEoIPV6oRFC1149.....
What a bunch of mean nasty ugly stuff.
My Sonic.net connection is simply rfc1483 (IP packets on an ATM PVC
with a standard SNAP header), and I think that's probably what SBC is
delivering them.
AT&T's business SDSL and IDSL circuits also work that way, and I think
our business ADSL does too (definitely over Covad, but there may be
some locations we can't get that); I don't know what the AT&T Consumer
folks do, but it's nice to have a design that Just Works, and that
leaves the IP issues to the ISP and doesn't have the ILEC/CLEC messing
with MTU sizes for no good reason.
                  Bill