VPN Discovery VPN Discovery Design Team Discussions and Options - - PowerPoint PPT Presentation

vpn discovery vpn discovery
SMART_READER_LITE
LIVE PREVIEW

VPN Discovery VPN Discovery Design Team Discussions and Options - - PowerPoint PPT Presentation

VPN Discovery VPN Discovery Design Team Discussions and Options Design Team Discussions and Options draft- -squire squire- -ppvpn ppvpn- -discovery discovery- -reqts reqts- -00.txt 00.txt draft Matt Squire Hatteras Networks


slide-1
SLIDE 1

VPN Discovery VPN Discovery

Design Team Discussions and Options Design Team Discussions and Options

draft draft-

  • squire

squire-

  • ppvpn

ppvpn-

  • discovery

discovery-

  • reqts

reqts-

  • 00.txt

00.txt

Matt Squire Hatteras Networks

msquire@hatterasnetworks.com

IETF December, 2001

slide-2
SLIDE 2

Design Team Contributors Design Team Contributors

Loa Andersson – Utfors Ron Bonica - MCI Juha Heinanen – Song Networks James Luciani – Crescent Networks Dave McDysan – WorldCom Dave Meyer – Sprint Hamid Ould-Brahim – Nortel Networks Yakov Rekhter – Juniper Networks Eric Rosen – Cisco Tissa Senevirathne – Force 10 Networks Matt Squire - Hatteras Networks

slide-3
SLIDE 3

Discovery Definition Discovery Definition

What is VPN discovery?

– Determination of apriori knowledge

required to signal other endpoint(s) within a VPN.

What knowledge is required?

– Endpoints (obvious) – Signaling method – Anything else?

slide-4
SLIDE 4

Necessity Necessity

Is a (new) solution required? – Methods currently in RFC status include muticast

(RFC 2917) and BGP (RFC 2547)

– Significant majority of design team felt additional

solution necessary, in particular for L2 VPNs.

– Some firmly opposed to additional mechanisms. Some I-Ds out already trying to address the

perceived need

– draft-luciani-ppvpn-vpn-discovery-01.txt

slide-5
SLIDE 5

Requirements Requirements

MUST support inter-provider VPNs MUST have capability for authentication and

access control

MUST respond to changes in timely fashion SHOULD limit VPN information to only those

PEs that are involved in the VPN

MUST provide IP addr of endpoints; MAY

provide additional data

slide-6
SLIDE 6

Timely Fashion Timely Fashion

How quickly must PEs know of VPN

membership changes?

– Seconds? – Minutes? – Epochs?

slide-7
SLIDE 7

Extended Discovery Extended Discovery

What needs to be discovered?

– IP Address (yes!) – Little bit o’ other – Anything and everything

Where does discovery end and signaling

begin?

slide-8
SLIDE 8

Short Version Short Version

Strong majority see need for solutions beyond

those defined in current RFCs – minority firmly against new stuff

Need to understand requirements with respect to

timeliness

Need to determine extensibility requirements Need to merge requirements with PPVPN

requirements draft