Method and system for VMAN protocol

Details Method and system for VMAN protocol Method and system for VMAN protocol

2001-01-05

2003-09-09

Nguyen, Chau (Department: 2663)

Multiplex communications

Pathfinding or routing

Switching a message which includes an address header

C370S474000

Reexamination Certificate

active

06618388

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to the field of virtual metropolitan area network (VMAN) topologies and internetwork communications technologies. In particular, the present invention relates to a protocol for use in a VMAN network architecture to route and forward data packets according to the VMAN configuration.
2. Background Information and Description of Related Art
A metropolitan area network (MAN) is a network that interconnects users with computer resources in a geographic area or region larger than that covered by a local area network but smaller than the area covered by a wide area network. The term is typically applied to the interconnection of networks in a city into a single larger network (which may then also offer efficient connection to a wide area network). The amount of data traffic being sent over MANs is increasing at an exponential rate. This is due in part to the increasingly ubiquitous use of the Internet by consumers and businesses, as well as the increasingly bandwidth-intensive nature of the Internet applications that are being deployed.
An important aspect of MANs is the ability of MAN service providers to create virtual private network network connections (VPNs) across a single MAN infrastructure, referred to as a virtual metropolitan area network (VMAN). VMANs allow customers having multiple locations within a metropolitan area to transport private traffic, including virtual local area network (VLAN) traffic, over the shared single MAN.
However, the use of vMANs to handle traffic from multiple customers over a single MAN creates access and security issues. Therefore, it is important to segregate one customer from another so that there is no co-mingling of traffic.
In addition, customer traffic must be transported over the MAN without interfering with the customers' own higher-layer protocols such as DECnet, or private IP subnets. For example, the DECnet Phase IV protocol can cause problems when routed to a Layer
2
MAN because the DECnet protocol changes the media access control (MAC) address in the packet's datalink header. Since duplicate MAC addresses are typically not allowed, MAN service providers end up managing DECnet streams by hand—something which neither the provider nor the customer wants.
Accordingly, a new approach is needed to securely manage traffic in a VMAN network architecture while not interfering with higher level protocols.
SUMMARY
According to one aspect of the invention, a method and system is provided in which a VMAN protocol is used to segregate MAN traffic at a customer and a provider domain level. A switch at the edge of the MAN encapsulates a customer data packet from an initiating 802.1Q customer domain in a new Ethernet header, which is used to specify the IEEE 802.1Q VLAN tags as determined by the customer-related VLAN configurations. A switch at the core of the MAN encapsulates the data packet further in another new Ethernet header, which is used to specify new VMAN tags as determined by the MAN service provider VMAN configurations. The nested encapsulation is repeated as necessary until the data packet is eventually forwarded to a remote switch at the edge of the MAN in accordance with the VMAN configuration, or the source and destination address in the original data packet. The remote switch strips the VMAN tags from the data packet, and forwards the stripped data packet to the receiving 802.1Q customer domain as specified in the IEEE 802.1Q VLAN tag.
According to one aspect of the invention, apparatus are provided to carry out the above and other methods.


