WO2001016766A9 - Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels - Google Patents

Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels

Info

Publication number
WO2001016766A9
WO2001016766A9 PCT/US2000/023774 US0023774W WO0116766A9 WO 2001016766 A9 WO2001016766 A9 WO 2001016766A9 US 0023774 W US0023774 W US 0023774W WO 0116766 A9 WO0116766 A9 WO 0116766A9
Authority
WO
WIPO (PCT)
Prior art keywords
virtual private
private networks
multiple virtual
providers
recited
Prior art date
Application number
PCT/US2000/023774
Other languages
English (en)
Other versions
WO2001016766A1 (fr
Inventor
Bryan Whittle
Kaj Tesink
Original Assignee
Science Applic Int Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Science Applic Int Corp filed Critical Science Applic Int Corp
Priority to JP2001520652A priority Critical patent/JP2003508955A/ja
Priority to AU70887/00A priority patent/AU7088700A/en
Priority to EP00959595A priority patent/EP1222548A4/fr
Publication of WO2001016766A1 publication Critical patent/WO2001016766A1/fr
Publication of WO2001016766A9 publication Critical patent/WO2001016766A9/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L12/5602—Bandwidth control in ATM Networks, e.g. leaky bucket
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2491—Mapping quality of service [QoS] requirements between different networks

Definitions

  • the present invention relates to virtual private networks. More particularly, the present invention relates to virtual private networks wherein in each virtual private network, multiple service providers can be utilized by the trading partners of the virtual private network.
  • the end-to-end service quality of the connection within the virtual private network is guaranteed to meet minimum requirements.
  • the end-to-end service quality encompasses numerous factors including: network services; interoperability; performance; reliability; disaster recovery and business continuity; security; customer care; and trouble handling.
  • the system and method of the present invention is directed to the interconnection of multiple virtual private networks each having multiple service providers.
  • the present invention encompasses a system and method for interconnecting multiple interconnect providers, such as exchange points, exchange networks, direct connect or transit service providers, between the multiple virtual private networks.
  • the present invention employs an end-to-end overseer across the multiple virtual private networks.
  • the ANX system is a business-to-business communications infrastructure that provides a uniform, secured link between trading partners, such as manufacturers and suppliers, in the automotive industry.
  • the ANX is a subscription-based network composed of Certified Service Providers (CSP).
  • CSPs are providers of LP network service that have satisfied certain service end-to-end quality.
  • CASPs are certificate authority service providers.
  • the Certified Exchange Point Operator (CEPO) provides services to interconnect CSPs. CEPOs also must satisfy certain end-to-end service quality requirements.
  • TP Trading Partners
  • the ANX system allows TPs to communicate, exchange information, and transact business with other TPs over the ANX network.
  • the TP may utilize any TCP/IP -compliant application program to exchange information with other TPs.
  • the registered TP selects the TPs with which it wants to communicate and thereafter may gain access to and receive communications from those selected TPs.
  • the ANX system allows each TP to develop its own virtual private network with its customers and vendors.
  • the ANX system significantly reduces the complexity of connecting to multiple trading partners. Since there are diverse communication protocols for the trading partners, separate links are required to access each trading partner. By having a single private network operated under a uniform protocol, interconnectivity between various trading partners is substantially simplified.
  • ANX offers improved end-to-end service quality. For example, if an auto manufacturer needs to place with its parts supplier an order for car seats, the manufacturer may submit over the ANX system its confidential CAD drawings directly to the supplier. The manufacturer may also fill out the order form that the supplier may have for filling orders and timely submit over the ANX system due to its high reliability and performance. The CSP and the CEPO must satisfy certain performance and security requirements in order to be certified under the ANX. The certification process is disclosed in ANX Release 1 Document Publication (TEL-2 02.00), which is incorporated herein by reference in its entirety.
  • the ANX VPN permits the use of a plurality of different IPSec devices. By virtue of the TEL-2 specification and the certification process all of the designated IPSec device are guaranteed to communicate with one another across the ANX VPN.
  • ANX was originated out of the need to interconnect automotive related companies, it is not limited to that industry. Any company/industry may become a TP, e.g. an aerospace company, a healthcare company, etc. ANX has become known as the Advanced Network eXchange.
  • the lag between the systems at each company will be different virtually every time.
  • the connection each has through their service provider, i.e. 14.4K, 28.8K, 56K, ISDN, DSL, Tl, etc., plus the number of servers through which the connection is directed contribute to the resulting time lag between the two companies.
  • the two parties may require a maximum acceptable time lag. Due to the nature of the Internet, it cannot guarantee such a maximum time lag.
  • the two companies may desire that service assistance be available at certain times or 24 hours a day. The Internet has no such guarantees for help availability in a multi-provider environment.
  • VPNs virtual private networks
  • Secure VPNs permit a company to communicate with any other entity on the network without the risk of increased vulnerability to viruses and hackers.
  • VPNs can connect to other VPNs over the Internet by providing authentication, access control, confidentiality and data integrity, there is still no way the end-to-end quality of the connection can be guaranteed to meet a required set of minimum standards in a multi-provider setting.
  • a secure VPN is a communication network that is secured with encryption and authentication.
  • Secure VPNs are based on multiple technologies, for example IPSec, tunneling, certification and shared secret authentication.
  • IPSec is the security standard established by the Internet Engineering task Force (IETF). Tunneling permits private networks to cross the Internet using unregistered IP addresses.
  • the system and method of the present invention utilizes an overseer that defines the service quality, continually qualifies service providers as meeting that service quality, and resolves end-to-end issues across multiple interconnected virtual private networks, such as the ANX.
  • an overseer that defines the service quality
  • service providers continually qualifies service providers as meeting that service quality
  • multiple interconnect providers are interconnected, and the manner in which these interconnect providers are interconnected so that the quality and reliability standards is met are another aspect of the present invention.
  • Still another object of the present invention is to provide a system and method of connecting multiple virtual private networks in which multiple interconnect providers are interconnected so that the end-to-end service quality is met.
  • Fig. 1 is a block diagram of two interconnected virtual private networks according to the present invention
  • Fig. 2 is a configuration of governance and management of separate virtual private networks
  • Fig. 3 is a configuration of governance and management of interconnected virtual private networks according to the present invention.
  • Fig. 4 is an interconnection configuration for governance of multiple inter- connected virtual private networks according to the present invention.
  • Fig. 5 is a flow chart showing contractual obligations according to the present invention.
  • Fig. 6 is a diagram illustrating end-to-end latency in a virtual private network having multiple service providers
  • Fig. 7 is a diagram illustrating end-to-end availability in a virtual private network having multiple service providers
  • Fig. 8 is a diagram illustrating trouble handling in a virtual private network having multiple service providers
  • Fig. 9 is a diagram illustrating an accountability model for a single virtual private network having multiple service providers
  • Fig. 10 is a diagram illustrating an accountability model for multiple virtual private networks having multiple service providers according to the present invention.
  • Fig. 11 is a diagram illustrating end-to-end interconnection of two virtual private networks according to the present invention.
  • Fig. 12 is a diagram illustrating a trouble escalation model for interconnection of two virtual private networks according to the present invention.
  • Fig. 13 is a diagram illustrating a multiple virtual private network fee model for interconnection of two virtual private networks according to the present invention.
  • Fig. 13 is a diagram illustrating interconnection of two virtual private networks using a multiple transit certified service providers according to the present invention
  • Fig. 14 is a diagram illustrating interconnection of two virtual private networks using a single transit certified service provider according to the present invention.
  • Fig. 15 is a diagram illustrating interconnection of two virtual private networks using a multiple transit certified service providers according to the present invention
  • Figs. 16 is a diagram illustrating interconnection of multiple virtual private networks using a multiple transit certified service providers, where no single transit certified service provider connects all of the virtual private networks according to the present invention.
  • Figs. 17a - c are alternative configurations for interconnecting multiple virtual private networks according to the present invention.
  • Fig. 1 shows a block diagram of two interconnected virtual private networks 20 and 22.
  • the present system and method of the interconnecting multiple virtual private networks is not intended to be limited to only these types of networks and has applicability to a wide variety of virtual private networks.
  • Each virtual private network 20 and 22 is shown having a trading partner (TP) 24 and 26, respectively. While Fig. 1 shows only one TP 24 and 26 for each virtual private network, there can in fact be hundred or thousands of such TPs for each virtual private network. Fig. 1 is intended to define the end-to-end service quality concept, and for such a purpose, only one TP 24 and 26 is need for each virtual private network 20 and 22.
  • TP trading partner
  • the end-to-end service quality cannot be achieved by simply interconnecting two virtual private networks, such as 20 and 22, with a wire.
  • the end-to-end service quality incorporates a user-centric philosophy, where the user is the TP or subscriber. The user is guaranteed a minimum level of service encompassing factors that include: network services; interoperability; performance; reliability; disaster recovery and business continuity; security; customer care; and trouble handling. Simply connecting the two virtual private networks 20 and 22 with a wire will not achieve the minimum satisfactory levels for these factors.
  • each VPN 20 and 22 is shown as having its own governance, program management, coopetition policy, contracts, service assurance, and service description. While each virtual private network can operate with a successful level of end-to-end service quality when each VPN is not interconnected to another VPN, the governance, program management, coopetition policy, contracts, service assurance, and service description may need to be revised when interconnecting two or more VPNs in order to maintain the end-to-end service quality. It will be appreciated that at the very least the interconnection of at least two
  • VPNs adds at least one additional level of complexity with regard to service between the VPNs.
  • One resolution is shown in Fig. 3, in which each VPN 20 and 22 maintain their own governance, but the program management, coopetition policy, contracts, service assurance, and service description for the two VPNs 20 and 22 are unified.
  • Such unification means that where the parameters for the program management, coopetition policy, contracts, service assurance, and service description of the two VPNs 20 and 22 are different, the parameter used in one of the networks is chosen as the acceptable minimum standard or a compromise parameter different from the parameter used in each or the VPNs is agreed upon. It is possible that the parameters for cornmunication within each VPN need not change, while the new parameters are used only when communicating between VPNs.
  • Fig. 3 further shows that the system and method contemplate connecting more than two VPNs.
  • each VPN has its own program overseer (POVER) 30, and a global, or multiple virtual private network, overseer 32 is provided to resolve issues between the POVERs 30. Arrows are shown between the POVERs 30 indicating that the POVERs 30 are free to resolve their issues without requiring the GOVER 32.
  • the GOVER is called on when direct POVER-to-POVER resolution fails.
  • Each of the POVERs 30 governs one of the regional VPNs, while the GOVER 32 oversees the interconnection of the VPNs.
  • the GOVER is responsible for end-to-end quality assurance, and in particular acts as an inter- VPN interconnection certifier.
  • the GOVER certifies interconnection facilities, and certifies a global CASP-CASP trust model.
  • the GOVER also is an inter- VPN arbitrator that steps in when POVERs cannot resolve trouble between them. Since the VPNs are used to running their networks in isolation, the interconnection of multiple VPNs has unique issues such as resolving trouble and conflicts between the VPNs and maintenance of minimum end-to-end service quality across the multiple programs. Since the system and method of the present invention are directed to providing specific end-to-end service quality, it must be possible for TPs to quantify the end-to-end service quality levels, and these service quality levels must be sufficient to allow applications to work across the multiple VPNs. Therefore, a high level of metric compatibility and measurement techniques are required. In the ANX type VPN each TP, CSP and CEP must meet specified criteria to become certified and to maintain that certification.
  • the certification provides the TPs or subscribers with confidence that the level or transport and security will meet their business needs.
  • the ANX type VPN utilizes multiple CSPs. On one level it is easier to run a VPN where all TPs are required to use a single CSP.
  • the use of multiple CSPs in the ANX type VPN fosters competition between the CSPs and allows the VPN to reach TPs that may not be serviced by a single CSP.
  • the implementation of multiple CSPs brings with it the drawback of insuring that the CSPs can talk to one another. Whether the connection from one TP to another TP within the same VPN is through a single CSP of two CSPs should be invisible to the TPs.
  • the TPs need never know when one or more CSPs are used for any particular connection.
  • the certification process ensures that the TPs use one of the certified IPSec devices at their premises, and that the CSPs will utilize certified equipment and meet certain metrics so as to achieve the end-to-end service quality guaranteed to the TPs. In this manner, the multiple CSPs will be able to communicate with one another.
  • the CSPs must meet business criteria, technical metrics, ongoing monitoring, trouble-handling criteria, routing registry criteria, and domain name registry criteria to achieve and maintain certification.
  • Fig. 5 shows the contractual obligations of the members of an ANX-type VPN.
  • the TPs 40 contract with the VPN, as denoted in Fig. 5 by the arrows to the overseer 50, and contract with one of the multiple CSPs 42.
  • the CSPs contract with the VPN and with the CEPO 44.
  • the CEPO 44 contracts with the VPN.
  • Each entity is responsible for the services that that entity provides.
  • Fig. 6 illustrates the end-to-end latency within the ANX network.
  • the TP1 router 60 is connected to ANX CSPi 62, which in turn is connected to ANX CEPO 64.
  • TP2 router 66 is connected to ANX CSP 2 68, which is connected to ANX CEPO 64.
  • the packet latency from each router 60 and 66 through the corresponding CSP is 125 msec.
  • the latency through the ANX CEPO is on the order of microseconds. The total packet latency through the network is therefore only slightly more than 250 msec.
  • Fig. 7 illustrates the end-to-end availability metric.
  • the Access network between the TP1 router 60 and the ANX CSPi 62 is permitted to be unavailable 43.80 hours/year.
  • the ANX CSPi 62 may only be unavailable 2.63 hrs./year.
  • the trunk 65 between the ANX CSPi 62 and the ANX CEPO may only be unavailable 1.76 hrs./year.
  • the ANX CEPO may only be unavailable 0.44 hours/year.
  • the foregoing availabilities yield a total of 99.895% availability or 9.22 hours per year downtime.
  • the outline for how trouble is handled within the ANX-type VPN is shown in
  • Fig. 8. There are effectively five layers of trouble handling. At the first level trouble between TPs is handled directly between the two TPs. Similarly, issues between the TPs and the CSPs are handled between the two parties. CSPs and the CEPOs also resolve their troubles between the troubled parties. A network overseer is provided to handle troubles that cannot be handled in the foregoing scenarios. The overseer can take complaints from the TPS, the CSPs, and the CEPOs.
  • a key to providing predictable end-to-end service quality is that the TPs must know the level of service they receive. To this end four service provider accountability levels exist. First, service providers, both interconnect providers and CSPs, must timely fix infrequent service provider troubles. Second, there must be end-to-end service provider cooperation to handle any troubles. Third, recourse must be provided to resolve disputes in the event of disagreement between CSPs and/or interconnect providers. Fourth, recourse must be provided to resolve continued non- compliance with the end-to-end service quality. Referring to Figs. 9 and 10, charts for single VPN and interconnected VPNs are shown, respectively. In Fig. 9, the CSPs 70, CEPOs 72 and CASPs 74 are accountable to the POVER 76.
  • the POVER 76 is accountable to the body 78 representing the TPs.
  • the body 78 is accountable a regional/national arbitration body 80.
  • the CSPs 70, the CEPOs 72, and CASPs 74 are accountable to the POVERs 76.
  • the POVERs 76 are accountable to a GOVER 77, which in turn is accountable to the body 78.
  • the body 78 instead of being accountable to the regional/national arbitration body 80, is accountable to an international arbitration body 82.
  • the GOVER POVER model is but one way to oversee ensuring of the end-to- end service quality and metric compatibility. How the ANX-type networks are connected will be discussed below. In this context there must be five key types of end-to-end technology compatibility: 1 network interconnection that ensures a trading partner on one VPN can reach any trading partner on the other VPN; 2 routing compatibility that ensures any trading partner on one VPN can logically reach nay TP on the other VPN; 3 naming compatibility, e.g. so the web names or e-mail names of any trading partner on one VPN can be resolved to an address that is routable over the two VPNs; 4 IPSec compatibility; and 5 digital security certificate compatibility across multiple VPNs. While Figs. 9 and 10 refer to regional/national VPNs and international arbitration, the VPNs need not be limited to a specific country or geographical area. Any ANX-type VPN, regardless of the location of its subscribers could be interconnected.
  • Fig. 1 illustrated the interconnection of two VPNs 20 and 22, a significant element is missing.
  • Fig. 11 shows two VPNs, that have multiple service providers, which are connected through an inter-program service provider, also called an interconnect provider.
  • the Tel-2 specification is still used as the basic guide in determining the end-to-end service quality, however regional or particular VPN peculiarities, referred to as deltas, must be considered when establishing the interconnected end-to-end service quality standards.
  • Fig. 12 illustrates an end-to-end trouble escalation model. It is expected that CSPs will work together to resolve trouble before contacting a POVER. Similarly, the POVERs and/or the POVERS and the interconnect provider are expected to work together to resolve trouble before contacting the GOVER.
  • the POVERs 100 pay fees to the GOVER to offset the costs of maintaining the GOVER.
  • the VPNs having multiple service providers in turn pay fees to support the POVER.
  • the interconnect providers pay a certification fee to the GOVER for certification as a interconnect provider between VPNs.
  • interconnect provider 120 interconnects VPNs having multiple service providers 122, 124, and 126.
  • Interconnect provider 130 interconnects VPNs having multiple service providers 132 and 126.
  • a TP of VPN 132 must connect through both Interconnect provider 130 and Interconnect provider 120 to reach TPs of either VPN 122 or 124.
  • Figs. 17a-c illustrate potential configurations of multiple VPNs.
  • a first TP 200 connects to a first CSP 210.
  • the CSP210 connects to a first exchange point 220.
  • the TP 200, CSP 210, and the exchange point 220 are within a first VPN 240.
  • a second TP 250 connects to a second CSP 260, which connects to a second exchange point 270.
  • the TP 250, CSP 260 and exchange point 270 are within a second VPN 280.
  • the two VPNs 240 and 280 are interconnected by an
  • Interconnect provider 300 which is connected to the exchange points 220 and 270.
  • Fig. 17b TP 200, CSP 210, exchange point 220 and Interconnect provider 300 are connected in the same manner shown in Fig. 17a. While the second TP 250 is connected to the CSP 260, the exchange point 270 is not provided. Instead CSP 260 is shown as connecting directly to the Interconnect provider 300. This embodiment encompasses the situation where the Interconnect provider 300 and CSP 260 are the same entity or are directly wired.
  • Fig. 17c is similar to Fig. 16b, Except that the interconnect provider also acts as a CSP 320, and a third TP 310 is connected directly to the Interconnect provider 300/CSP 320. As stated previously, while the end-to-end service quality is based upon the
  • TEL-2 the degree to which the TEL-2 specification needs to be modified to interconnect multiple VPNs depends upon the chosen complexity of the interconnection.
  • An xNX-type VPN uses a maximum of two CSPs between any two TPS. A larger value, either three or four, is needed for multiple VPNs.
  • the Interconnect provider will account for one additional CSP, and for configuration set forth in Fig. 16, two Interconnect providers are employed in addition to the two CSPs yielding four CSPs.

Abstract

L'invention concerne un système et un procédé permettant d'interconnecter plusieurs réseaux privés virtuels (VPN) (122, 124, 126, 132) qui utilisent chacun de multiples fournisseurs de services (120, 130), tout en offrant une norme minimale de qualité et de fiabilité de connexions de bout en bout. Le système et le procédé reposent sur l'utilisation d'un surveillant qui résoud les problèmes de bout en bout survenant sur de multiples réseaux privés virtuels interconnectés (122, 124, 126, 132). Lors de la connexion de multiples réseaux privés virtuels (122, 124, 126, 132), de multiples fournisseurs d'interconnexion (120, 130) sont interconnectés de sorte que soit respectée la norme de qualité du service de connexion de bout en bout. L'homologation de fournisseurs de service, de points d'échange, de fournisseurs de services de transit et de dispositifs IPSec permet une interopérabilité pour le cryptage, l'intégrité et l'authentification du produit de tous les vendeurs IPSec. Lorsque deux abonnés utilisent un équipement IPSec certifié, ils peuvent mutuellement se fournir un accès contrôlé à leurs réseaux respectifs.
PCT/US2000/023774 1999-08-31 2000-08-31 Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels WO2001016766A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2001520652A JP2003508955A (ja) 1999-08-31 2000-08-31 複数の仮想専用ネットワークを相互接続するシステムおよび方法
AU70887/00A AU7088700A (en) 1999-08-31 2000-08-31 System and method for interconnecting multiple virtual private networks
EP00959595A EP1222548A4 (fr) 1999-08-31 2000-08-31 Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15156399P 1999-08-31 1999-08-31
US60/151,563 1999-08-31

Publications (2)

Publication Number Publication Date
WO2001016766A1 WO2001016766A1 (fr) 2001-03-08
WO2001016766A9 true WO2001016766A9 (fr) 2002-09-12

Family

ID=22539331

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/023774 WO2001016766A1 (fr) 1999-08-31 2000-08-31 Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels

Country Status (4)

Country Link
EP (1) EP1222548A4 (fr)
JP (1) JP2003508955A (fr)
AU (1) AU7088700A (fr)
WO (1) WO2001016766A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8843643B2 (en) 1998-10-30 2014-09-23 Virnetx, Inc. System and method employing an agile network protocol for secure communications using secure domain names
US8874771B2 (en) 1998-10-30 2014-10-28 Virnetx, Inc. Agile network protocol for secure communications with assured system availability
US8943201B2 (en) 1998-10-30 2015-01-27 Virnetx, Inc. Method for establishing encrypted channel

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10511573B2 (en) 1998-10-30 2019-12-17 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US6502135B1 (en) 1998-10-30 2002-12-31 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US7188365B2 (en) 2002-04-04 2007-03-06 At&T Corp. Method and system for securely scanning network traffic
US7203957B2 (en) 2002-04-04 2007-04-10 At&T Corp. Multipoint server for providing secure, scaleable connections between a plurality of network devices
US7574738B2 (en) * 2002-11-06 2009-08-11 At&T Intellectual Property Ii, L.P. Virtual private network crossovers based on certificates
US7313605B2 (en) 2003-07-03 2007-12-25 At&T Corp. Externally controlled reachability in virtual private networks
US20090129386A1 (en) * 2005-04-29 2009-05-21 Johan Rune Operator Shop Selection
US20070136805A1 (en) * 2005-11-23 2007-06-14 Ils Technology Llc Business-to-business remote network connectivity
US8325732B2 (en) * 2008-12-22 2012-12-04 Rockstar Consortium Us Lp Method for operating multi-domain Provider Ethernet networks

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5485455A (en) * 1994-01-28 1996-01-16 Cabletron Systems, Inc. Network having secure fast packet switching and guaranteed quality of service
US6104701A (en) * 1996-12-13 2000-08-15 International Business Machines Corporation Method and system for performing a least cost routing function for data communications between end users in a multi-network environment
US6226748B1 (en) * 1997-06-12 2001-05-01 Vpnet Technologies, Inc. Architecture for virtual private networks
US6173399B1 (en) * 1997-06-12 2001-01-09 Vpnet Technologies, Inc. Apparatus for implementing virtual private networks
JPH11168496A (ja) * 1997-12-05 1999-06-22 Casio Comput Co Ltd 蓄積型メールシステムの不在通知方法、該システムの転送方法及びメール受信方法
EP0926906A1 (fr) * 1997-12-24 1999-06-30 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Méthode et système pour délivrer des appels à plusieurs domaines de fournisseur de services

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8843643B2 (en) 1998-10-30 2014-09-23 Virnetx, Inc. System and method employing an agile network protocol for secure communications using secure domain names
US8850009B2 (en) 1998-10-30 2014-09-30 Virnetx, Inc. System and method employing an agile network protocol for secure communications using secure domain names
US8868705B2 (en) 1998-10-30 2014-10-21 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US8874771B2 (en) 1998-10-30 2014-10-28 Virnetx, Inc. Agile network protocol for secure communications with assured system availability
US8904516B2 (en) 1998-10-30 2014-12-02 Virnetx, Inc. System and method employing an agile network protocol for secure communications using secure domain names
US8943201B2 (en) 1998-10-30 2015-01-27 Virnetx, Inc. Method for establishing encrypted channel
US9027115B2 (en) 1998-10-30 2015-05-05 Virnetx, Inc. System and method for using a registered name to connect network devices with a link that uses encryption
US9038163B2 (en) 1998-10-30 2015-05-19 Virnetx, Inc. Systems and methods for connecting network devices over communication network
US9037713B2 (en) 1998-10-30 2015-05-19 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US9100375B2 (en) 1998-10-30 2015-08-04 Virnetx, Inc. System and method employing an agile network protocol for secure communications using secure domain names
US9374346B2 (en) 1998-10-30 2016-06-21 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US9386000B2 (en) 1998-10-30 2016-07-05 Virnetx, Inc. System and method for establishing a communication link
US9413766B2 (en) 1998-10-30 2016-08-09 Virnetx, Inc. Method for establishing connection between devices
US9479426B2 (en) 1998-10-30 2016-10-25 Virnetz, Inc. Agile network protocol for secure communications with assured system availability

Also Published As

Publication number Publication date
AU7088700A (en) 2001-03-26
JP2003508955A (ja) 2003-03-04
WO2001016766A1 (fr) 2001-03-08
EP1222548A4 (fr) 2009-04-22
EP1222548A1 (fr) 2002-07-17

Similar Documents

Publication Publication Date Title
US20060227786A1 (en) System and Method for Interconnecting Multiple Virtual Private Networks
US11936518B2 (en) Interconnection platform for real-time configuration and management of a cloud-based services exchange
US11381414B2 (en) System and method for providing network support services and premises gateway support infrastructure
CN108551464B (zh) 一种混合云的连接建立、数据传输方法、装置和系统
US10230588B2 (en) Dynamically deployable self configuring distributed network management system using a trust domain specification to authorize execution of network collection software on hardware components
KR101493312B1 (ko) 가상 네트워크들에서의 신뢰성 및 이용가능성 셋팅을 위한 제어 메커니즘
JP3676989B2 (ja) 新たに規定されたカスタマーネットワークルートの通知を検証する方法
US8239520B2 (en) Network service operational status monitoring
US20040004966A1 (en) Using virtual identifiers to route transmitted data through a network
KR20080008357A (ko) 네트웍 서비스 인프라스트럭처 시스템 및 방법
WO2001016766A9 (fr) Systeme et procede permettant d'interconnecter plusieurs reseaux prives virtuels
Trammell et al. Adding path awareness to the Internet architecture
US10528759B2 (en) Application programming interface bridge for transporting a local request from a local client system to a target server system, and method thereof
US20130138793A1 (en) Network information processing system, a network information processing apparatus and a data processing method
US20030149889A1 (en) Automatic communication and security reconfiguration for remote services
Cisco Release Notes for Cisco 7000 Family for Cisco IOS Release 12.2 T
Michalski et al. Secure ICCP integration considerations and recommendations
US11856117B1 (en) Autonomous distributed wide area network having control plane and order management on a blockchain
Fowler Cloud Network Engineering
Milinović et al. Deliverable DS5. 1.1: eduroam Service Definition and Implementation Plan
CN115955509A (zh) 一种区块链的访问方法及装置
Hughes Requirements of a middleware for managing a large, heterogeneous programmable network
Murphy et al. Comprehensive Routing Security Development and Deployment for the Internet
Cossu et al. D5. 2: XIFI Core Backbone
WO2002089384A2 (fr) Utilisation d'identificateurs virtuels pour l'acheminement de donnees, et traitement de donnees acheminees sur un reseau

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
ENP Entry into the national phase

Ref country code: JP

Ref document number: 2001 520652

Kind code of ref document: A

Format of ref document f/p: F

WWE Wipo information: entry into national phase

Ref document number: 2000959595

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2000959595

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

AK Designated states

Kind code of ref document: C2

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1-14, DESCRIPTION, REPLACED BY NEW PAGES 1-14; PAGES 15-19, CLAIMS, REPLACED BY NEW PAGES 15-19; PAGES 1/10-10/10, DRAWINGS, REPLACED BY NEW PAGES 1/10-10/10; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE