- Test - lists.nanog.org

RE: MPLS in metro access networks
by Irwin Lazar 15 Nov '01

15 Nov '01

MPLS is also useful as a VPN provisioning tool in the Metro space, especially to allow the provisioning of end-to-end PVCs regardless of Layer 2 transport. For example, a service provider could use MPLS-VPNs to link sites on its Ethernet MAN to sites on its DSL or Frame Relay services. Also, you may wish to check out Riverstone's collection of papers on Etherent, MANs and MPLS available at: http://www.riverstonenet.com/technology/ and the MPLS Resource Center - www.mplsrc.com Irwin -----Original Message----- From: srihari varada [mailto:varada@txc.com] Sent: Thursday, November 15, 2001 11:12 AM To: nanog(a)merit.edu Subject: MPLS in metro access networks Hello: I have heard some stressing the role of MPLS in metro access networks. It is difficult for me to visualize the need for it in them while it is not so difficult to understand the utility (load balancing and fault restoration etc.) of it in the metro backbone networks. To characterize metro access networks in the context, the following is provided: -- aggregates traffic from residential (arriving via broadband access links such as xDSL, Cable) and business consumers (arriving via broadband access links such as xDSL and high speed links such as Ethernet or SONET) -- funnels aggregated traffic to metro backbone networks for destination hosts in the local metro region or remote regions across the internet regional and backbone networks. Majority of such access networks are SONET/ATM based (I didn't come across any case of Gig Ethernet. However, I do not preculde it). Thus, there are two questions: -- Are there known RBOCs/ILECs and CLECs entrenching MPLS in the said network scope? (I do not see many major ILECs in the un-official MPLS service providers list being circulated but it may mean little) -- If so, what motivates them to do so? Any analysis of the driving forces is appreciated. Regards, Srihari Varada

2 1

RE: Photo Op: You too can have your picture taken with a.root-ser vers.net
by Larson, Matt 15 Nov '01

15 Nov '01

Chris Woodfield wrote: > IIRC, Verisign operates every gtld-servers.net server, That's correct: VeriSign Global Registry Services operates the name servers and ancillary equipment at all 13 com/net/org name server sites, which are distributed throughout the world. > Does Verisign use the same hardware and OS on all of these > servers, or are the vendors distributed? We are in the process of diversifying all aspects of the com/net/org name server constellation: name server software, name server hardware and OS, and network hardware and OS. Our goal is to eliminate the possibility of a single hardware or software defect affecting all the sites. Matt -- Matt Larson <mlarson(a)verisign.com> VeriSign Global Registry Services

2 1

RE: MPLS in metro access networks
by Quibell, Marc 15 Nov '01

15 Nov '01

soooo...Label switching assigns labels to packet headers which results in less time and processing looking up routes, and instead relies upon a label index for forwarding decisions? Hence my statement "faster switching/routing and less processing":) Marc -----Original Message----- From: Michael Cohen [mailto:mcohen@thrupoint.net] Sent: Thursday, November 15, 2001 10:56 AM To: Quibell, Marc Subject: RE: MPLS in metro access networks I hope so:) -----Original Message----- From: Quibell, Marc [mailto:mquibell@icn.state.ia.us] Sent: Thursday, November 15, 2001 10:46 AM To: 'mcohen(a)thrupoint.net'; nanog(a)merit.edu Subject: RE: MPLS in metro access networks Are we talking about Multiprotocol Label Switching? Marc -----Original Message----- From: Michael Cohen [mailto:mcohen@thrupoint.net] Sent: Thursday, November 15, 2001 10:45 AM To: nanog(a)merit.edu Subject: RE: MPLS in metro access networks And I'm not sure what faster switching/routing has to do with MPLS:) I believe one of the ideas behind MPLS benefiting metro access networks is using MPLS to deliver layer 2 VPNs across an MPLS enabled core thus simulating leased lines for access clients...but I'm sure somebody will correct me if I'm wrong. There seems to be some hype for Martini draft VPNs and large enterprise customers in metro areas. Cheers, -Michael Cohen -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Quibell, Marc Sent: Thursday, November 15, 2001 10:20 AM To: 'srihari varada'; nanog(a)merit.edu Subject: RE: MPLS in metro access networks I would think faster switching/routing and less processing would be wanted in any mid-to-large sized network...I'm not sure what load balancing and fault restoration has to do with MPLS.... Marc -----Original Message----- From: srihari varada [mailto:varada@txc.com] Sent: Thursday, November 15, 2001 10:12 AM To: nanog(a)merit.edu Subject: MPLS in metro access networks Hello: I have heard some stressing the role of MPLS in metro access networks. It is difficult for me to visualize the need for it in them while it is not so difficult to understand the utility (load balancing and fault restoration etc.) of it in the metro backbone networks. To characterize metro access networks in the context, the following is provided: -- aggregates traffic from residential (arriving via broadband access links such as xDSL, Cable) and business consumers (arriving via broadband access links such as xDSL and high speed links such as Ethernet or SONET) -- funnels aggregated traffic to metro backbone networks for destination hosts in the local metro region or remote regions across the internet regional and backbone networks. Majority of such access networks are SONET/ATM based (I didn't come across any case of Gig Ethernet. However, I do not preculde it). Thus, there are two questions: -- Are there known RBOCs/ILECs and CLECs entrenching MPLS in the said network scope? (I do not see many major ILECs in the un-official MPLS service providers list being circulated but it may mean little) -- If so, what motivates them to do so? Any analysis of the driving forces is appreciated. Regards, Srihari Varada

2 1

RE: MPLS in metro access networks
by Quibell, Marc 15 Nov '01

15 Nov '01

Are we talking about Multiprotocol Label Switching? Marc -----Original Message----- From: Michael Cohen [mailto:mcohen@thrupoint.net] Sent: Thursday, November 15, 2001 10:45 AM To: nanog(a)merit.edu Subject: RE: MPLS in metro access networks And I'm not sure what faster switching/routing has to do with MPLS:) I believe one of the ideas behind MPLS benefiting metro access networks is using MPLS to deliver layer 2 VPNs across an MPLS enabled core thus simulating leased lines for access clients...but I'm sure somebody will correct me if I'm wrong. There seems to be some hype for Martini draft VPNs and large enterprise customers in metro areas. Cheers, -Michael Cohen -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Quibell, Marc Sent: Thursday, November 15, 2001 10:20 AM To: 'srihari varada'; nanog(a)merit.edu Subject: RE: MPLS in metro access networks I would think faster switching/routing and less processing would be wanted in any mid-to-large sized network...I'm not sure what load balancing and fault restoration has to do with MPLS.... Marc -----Original Message----- From: srihari varada [mailto:varada@txc.com] Sent: Thursday, November 15, 2001 10:12 AM To: nanog(a)merit.edu Subject: MPLS in metro access networks Hello: I have heard some stressing the role of MPLS in metro access networks. It is difficult for me to visualize the need for it in them while it is not so difficult to understand the utility (load balancing and fault restoration etc.) of it in the metro backbone networks. To characterize metro access networks in the context, the following is provided: -- aggregates traffic from residential (arriving via broadband access links such as xDSL, Cable) and business consumers (arriving via broadband access links such as xDSL and high speed links such as Ethernet or SONET) -- funnels aggregated traffic to metro backbone networks for destination hosts in the local metro region or remote regions across the internet regional and backbone networks. Majority of such access networks are SONET/ATM based (I didn't come across any case of Gig Ethernet. However, I do not preculde it). Thus, there are two questions: -- Are there known RBOCs/ILECs and CLECs entrenching MPLS in the said network scope? (I do not see many major ILECs in the un-official MPLS service providers list being circulated but it may mean little) -- If so, what motivates them to do so? Any analysis of the driving forces is appreciated. Regards, Srihari Varada

1 0

MPLS in metro access networks
by srihari varada 15 Nov '01

15 Nov '01

Hello: I have heard some stressing the role of MPLS in metro access networks. It is difficult for me to visualize the need for it in them while it is not so difficult to understand the utility (load balancing and fault restoration etc.) of it in the metro backbone networks. To characterize metro access networks in the context, the following is provided: -- aggregates traffic from residential (arriving via broadband access links such as xDSL, Cable) and business consumers (arriving via broadband access links such as xDSL and high speed links such as Ethernet or SONET) -- funnels aggregated traffic to metro backbone networks for destination hosts in the local metro region or remote regions across the internet regional and backbone networks. Majority of such access networks are SONET/ATM based (I didn't come across any case of Gig Ethernet. However, I do not preculde it). Thus, there are two questions: -- Are there known RBOCs/ILECs and CLECs entrenching MPLS in the said network scope? (I do not see many major ILECs in the un-official MPLS service providers list being circulated but it may mean little) -- If so, what motivates them to do so? Any analysis of the driving forces is appreciated. Regards, Srihari Varada

1 0

Re: Rate limiting UDP,Multicast,ICMP
by Brian 15 Nov '01

15 Nov '01

I have alao heard of providers who have rate limited icmp on their own backbone links, or links facing peering partners, just something else to consider.. Brian ----- Original Message ----- From: "David Schwartz" <davids(a)webmaster.com> To: <TGainer(a)e-xpedient.com>; <nanog(a)merit.edu> Sent: Wednesday, November 14, 2001 2:53 PM Subject: Re: Rate limiting UDP,Multicast,ICMP > > > On Tue, 13 Nov 2001 12:42:01 -0500, Thomas Gainer wrote: > > >A little more information. We sell 100Mb Ethernet pipes to the Internet. > >(Yes, there are a few of us left). A fair number of these customers are > >small businesses. Usually, they have servers but very little IT support and > >even less IT know how. My thought is to rate limit UDP and ICMP at the > >customer port to no more than 3Mb/s so WHEN (not if) a customer is > >compromised, the effects are somewhat limited and my MAN pipes have some > >measure protection. The question is, what am I not thinking of? DNS, TFTP > >and such should all operate virtually unaffected, as they are not bandwidth > >hungry services. > > Are you rate limiting only inbound? Or both ways? Are you trying to protect > your customers from attack or prevent them from being the source of attacks > if their machines are compromised? Or both? > > If you rate-limit UDP outbound, you make it very hard for your customers to > source streaming media. If you rate-limit inbound, you make it very hard for > your customers to reflect streaming media. So long as you let your customers > know what you're doing in advance, you shouldn't have any problems. > > You may wish to allow clueful customers to opt out of this filtering > (ideally selectively) if they do wish to do things with high-bandwidth UDP > applications. It wouldn't be unreasonable to require customers opting out of > such filtering to assume responsibility/liability for any floods that might > affect them as a result. You may wish to charge them for your costs associate > with floods they originate that affect others as well. > > DS > >

1 0

Rate limiting UDP,Multicast,ICMP
by Thomas Gainer 14 Nov '01

14 Nov '01

A little more information. We sell 100Mb Ethernet pipes to the Internet. (Yes, there are a few of us left). A fair number of these customers are small businesses. Usually, they have servers but very little IT support and even less IT know how. My thought is to rate limit UDP and ICMP at the customer port to no more than 3Mb/s so WHEN (not if) a customer is compromised, the effects are somewhat limited and my MAN pipes have some measure protection. The question is, what am I not thinking of? DNS, TFTP and such should all operate virtually unaffected, as they are not bandwidth hungry services. Thomas

3 2

Cisco 7206 Reboot / Bus Error
by Gyorfy, Shawn 14 Nov '01

14 Nov '01

What's up? One of my routers rebooted yesterday, this is what I got. System returned to ROM by Bus Error at PC 0x60527D44, address 0xFFFFFFFF As per Cisco's website Mapping Address page, it states Reserved Memory (0x0 5000 0000 - 0x0 FFFF FFFF) [it's a 7206 w/ a NPE]. When I do a 'sh region' I can't find the correlation. If I do 'sh tech-support' I find 0xFFFFFFFF at Timers Counters at CT0 but can't go any further. Has anyone experienced the above error? If so, what action did you take? The system is up and running fine now, it just rebooted but I would like to make sure it doesn't happen again. shawn.

2 1

Strange BGP phantom announce remaining
by Stephane Bortzmeyer 14 Nov '01

14 Nov '01

I probably made a stupid mistake when changing my BGP announces but I cannot see where. We are a customer of Abovenet and Telia in France (we have AS 20766) and we peer with AS 6461 and 1299. We announce one prefix, 80.67.160.0/19. All the looking glasses I've tried see that prefix, including routers at Abovenet. The strange is that people at Colt (try yourself on route-server.colt.net) see two prefixes, 80.67.160.0/19 and 80.67.160.0/21. The second one, more specific, was indeed announced but is no longer sent for six days. Our routers seems correct and displays only one announce: drowzee-bgpd> show ip bgp neighbors 62.4.73.26 advertised-routes Network Next Hop Metric LocPrf Weight Path *> 80.67.160.0/19 62.4.73.30 50 32768 20766 i Total number of prefixes 1 Does you have any idea why routers at Colt still see the old announce? People at Colt have no idea. Abovenet checked on its side and sees only the good prefix. Configuration: Debian "woody", Linux kernel 2.4.9, Zebra routing software 0.91 and 0.92a (hence the copy to the Zebra list). http://lookinglass.gitoyen.net/ if you want to examine our network.

2 2

Rate limiting UDP,Multicast,ICMP
by Thomas Gainer 14 Nov '01

14 Nov '01

Is it common practice for ISPs to rate limit UDP, Multicast and ICMP on a customer connection to reduce the effects of various DOS attacks? On the backbone? TIA, Thomas

5 5