• No results found

IPv6 Solutions on Juniper Networks

N/A
N/A
Protected

Academic year: 2021

Share "IPv6 Solutions on Juniper Networks"

Copied!
22
0
0

Loading.... (view fulltext now)

Full text

(1)

Copyright © 2003 Juniper Networks, Inc. http://www.juniper.net

IPv6 solution on Juniper Networks

IPv6 solution on Juniper Networks

M

M

-

-

series and T

series and T

-

-

series

series

Internet routers

Internet routers

Ahmed Gueatri

aguetari@juniper.net

April 2003

IPv6 Implementation

IPv6 examples and Case Studies

(2)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 3

IPv6 Qualified Router

What means really Dual Stack?

‹

Addressing & Forwarding

‹

Routing Protocols

‹

Service Richness

‹

Operational Efficiency

IPv4

IPv6

PE 1

PE 1

IPv6 Addressing

‹

Dual IP addressing on the same interface

‹

Neighbor discovery

‹

ICMPv6

interfaces { ge-0/1/0 { unit 0 { family inet { address 157.168.0.5/24; } family inet6 { address 8028:20::1/64; } } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

(3)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 5

Autogeneration of EUI 64-bit

Interface Addresses for IPv6

‹

Stateless auto-configuration

™

Node starts by appending its interface ID (EUI-64) to the

link-local network prefix, fe80::/64

™

Sends router solicitation

™

Receives prefix from router advertisement

‹

Benefits

™

Simplifies host configuration

™

Broadens client coverage

Router Solicitation via ND Router Advertisement via ND Host IP

information configured dynamically

IPv6 Qualified Router for ISPs

What means really Dual Stack?

‹

Addressing & Forwarding

‹

Routing Protocols

‹

Service Richness

‹

Operational Efficiency

IPv4

(4)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 7

Routing Protocols

‹

Static routing

™

May be used with customer sites

‹

IGP

™

IPv6 unicast can be routed by RIPng, OSPFv3, or ISIS

™

Current ISIS backbone don’t need IGP upgrade

™

Current OSPF backbone need to:

‹ Migrate to IS-IS

‹ Or add/deploy OSPFv3

‹

BGP-MP

™

Just add the IPv6 routing in existing M-BGP set-up

™

Can use same design

™

Can be set-up over v4 or v6

‹ Just add v6 routing over BGP/v4 sessions (next-hop!)

‹ Use BGP over v6 in case of IPv6 deployment in IPv4 tunnels

™

Separating BGP sessions for v4 and v6 may also have some advantages

‹ Monitoring, flexibility…

PE 1

PE 1

Static Routing

example

routing-options { rib inet6.0 { static { route 8028:10::1/128 next-hop 8028:25::2; } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

(5)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 9

PE 1

PE 1

RIPng Routing

example

protocols { ripng { group igp { neighbor ge-0/1/0.0; } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

Area 3

OSPFv3

‹

Major changes to accommodate:

™

Address size

™

General protocol semantics

‹

Addressing semantics removed from

OSPF packets and LSAs

™

New LSAs for IPv6 addresses & prefixes

™

OSPF runs on per-link, not per-subnet

™

Flooding scope for LSAs generalized

™

Authentication removed

‹

Benefits

™

Other functions remain the same (e.g.

SPF calculation, area support, etc.)

™

Familiarity - widely deployed IGP

Area 2

AS1

Area 1

(6)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 11

PE 1

PE 1

OSPFv3

example

interfaces { so-0/0/0 { unit 0 { family inet { address 10.19.6.2/24; } family inet6 { address 9009:6::2/64; } } } lo0 { unit 0 { family inet { address 10.245.71.6/32; } family inet6 { address feee::10:255:71:6/128; } } } } protocols { ospf3 { area 0.0.0.2 { interface so-0/0/0.0; interface lo0.0 { passive; } } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

so-0/0/0.0

PE 1

PE 1

External M-BGP

example

interfaces { ge-0/1/0 { unit 0 { family inet { address 11.19.1.2/24; } family inet6 { address ::11.19.1.2/126; } } } } routing-options { autonomous-system 100; } protocols { bgp { group ebgp_both { type external; local-address 11.19.1.2; family inet { unicast; } family inet6 { unicast; } peer-as 1; neighbor 11.19.1.1; } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

ge-0/1/0

(7)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 13

E-BGP Peering over IPv6

Link Local Addresses

‹

E-BGP Peering over IPv6 LLA

™

BGP4+ Peering Using IPv6 Link-local

Address

™

draft-kato-bgp-ipv6-link-local-00.txt

™

Allows use of link-local address for direct

peering connections instead of using global

addresses

‹

How it works

™

Link local addresses can be auto-generated

or manually configured

‹

Benefits

™

Simpler administration

™

Flexibility

‹

NSPIXP6 uses link local address

AS1

AS2

E-BGP

Multicast Routing

‹

Performance and scaling for IPv6 multicast clearly

important

‹

PIMv2 to support for IPv4 and IPv6

‹

Multicast Listener Discovery (MLD) protocol to discover

the presence of multicast listeners

™

Derived from IGMPv2

™

Uses ICMPv6 message type instead of IGMP message types

™

MPDv2 is required for PIM-SSM

(8)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 15

IPv6 Qualified Router for ISPs

What means really Dual Stack?

‹

Addressing & Forwarding

‹

Routing Protocols

‹

Service Richness

‹

Operational Efficiency

IPv4

IPv6

IP Services

‹

Routers must be able to perform intelligent IPv6

packet handling

™

Filtering – Selective forwarding and discarding

™

Monitoring - Sampling, counting, logging, etc.

™

QoS - Policing, shaping, queuing, profiling, etc.

™

Forwarding – Directing packets based on any header

information

‹

All classification and packet handling must be done

in hardware to truly minimize performance impact

‹

IP services and performance must not be mutually

(9)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 17

IP2 Services

Filtering & Policing

0 % 20 % 40 % 60 % 80 % 100 % 120 %

Increasing Number of Packet Filters

Increasing Number of Packet Filters

Packet Forwarding

Packet Forwarding

Internet Processor II ASIC

CPU-based router

‹

Packet filtering

™

DoS attack prevention

™

Comprehensive security

™

E.g. Source Address Filters

‹

Policing

™

Interface-level rate limiting

™

E.g. Bandwidth - limits bps

™

E.g. Maximum burst size

‹

Predictable performance

with rich IPv6 services

‹

IP-II enables significant

functionality with

applications to network

management

™

Security

™

Monitoring

™

Accounting

IP-II

IP-II

Multiple rules may be specified.

Multiple rules may be specified.

Filter Specification

Filter Specification

filter Limit-Customer-A { policer Lim { if-exceeding { bandwidth-limit 1m; burst-size-limit 100k; } then discard; } term 1 { from { source-address { 3ffe:1002:6411::/48; } } then { policer Lim; accept; } } }

All IPv6 Packets Handled By Router

All IPv6 Packets Handled By Router

Microcode

Microcode

Packet

Handling

Programs

Log, syslog Count, Policer, Loss-priority, Forwarding-class

Compile

Compile

IPv6 Filtering

IPv6 source address field

IPv6 source address field

IPv6 destination address field

IPv6 destination address field

TCP/UDP source port field

TCP/UDP source port field

TCP/UDP destination port field

TCP/UDP destination port field

Next header field

Next header field

Traffic class field

Traffic class field

Silent

Silent

Discard

Discard

Forward

Forward

TCP Reset

TCP Reset

Or ICMP

Or ICMP

Unreachable

Unreachable

Routing

Routing

Next Term

Next Term

(10)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 19

PE 1

PE 1

Flexible bandwidth

firewall { family inet6 { filter LimitCE-A2{ policer LimCE-A2 { if-exceeding { bandwidth-limit 1m; burst-size-limit 100k; } then discard; } term 1 { from { source-address { 3ffe:1411:2205::/48; } } then { policer LimCE-A2; accept; } } } } }

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

3ffe:1411:2205::5

Security

‹

Security on routers is more important than ever

™

for customer and infrastructure protection

‹

On-going DoS work in IPv4 to be extended to IPv6

‹

Hardware-based packet handling, filtering optimize key

security actions

(11)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 21

Source Address Verification

‹

uRPF can be configured per-interface/sub-interface

‹

Supports both IPv4 and IPv6

‹

Packet/Byte counters for traffic failing the uRPF check

‹

Additional filtering available for traffic failing check:

™

police/reject

™

Can syslog the rejected traffic for later analysis

‹

Two modes available:

™

Active-paths:

‹

uRPF only considers the best path toward a particular destination

™

Feasible-paths:

‹

uRPF considers all the feasible paths. This is used where routing is

asymmetrical.

PE 1

PE 1

Source Address Verification

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

B3

so-0/0/0.0 ge-0/1/0 3ffe:1411:2205::5 Attack with Source address = 3ffe:1411:2205::5

uRPF

3ffe:1411:2205::/48*[BGP/170] >via so-0/0/0/0.0

(12)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 23

PE 1

PE 1

Real-time DoS Identification

with Destination Class Usage

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

3ffe:1541:2305::/48 so-0/0/0.0 ge-0/1/0 policy-options {

community victim members 100:100; policy-statement set-dest-class term 1 { from { protocol bgp; community victim; } then { destination-class dcu-victim; accept; } } } } interfaces { so-2/0/1 { unit 0 { family inet6 { address feee::10:255:73:2/128; accounting { destination-class-usage; } } } } } routing-options{ forwarding-table{ export set-dest-class; } }

PE 1

PE 1

Real-time DDoS Identification

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

3ffe:1541:2305::/48 so-0/0/0.0 ge-0/1/0

(13)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 25

PE 1

PE 1

Real-time DDoS Identification

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

3ffe:1541:2305::12 so-0/0/0.0 ge-0/1/0 BGP update BGP update 3ffe:1541:2305::12/128 3ffe:1541:2305::12/128 Community 100:100 Community 100:100

QoS

‹

IPv6 header includes traffic class and flow label

™

Traffic class function = DSCP

™

Largely undefined flow label identifies a traffic flow that

needing special handling, I.e. voice, video, etc.

‹

IPv6 routers must be able to use traffic class and flow

(14)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 27

VPNs

‹

VPNs are a valuable service

‹

Provider managed IPv4 VPN models have been successful

‹

Established VPN technologies used for IPv4 must be carried

over to IPv6

‹

Services offered as part of a VPN, I.e. QoS, will still be

required for IPv6

‹

VPN management must be able to support IPv4 and IPv6

traffic

L3 VPN over MPLS

P

P

P

P

P

P

PE 2

PE 2

VPN A

VPN A

Site 3, IPv6

Site 3, IPv6

VPN A

VPN A

Site 1, IPv6

Site 1, IPv6

VPN B

VPN B

Site2, IPv4

Site2, IPv4

VPN B

VPN B

Site 1, IPv4

Site 1, IPv4

PE 1

PE 1

PE 3

PE 3

VPN A

VPN A

Site2, IPv6

Site2, IPv6

CE

CE

A1

A1

CE

CE

B1

B1

CE

CE

A3

A3

CE

CE

A2

A2

CE

CE

B2

B2

P

P

VPN B

VPN B

Site3, IPv4

Site3, IPv4

CE

CE

B3

B3

CE

CE

C1

C1

VPN C

VPN C

Site 1, IPv4

Site 1, IPv4

VPN C

VPN C

Site 2, IPv4

Site 2, IPv4

CE

CE

C2

C2

Static

Static

Routes

Routes

OSPF

OSPF

Routing

Routing

E

E

-

-

BGP

BGP

(15)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 29

IPv6 Qualified Router for ISPs

What means really Dual Stack?

‹

Addressing & Forwarding

‹

Routing Protocols

‹

Service Richness

‹

Operational Efficiency

IPv4

IPv6

Network Management

‹

IPv6 Management must be integrated in existing

management systems

‹

SNMP over v6 with IPv6 MIBs

‹

Intuitive CLI

‹

IPv6 Accounting

‹

APIs (e.g. XML) for OSS integration

™

Reduce latency between new vendor feature/service and

OSS integration

™

Operational efficiency hinges on OSS integration

‹

Router operations over IPv6

(16)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 31

Robustness and Reliability

‹

Common support of features, services on every interface

across all platforms

‹

Same approach for hardware-based packet handling as IPv4

™

Performance is critical

™

Maintaining SLA agreement for IPv4 while operating IPv6

‹

Separation of routing and control planes

‹

Graceful restart mechanisms

™

BGP, OSPF, IS-IS, RSVP, LDP…

‹

Linear software releases continuity to ensure common

support and evolution

Integration of non IPv6 capable

routers

‹

IPv6 in IPv4 tunnels

™

GRE or IP-IP Tunnels

™

Only possible:

‹

with performance (hardware tunneling)

‹

at small scale for manageability

‹

Connecting IPv6 Islands with IPv4 MPLS

(17)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 33

PE 1

PE 1

IPv6 in IPv4 tunnels

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

R

R

v4v4

R

R

v4v4

R

R

v4v4

R

R

v4v4 interfaces { so-0/0/0 { unit 0 { family inet { address 100.255.3.2/24; } } } gr-1/0/0 { unit 0 { tunnel { source 100.255.3.2; destination 100.255.2.1; } family inet6 { address 9009:6::2/64; } } } } so-0/0/0.0 100.255.3.2 100.255.2.1

Connecting IPv6 Islands with IPv4

MPLS (1)

IPv6

MPLS

IPv6

IPv4

IPv6

PE2

‹

IETF Draft as defined in

draft-ietf-ngtrans-bgp-tunnel-04.txt

™

Connecting IPv6 Islands across IPv4 Clouds with BGP

™

Also known as “6PE”

‹

PEs run Dual Stack MP-BGP over IPv4

™

PE and CE exchanges IPv6 routes

™

MPLS LDP/RSVP LSPs are set up using IPv4

‹

Benefits

™

Leverages existing MPLS infrastructure

™

Requires IPv6 support only on PE router

(18)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 35

PE 1

PE 1

Connecting IPv6 Islands with IPv4

MPLS (2)

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

R

R

v4v4

R

R

v4v4

R

R

v4v4

R

R

v4v4 interfaces { so-0/0/0 { unit 0 { family inet { address 100.255.3.2/24; } family inet6; family mpls; } } ge-0/1/0 unit 0 { family inet6 { address 8002::1/126; } } } lo0 { unit 0 { family inet { address 10.245.71.6/32; } family mpls; } } } routing-options { autonomous-system 100; } so-0/0/0.0 100.255.3.2 100.255.2.1 ge-0/1/0

PE 1

PE 1

Connecting IPv6 Islands with IPv4

MPLS (3)

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

R

R

v4v4

R

R

v4v4

R

R

v4v4

R

R

v4v4 protocols { rsvp { interface so-0/0/0.0; } mpls { ipv6-tunneling; label-switched-path to_PE1 { to 10.245.72.6; } interface so-0/0/0.0; } bgp { group to_PE1 { type internal; local-address 10.245.71.6; family inet6 { labeled-unicast { explicit-null; } } export red-export; neighbor 10.245.72.6; } } ospf { traffic-engineering; area 0.0.0.0 { interface so-0/0/0.0; interface lo0.0 { passive; } } so-0/0/0.0 100.255.3.2 100.255.2.1 ge-0/1/0

(19)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 37

PE 1

PE 1

Connecting IPv6 Islands with IPv4

MPLS (4)

P

P

P

P

P

P

PE 2

PE 2

PE 3

PE 3

CE

CE

A1

A1

CE

CE

A2

A2

P

P

CE

CE

B3

B3

CE

CE

C1

C1

R

R

v4v4

R

R

v4v4

R

R

v4v4

R

R

v4v4 # protocols (next) ripng { group to_CE-B3 { export red-import; neighbor ge-0/1/0.0; } } } policy-options { policy-statement red-export { term 1 {

from protocol ripng; then accept; } term 2 { then reject; } } policy-statement red-import { from protocol bgp; then accept; } } so-0/0/0.0 100.255.3.2 100.255.2.1 ge-0/1/0.0

IPv6 Implementation

IPv6 examples and Case Studies

Agenda

(20)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 39

Juniper Networks IPV6 deployment

in R&E and ISPs

Americas

EMEA

APAC

Case 1: direct connection to IPv4

+ IPv6 services

LAN

POS

ATM

GigE…

Switch Switch

Metropolitan,

Regional or

National

Network

Switch

BGP

RIPv6

6bone

IPv6

Service

IPv4

+ IPv6

IPv6 direct peering

interfaces { ge-0/1/0 { unit 0 { family inet { address 192.168.0.5/24; } family inet6 { address 8028:20::1/64; } } } so-0/0/0 { unit 0 { family inet { address 204.146.35.1/30; } family inet6 { address 8028:25::1/64; } } } lo0 { unit 0 { family inet { address 192.168.5.1/32 address 127.0.0.1/32; } family inet6 { address 8028:5::1/128; address ::1/128; } routing-options { routing-options { autonomous-system 100; } } protocols { ripng { group igp { neighbor ge-0/1/0.0; } } bgp { group NREN-4-6 { local-address 204.146.35.1; family inet6 { unicast; } family inet { unicast; } peer-as 64595; neighbor 204.146.35.2; }

(21)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 41

Case 2: remote connection

to IPv6 service

LAN

POS

ATM

GigE…

Switch Switch

Metropolitan,

Regional or

National

Network

Switch

BGP with

v6 addresses

RIPv6

IPv6

Service

IPv4 + IPv6 addresses on each interface

IPv4

+ IPv6

6bone

IPv6 in IPv4 tunnel

IPv6 direct peering

interfaces { ge-0/1/0 { unit 0 { family inet { address 192.168.0.5/24; } family inet6 { address 8028:20::1/64; } } } so-0/0/0 { unit 0 { family inet { address 204.146.35.1/30; } } gr-1/0/0 { unit 0 { tunnel { source 204.146.35.1; # so-0/0/0.0 destination 195.150.10.34; } family inet6 { address 8028:25::1/64; } } } lo0 { unit 0 { family inet { address 192.168.10.1/32 address 127.0.0.1/32; } family inet6 { address 8028:5::1/128; address ::1/128; } routing-options { rib inet6.0 { static { route 8028:10::1/128 next-hop 8028:25::2; } } protocols { ripng { group igp { neighbor ge-0/1/0.0; } } bgp { group peering-v6 { type external; local-address 8028:5::1; # Loopback peer-as 64595; neighbor 8028:10::1; } } }

Pan-European Research Networking

10 Gb/s

backbone

with Juniper

M160s

WDM optical

technology

30 R&E

connected

organizations

European

connectivity

to over 3000

R&E

institutions

RedIRIS Aconet Belnet UNICOM-B CARNet CYNET CESNET Forskningsnettet EENet FUNET RENATER DFN GRNET HUNGARNET RHnet HEAnet GARR LATNET LITNET RESTENA SURFnet UNINETT POL-34 RCTS RoEduNet SANET ARNES SUNET SWITCH UKERNA

Multicast

IP Premium

VPN

IPv6

(22)

http://www.juniper.net

Copyright © 2003 Juniper Networks, Inc. 43

IPv6 Available Features

‹

Available on all M-series and T-series platforms

‹

IS-IS

‹

OSPFv3

‹

MP-BGP over

v4/v6

‹

RIPng

‹

Static

‹

IPv6 VPN

(RFC2547bis)

‹

PIM v2

‹

MLD

‹

Forwarding

in hardware

‹

Addressing

™ Link, site, global ™ Stateless

autoconfiguration

‹

Neighbor discovery

‹

IPv6 Packet Filtering

‹

EUI 64 Autogeneration

‹

Unicast RPF

‹

FBF and CBF for IPv6

‹

Destination/Source

Class Usage

‹

Common support

‹

ICMPv6

‹

SNMP over v6 + MIBs

‹

IP applications

™ Ping, telnet, ssh, ftp… ‹

Transition

™ Configured tunnels ™ Dual stack ™ Transport IPv6 in MPLS

Addressing &

Forwarding

Protocols

Routing

Operations &

Transition

Now

Thank You

References

Related documents

 H3C S7500X switch series comes with IPv4/IPv6 dual-stack platform that provides sophisticated IPv4/IPv6 solutions by supporting multiple tunnels, IPv4/IPv6 Layer 3

Characterization Techniques Test Invasive/ Noninvasive Sample Recovered Usage Standard penetration test Invasive Yes Extensive Cone penetration test Invasive No Extensive

Performance Metrics for VAAI vSphere Plug-in for Array Management SIOC VASA AQDT VADP VASRM Storage DRS HARDWARE * (CONTINUED) Supported Drives FC or SAS HDD

It can be said that the above mentioned articles that deal with food sovereignty implicitly, show the dedication and importance the Government places within

A teleradiology report should contain the type of the service (primary interpretation, second opinion etc.), the name of both the transmitting and receiving sites, the

neighbouring properties the generous gardens and grounds of Green Haven include and ample driveway parking to the front of the bungalow, garage and car port offering..

The findings provided support for different models depend- ing on the SAL domain and the cultural group, after controlling for autoregressive effects and the effects of

• Create, manage, delete site-to-site IPsec VPNs to your virtual private cloud