70 likes | 135 Views
MAL M PLS A daptation L ayer. SG13 – futures session 25 July 2003. Yaakov (J) Stein. Q5 Service Interworking Brainstorming. MAL is a BAD name for this talk it is about Service Interworking Temporary new definition of SI (broader than Y.1401 definition)
E N D
MALMPLSAdaptationLayer SG13 – futures session 25 July 2003 Yaakov (J) Stein
Q5 Service InterworkingBrainstorming MAL is a BAD name for this talk it is about Service Interworking Temporary new definition of SI (broader than Y.1401 definition) CONSTRUCTION OF ROBUST CLIENT CONNECTIVITY FROM A CONCATENATION OF SUBNETWORKS OF DISSIMILAR TECHNOLOGIES WHILE PRESERVING KEY SERVICE ATTRIBUTES
Focus on MPLS MPLS benefits from experience with ATM, SDH, FR, Ethernet, IP, etc. Many of us believe that MPLS will last forever or for 10 years, whichever comes first We don’t yet sell an MPLS service and we don’t want to
ATM SDH MPLS interface IP FR Coexistence & Migration user services services sold user services
Real-time constant rate Real-time variable rate Non-real-time packet Traffic Types
MatchingTraffic to network Network-specific interfaces increase interworking complexity Not equally easy to put traffic types on networks For example: • RT constant-rate on SDH easy • RT constant-rate on ATM harder • RT constant-rate on MPLS challenging
MAL To facilitate co-existence and migration to MPLS define a single interface per traffic type • MAL-0 type agnostic • MAL-C for real-time constant rate • MAL-V for real-time variable rate • MAL-P for non-real-time packet