Service Requirements for Provider Provisioned Virtual Private - - PowerPoint PPT Presentation

▶
service requirements for provider provisioned virtual
SMART_READER_LITE
LIVE PREVIEW

Service Requirements for Provider Provisioned Virtual Private - - PowerPoint PPT Presentation

Aug 31, 2022 103 likes •264 views

Service Requirements for Provider Provisioned Virtual Private Networks (PPVPN) draft-ietf-ppvpn-requirements-00.txt Presented by Dave McDysan March 23, 2001 Service Requirements for PPVPNs 1 Authors M. Carugi (Co-Editor) France Telecom D.

slide-1
SLIDE 1

March 23, 2001 Service Requirements for PPVPNs 1

Service Requirements for Provider Provisioned Virtual Private Networks (PPVPN)

draft-ietf-ppvpn-requirements-00.txt Presented by Dave McDysan

slide-2
SLIDE 2

March 23, 2001 Service Requirements for PPVPNs 2

Authors

Zephion Networks

  • R. Wilder

NTT

  • J. Sumimoto

Sprint

  • A. Nagarajan

Telia

  • F. Johansson

AT&T

  • L. Fang

WorldCom

  • D. McDysan (Co-Editor)

France Telecom

  • M. Carugi (Co-Editor)
slide-3
SLIDE 3

March 23, 2001 Service Requirements for PPVPNs 3

Objectives of Document

  • Define terminology
  • Identify requirements applicable to a number of

approaches

  • Provide a “checklist” to evaluate applicability of

individual approaches

  • Categorized requirements as:

– General – Customer-driven – Service provider driven

  • Many requirements taken from Y.1311, Y.1311.1

(Requires review/ validation by ppvpn WG) – http://nbvpn.francetelecom.com/ituRelated.html

slide-4
SLIDE 4

March 23, 2001 Service Requirements for PPVPNs 4

Definitions and Terminology

  • “Private” in VPN used in ownership sense
  • Customer/organization/subscriber is a set

sites

  • Intranet is sites of single customer
  • Extranet is sites of multiple customers
  • Layered VPN Services: L2 and L3
  • Customer (facing) Equipment (CE) device
  • Provider (facing) Edge (PE) switch/router
  • VPN Tunnels

– L3: MPLS, GRE, IPsec, (add IP/IP) – L2: FR, ATM, MPLS, Ethernet VLAN?

slide-5
SLIDE 5

March 23, 2001 Service Requirements for PPVPNs 5

Reference Model for CE-Based VPNs

VPN tunnel VPN tunnel CE VPN A PE PE PE Device for Network Mgmt Customer- interface CE VPN B SP Network(s) PE Access Network Customer- interface Access Network

slide-6
SLIDE 6

March 23, 2001 Service Requirements for PPVPNs 6

Reference Model for Network-Based VPNs

VPN tunnel VPN tunnel CE VPN A PE Device for Network Mgmt Customer- interface CE VPN B SP Network(s) Access Network Customer- interface Access Network

slide-7
SLIDE 7

March 23, 2001 Service Requirements for PPVPNs 7

General Requirements

  • Support arbitrary topology
  • Constrained distribution of data and routing

information

  • Support overlapping IP addresses
  • Security for data, routing, & access
  • Management of service, resources
  • Interoperability within same solution
  • Interworking between solutions desirable
slide-8
SLIDE 8

March 23, 2001 Service Requirements for PPVPNs 8

Customer Requirements

  • Service provider independence
  • Support unicast and multicast traffic
  • No restriction on CE routing protocol
  • Service Level Agreement support
  • Customer management
  • Security & Integrity
  • Minimal migration impact
  • Dedicated and dial-in access
  • Internet reachable over VPN access network
  • Hybrid VPN scenarios desirable
slide-9
SLIDE 9

March 23, 2001 Service Requirements for PPVPNs 9

Examples of Dual-homing Arrangements

User site PE Network User site PE Network Network PE User site PE Network PE Network Network User site

Backdoor link

User site User site

Backdoor link

PE PE PE

slide-10
SLIDE 10

March 23, 2001 Service Requirements for PPVPNs 10

Service Provider Requirements

  • Scalability: VPNs, sites per VPN, routes per

VPN, change rate

  • Learn VPN membership dynamically
  • Service Level Agreements and Specs
  • Quality of service support
  • Inter-AS (SP) support
  • Isolation of traffic and processing
  • Tunneling mechanism independence
  • Backbone technology independence
  • Provide protection & restoration options
slide-11
SLIDE 11

March 23, 2001 Service Requirements for PPVPNs 11

Service Provider Requirements (continued)

  • Support carrier’s carrier (i.e., ppvpn

wholesale)

  • Management: At least FCAPS
  • Support for migration between solutions
  • Isolation, security, authentication &

identification

  • Provisioning routing, access, security
  • Provide access to value-added services
  • Interoperability between vendors
  • Interworking between solutions
slide-12
SLIDE 12

March 23, 2001 Service Requirements for PPVPNs 12

Next Steps

  • Resolve overlap in outline & content, fill in TBDs
  • Clean up editorial comments
  • Clearly state MUST, MAY, SHOULD
  • Continued alignment with framework
  • Please comment on nbvpn (ppvpn) Email exploder

– What is missing? – What is over specified? – Help resolve OPEN ISSUES in document

  • WG charter goal is submission to IESG for

consideration as Informational RFC after August 2001 meeting

slide-13
SLIDE 13

March 23, 2001 Service Requirements for PPVPNs 13

OPEN ISSUES

  • Precise definition of Port-Based (L2) VPNs

– Are Ethernet VLAN services within scope? – Are only L2 VPNs implemented over IP(MPLS) in scope? Native FR & ATM networks out of scope.

  • Precise definition of CE and PE
  • Align definitions with framework (See 2.x)
  • Give timeframe AND numerical scaling (See )
  • Which identifiers are needed? (See 5.3)
  • What items are important in SLAs? (See 5.5)
slide-14
SLIDE 14

March 23, 2001 Service Requirements for PPVPNs 14

OPEN ISSUES

  • How should QoS be spec’d? (See 5.6)
  • Agree on Management rqmts (See 5.14)

– Detail service creation & provisioning? – Move policy-mgmt to framework doc? – Need information model requirements

  • Include other Tunneling Technologies?

– IP/Optical, IP/Switched Circuit