REFERENCES:
patent: 4897874 (1990-01-01), Lidinsky et al.
patent: 5027350 (1991-06-01), Marshall
patent: 5088032 (1992-02-01), Bosack
patent: 5095480 (1992-03-01), Fenner
patent: 5115431 (1992-05-01), Williams et al.
patent: 5136580 (1992-08-01), Videlock et al.
patent: 5241682 (1993-08-01), Bryant et al.
patent: 5251205 (1993-10-01), Callon et al.
patent: 5274631 (1993-12-01), Bhardwaj
patent: 5287103 (1994-02-01), Kasprzyk et al.
patent: 5304992 (1994-04-01), Harashima
patent: 5311509 (1994-05-01), Heddes et al.
patent: 5313582 (1994-05-01), Hendel et al.
patent: 5317562 (1994-05-01), Nardin et al.
patent: 5319644 (1994-06-01), Liang
patent: 5345446 (1994-09-01), Hiller et al.
patent: 5353383 (1994-10-01), Uchimura et al.
patent: 5361256 (1994-11-01), Doeringer et al.
patent: 5371852 (1994-12-01), Attanasio et al.
patent: 5394394 (1995-02-01), Crowther et al.
patent: 5394402 (1995-02-01), Ross
patent: 5408469 (1995-04-01), Opher et al.
patent: 5423002 (1995-06-01), Hart
patent: 5426637 (1995-06-01), Derby et al.
patent: 5473599 (1995-12-01), Li et al.
patent: 5473607 (1995-12-01), Hausman et al.
patent: 5485455 (1996-01-01), Dobbins et al.
patent: 5500860 (1996-03-01), Perlman et al.
patent: 5519704 (1996-05-01), Farinacci et al.
patent: 5526489 (1996-06-01), Nilakantan et al.
patent: 5550816 (1996-08-01), Hardwick et al.
patent: 5555256 (1996-09-01), Calamvokis
patent: 5604868 (1997-02-01), Komine et al.
patent: 5617421 (1997-04-01), Chin et al.
patent: 5651002 (1997-07-01), Van Seters et al.
patent: 5666363 (1997-09-01), Osakabe et al.
patent: 5684800 (1997-11-01), Dobbins et al.
patent: 5740171 (1998-04-01), Mazzola et al.
patent: 5742604 (1998-04-01), Edsall et al.
patent: 5752003 (1998-05-01), Hart
patent: 5764636 (1998-06-01), Edsall
patent: 5790541 (1998-08-01), Patrick et al.
patent: 5825772 (1998-10-01), Dobbins et al.
patent: 5872783 (1999-02-01), Chin
patent: 5892912 (1999-04-01), Suzuki et al.
patent: 5910955 (1999-06-01), Nishimura et al.
patent: 5946308 (1999-08-01), Dobbins et al.
patent: 5956335 (1999-09-01), Backes et al.
patent: 5959968 (1999-09-01), Chin et al.
patent: 5959990 (1999-09-01), Frantz et al.
patent: 5978378 (1999-11-01), Van Seters et al.
patent: 6023563 (2000-02-01), Shani
patent: 6035105 (2000-03-01), McCloghrie et al.
patent: 6075776 (2000-06-01), Tanimoto et al.
patent: 6111876 (2000-08-01), Frantz et al.
patent: 6128666 (2000-10-01), Muller et al.
patent: 6147995 (2000-11-01), Dobbins et al.
patent: 6157647 (2000-12-01), Husak
patent: 6163543 (2000-12-01), Chin et al.
patent: 6181699 (2001-01-01), Crinion et al.
patent: 6209649 (2001-04-01), Pringle et al.
patent: 6219699 (2001-04-01), McCloghrie et al.
patent: 6226771 (2001-05-01), Hilla et al.
R. Woodburn, “A Scheme for an Internet Encapsulation Protocol: Version 1,” Request for Comments: 1241, Jul. 1991 (“RFC1241”).
B. Elliston, “Encapsulating IP ith the Small Computer System Interface,” Request for Comments 2143, May 1997, (“RFC2143”).
S. Kent, et al., “IP Encapsulating Security Payload (ESP),” Request for Comments 2406, Nov. 1998, (“RFC2406”).
D. Farinacci, et al., “Generic Routing Encapsulation (GRE),” Request for Comments 2784, Mar. 2000, (“RFC2784”).
S. Hanks, et al., “Generic Routing Encapsulation over IPv4 Networks,” Request for Comments 1702, Oct. 1994, (“RFC1702”).
S. Hanks, et al., “Generic Routing Encapsulation (GRE),” Request for Comments 1701, Oct. 1994, (“RFC1701”).
C. Perkins, “Minimal Encapsulation within IP,” Request for Comments 2004, Oct. 1996, (“RFC2004”).
C. Perkins, “IP Encapsulation within IP,” Request for Comments 2003, Oct. 1996, (“RFC2003”).
W. Simpson, “IP in IP Tunneling,” Request for Comments 1853, Oct. 1995, (“RFC1853”).
P. Srisuresh, “Security Model with Tunnel-mode IPsec for NAT Domains,” Oct. 1999, (“RFC2709”).
D. Provan, “Tunneling IPX Traffic Through IP Networks,” Request for Comments 1234, Jun. 1991, (“RFC1234”).
V. Rawat, et al., “Layer Two Tunneling Protocol (L2TP) over Frame Relay,” Request for Comments 3070, Feb. 2001, (“RFC3070”).
W. Townsley, et al., “Layer Two Tunneling Protocol ‘L2TP’,” Request for Comments 2661, Aug. 1999, (“RFC2661”).
E. Rosen, et al., “Multiprotocol Label Switching Architecture,” Request for Comments 3031, Jan. 2001, (“RFC3031”).
K. Hamzeh et al., “Point-to-Point Tunneling Protocol (PPTP),” Request for Comments 2637, Jul. 1999, (“RFC2637”).
D. McPherson, et al., “VLAN Aggregation for Efficient IP Address Allocation,” Request for Comments 3069, Fe

Affiliated with

Also associated with

Rating

Method and system for VMAN protocol does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method and system for VMAN protocol, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for VMAN protocol will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3086038