> > Couldn't PBB or even Q-in-Q provide that isolation as well, at least for
> > point-to-point services? I must say that I don't personally have much
> > experience with those, because we tend to connect our customers to
> > EoMPLS-capable routers directly.
> QinQ does nothing to reduce the numbe
Linen,
> As far as I'm concerned, enterprises should just connect their various
sites to the Internet independently, and use VPN
> techniques if and where necessary to provide the illusion of a unified
network. In practice, this illusion of a single
> large LAN (or rather, multiple organization
> -Original Message-
> From: Shane Ronan
> Sent: Thursday, December 31, 2009 1:39 PM
> Subject: Re: Restrictions on Ethernet L2 circuits?
>
> Yipes is still offering services under the Yipes, name, at least in
the
> NY Metro Area.
I based my information on t
Yipes is still offering services under the Yipes, name, at least in the NY
Metro Area.
On Dec 31, 2009, at 3:32 PM, George Bonser wrote:
>> -Original Message-
>> From: Shane Ronan
>> Sent: Thursday, December 31, 2009 12:24 PM
>> Subject: Re: Restrictions
> -Original Message-
> From: Shane Ronan
> Sent: Thursday, December 31, 2009 12:24 PM
> Subject: Re: Restrictions on Ethernet L2 circuits?
>
>
> > (now defunct) Yipes! NAN (National Area Network) product
>
> They don't offer this anymore?
>
Yi
> -Original Message-
> From: Endresen Even
> Sent: Thursday, December 31, 2009 12:41 AM
> Subject: Restrictions on Ethernet L2 circuits?
>
> Hello,
>
> Anyone with opinions on what restrictions a service provider should
and
> should not impose on Ether
> (now defunct) Yipes! NAN (National Area Network) product
They don't offer this anymore?
> -Original Message-
> From: Simon Leinen
> Sent: Thursday, December 31, 2009 8:29 AM
> Subject: Re: Restrictions on Ethernet L2 circuits?
> > Should business customers expect to be able to connect several LANs
> > through an Ethernet L2 ciruit and build a
> > Or should the service provider implement port security and limit the
> > number of MAC addresses on the access ports, forcing the customer to
> > connect a router in both ends and segment their network?
>
> That would make the service less attractive, and also more complex to
> set up and main
witch that gets the deencapsualted traffic is your business.
-Original Message-
From: Endresen Even [mailto:even.endre...@bkk.no]
Sent: Thursday, December 31, 2009 12:41 AM
To: nanog@nanog.org
Subject: Restrictions on Ethernet L2 circuits?
Hello,
Anyone with opinions on what restric
Interesting questions. Here are a few thoughts from the perspective of
an education/research backbone operator that used to be IP only but has
also been offering L2 point-to-point circuits for a few years.
> Should business customers expect to be able to connect several LANs
> through an Ethernet
- "Endresen Even" schreef:
> Hello,
>
> Anyone with opinions on what restrictions a service provider should
> and
> should not impose on Ethernet L2 circuits provided to business
> customers
> wanting to connect several offices?
Although different in concept, but somehwat similair in issue
Hello,
Anyone with opinions on what restrictions a service provider should and
should not impose on Ethernet L2 circuits provided to business customers
wanting to connect several offices?
The service provider's MPLS core network doesn't mind what traffic flows
through the EoMPLS tunnel, but the L
13 matches
Mail list logo
