Target Choice of PW Type

AKA Wildcard PW TypeGeorge Swallow

swallow@cisco.com

Background

• draft name/tile broken s/b PW Type• draft-swallow-pwe3-spvc-iw brought here

several eons ago• It was decided this work was more appropriate

for MFA Forum because only small bits and pieces directly affected PWE. Those pieces, however were to be brought back here

• Liaison from MFA Forum, presented in Paris requested this functionality

Reference ApplicationTransitioning ATM endpoints to PEs

MPLS

PE

Customer Site

ATM

Customer Site

Customer Site

Customer Site

Customer Site

Customer Site

The Problem (left brain)

• Interworking PE must have no per connection configuration (derives from need for redundancy)

• ATM connection may be for either a frame or cell service

• More effective to reassemble at Interworking PE than at customer facing PE

• Need for reassembly may not be clearly inferrable from ATM signalling message

The problem (right brain)

MPLS

Customer Site

Customer Site

ATM

PE1

PE2

ATM / FR Interworking, FRF5, FRF 8.1 configured

at PAE and/or PME

PNNI / Q.2931

Decision on reassembly must be made before

configuration is known

Label Mapping

The Problem (left brain)

• PW Type must be first signaled from Interworking PE to target PE

• Within PWE3 domain, need for reassembly is only known at the target PE

Proposal

• New PW type that allows target to choose PW Type

• Semantics are– You (the target) decide– I’ll use (assuming I can)– To be compliant with stipulation that PW types

must match, acts as a wildcard - matches anything (except itself)

• May have wider applicability

Next Steps

• Make it a workgroup draft– Fix title

• Get WG feedback