View
218
Download
0
Category
Tags:
Preview:
Citation preview
Towards PAR for Segment Protection Switching
M Vinod Kumar
Abhay Karandikar
Agenda
bull Refreshbull Motivationbull Gaps in Present Standardbull Terminology for Segment Protection- agreed so
farbull Summary of Segment Protection Requirementsbull Summary of Segment Protection Solutions
discussed so far in the groupbull Pros and Cons of various solutionsbull Need for a PAR
Prior Artsbull Eilat (May Interim) - Abhay presents SPS as means to solve P2MP protection
ay-Abhay-Protection-Switching-for-P2MP-0508ppt
bull Denver (July Plenary) ndash Jointly by Abhay Bob and Johnnew-sultan-fast-reroute-te-0708-v02pdf
bull Seoul (Sept Interim) - Bob presents interpretations and observations Dave presents issues to address and Vinod presents case for SPS
new-sultan-segment-protection-scaling-0908-v01pps new-martin-PBB-TE-segment-prot-0908-v01pdf new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Dallas (Nov Plenary) -Vinod uploads document on case for SPS and No new work prez due to Lack of time
new-Vinod-SegmentProtectionSwitching-1108-v01doc new-martin-PBB-TE-segment-prot-1108-v00pdf new-sultan-segment-protection-requirements-1108-v02pdf
bull New Orleans (Jan Interim) ndash Dave presents client-server method Wei presents 3-tupple translation Bob presents segment protection for infrastructure and Vinod presents four distinct methods
new-martin-PBB-TE-segment-prot-0109-v00pdfnew-weiyh-segment-protection-0109-v00pdfnew-sultan-segment-protection-technical-proposal-0109-v01pdfnew-vinod-SPS-modeling-0109-v1ppt
Motivation
bull Reference new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Carrier Requirementsndash Infrastructure failure- major cause of outagendash Service providers have the knowledge that
certain links are more prone to failurebull Upcoming areasfloodsroad construction
ndash Protection models must include N1
Gaps in Present Standard
bull PBB-TE has addressed end-to-end protection of P2P TESI within a single domain
bull Service providers need efficient mechanism to protect vulnerable links of the topology
bull N1 is not addressed in PBB-TE
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Agenda
bull Refreshbull Motivationbull Gaps in Present Standardbull Terminology for Segment Protection- agreed so
farbull Summary of Segment Protection Requirementsbull Summary of Segment Protection Solutions
discussed so far in the groupbull Pros and Cons of various solutionsbull Need for a PAR
Prior Artsbull Eilat (May Interim) - Abhay presents SPS as means to solve P2MP protection
ay-Abhay-Protection-Switching-for-P2MP-0508ppt
bull Denver (July Plenary) ndash Jointly by Abhay Bob and Johnnew-sultan-fast-reroute-te-0708-v02pdf
bull Seoul (Sept Interim) - Bob presents interpretations and observations Dave presents issues to address and Vinod presents case for SPS
new-sultan-segment-protection-scaling-0908-v01pps new-martin-PBB-TE-segment-prot-0908-v01pdf new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Dallas (Nov Plenary) -Vinod uploads document on case for SPS and No new work prez due to Lack of time
new-Vinod-SegmentProtectionSwitching-1108-v01doc new-martin-PBB-TE-segment-prot-1108-v00pdf new-sultan-segment-protection-requirements-1108-v02pdf
bull New Orleans (Jan Interim) ndash Dave presents client-server method Wei presents 3-tupple translation Bob presents segment protection for infrastructure and Vinod presents four distinct methods
new-martin-PBB-TE-segment-prot-0109-v00pdfnew-weiyh-segment-protection-0109-v00pdfnew-sultan-segment-protection-technical-proposal-0109-v01pdfnew-vinod-SPS-modeling-0109-v1ppt
Motivation
bull Reference new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Carrier Requirementsndash Infrastructure failure- major cause of outagendash Service providers have the knowledge that
certain links are more prone to failurebull Upcoming areasfloodsroad construction
ndash Protection models must include N1
Gaps in Present Standard
bull PBB-TE has addressed end-to-end protection of P2P TESI within a single domain
bull Service providers need efficient mechanism to protect vulnerable links of the topology
bull N1 is not addressed in PBB-TE
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Prior Artsbull Eilat (May Interim) - Abhay presents SPS as means to solve P2MP protection
ay-Abhay-Protection-Switching-for-P2MP-0508ppt
bull Denver (July Plenary) ndash Jointly by Abhay Bob and Johnnew-sultan-fast-reroute-te-0708-v02pdf
bull Seoul (Sept Interim) - Bob presents interpretations and observations Dave presents issues to address and Vinod presents case for SPS
new-sultan-segment-protection-scaling-0908-v01pps new-martin-PBB-TE-segment-prot-0908-v01pdf new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Dallas (Nov Plenary) -Vinod uploads document on case for SPS and No new work prez due to Lack of time
new-Vinod-SegmentProtectionSwitching-1108-v01doc new-martin-PBB-TE-segment-prot-1108-v00pdf new-sultan-segment-protection-requirements-1108-v02pdf
bull New Orleans (Jan Interim) ndash Dave presents client-server method Wei presents 3-tupple translation Bob presents segment protection for infrastructure and Vinod presents four distinct methods
new-martin-PBB-TE-segment-prot-0109-v00pdfnew-weiyh-segment-protection-0109-v00pdfnew-sultan-segment-protection-technical-proposal-0109-v01pdfnew-vinod-SPS-modeling-0109-v1ppt
Motivation
bull Reference new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Carrier Requirementsndash Infrastructure failure- major cause of outagendash Service providers have the knowledge that
certain links are more prone to failurebull Upcoming areasfloodsroad construction
ndash Protection models must include N1
Gaps in Present Standard
bull PBB-TE has addressed end-to-end protection of P2P TESI within a single domain
bull Service providers need efficient mechanism to protect vulnerable links of the topology
bull N1 is not addressed in PBB-TE
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Motivation
bull Reference new-Protection-Vinod-Case-for-Segment-Protection-0908-v1pps
bull Carrier Requirementsndash Infrastructure failure- major cause of outagendash Service providers have the knowledge that
certain links are more prone to failurebull Upcoming areasfloodsroad construction
ndash Protection models must include N1
Gaps in Present Standard
bull PBB-TE has addressed end-to-end protection of P2P TESI within a single domain
bull Service providers need efficient mechanism to protect vulnerable links of the topology
bull N1 is not addressed in PBB-TE
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Gaps in Present Standard
bull PBB-TE has addressed end-to-end protection of P2P TESI within a single domain
bull Service providers need efficient mechanism to protect vulnerable links of the topology
bull N1 is not addressed in PBB-TE
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Definitions of Segmentbull A Segment is a single link or a sequence of links and bridges providing connectivity between
two bridges The segment is bounded at each end by a Provider Network Port (PNP) A bridge lying within the segment is a BCB A segment endpoint bridge is a BCB or an IB-BEB
bull A Primary segment is a segment along whose path one or more TESIs have been coincidently provisioned
bull A Backup segment is a segment having the same endpoint bridges as the primary segment but whose path is otherwise disjoint from the primary segment
bull An Infrastructure Segment is Sequence of links and bridges that protects atleast one TESI coincident with it
bull A Data Path Segment is portion of a TESI bounded by a PNP at each endndash Multiple Data Path segments can be associated with an infrastructure segment
bull Infrastructure Protection - Preserve connectivity of all TESIs transiting an active infrastructure segment on the failure of one or more links or bridges associated with that segment
bull Data Path Protection - Preserve connectivity of a TESI in the presence of a TESI data path failure occurring within the active TESI segment due to link failure node failure FDB corruption etc
bull M1 Protection ndash Support multiple backup segments (Mge1) to which traffic can be switched in the event of the failure of the primary segment The backup segment having the highest provisioned priority value among operational backup segments is selected to be the active segment Should support Load Balancing M = 3 atleast
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Types of Segment Protection Schemes
bull Infrastructure Segment Protection
bull Data Path Segment Protection
There is an agreement on the requirements for Infrastructure Segment Protection
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Infrastructure Segment Protection Requirements
new-sultan-segment-protection-requirements-0109-v01pdfnew-irene-Segment-Protection-Requirements-0309-v01pptbull Maintain the same or better quality of transport as offered by PBB-TEbull End-to-end integrity must be honoredbull Solution must be operationally simple and should not require large number
of provisioning actionbull Solution shall not switch traffic when there is no fault unless required by
management commandsbull Shall have minimal impact on bridge architecturebull Shall support N1 protection group with load sharing supportbull Address the relatively high failure rate of particular links or bridges within a
networkbull Address the likelihood of concurrent failures occurring in different segments
of a networkbull Allow maintenance activities to be performed independently in different
segments of the networkbull Provide an efficient means of protecting portions of a PtMP TESI
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Segment Protection Solutions
bull Segment Protection Solutions can be broadly classified in three typesndash Hierarchical (Client server by Dave Triple Q
by Vinod Tejas)ndash Cascaded (Tuple switch by Wei ZTE BB-BEB
model by Vinod)ndash Port redirection by Bob
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Hierarchical Segment Protectionbull This is also known as Client-Server model (Dave) or Triple MAC (Vinod)bull Upgrade the BCBs at the edges of the segment to IB-BEBs and provide a PBB
hierarchal (8021ah 2661) S-tagged interface (8021ah 254)1048766bull Each segment is now a new (server layer ) TESI in a regular PBB-TE 11 TESI PG
with the corresponding TESI CCM integrity coverage
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Cascaded Segment Protection
bull Also known as 3-tupple translation (Wei Yuehua) or Enhanced BB-BEB (Vinod)
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Overlay Segment Protection
bull Also known as port-redirect (Bob Sultan) bull Only addresses Infrastructure Segment Protection Switchingbull Special logic needed at AIB and PIB to correlate the faults and port-
redirect or switch the TESI without forwarding ambiguity
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Features Hierarchical PBB-TE 3-Tupple Translation
Port-redirect
Data Frame size Increase Same Same
Standards Impact None Minor Minor
Hardware Logic Same as 1ah Same as 1ah Same as 1ad
Placement at the BEB HW complexity increase
Minimum HW complexity
Same HW logic
Control Plane Logic (AIB) None None Yes
Retracing Yes Yes None
Protection Scope Group of TESIs TESI Group of TESI
Data Path Integrity Yes Yes No
Blind Switch No No Yes
Scalability Yes Yes No
CCM complexity Per Segment Per TESI per AIB or PIB
Reinforcing Proposals E-NNI v2 in MEF and IEEE
E-NNI v2 in MEF and IEEE
No
Alternate competing Standards
No No G8032 v2
Support for Infrastructure Yes Yes Yes
Forwarding Ambiguity No No No
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
PAR
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
What do we get
bull Protection segments are pre-provisioned to allow sub-50ms protection switching
bull The segments forming protection group are constantly monitored
bull Optimal network resource utilizationndash By protecting portion of e2e TESIndash By supporting load sharing with N1ndash By supporting minimal provisioning for
protection
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Value Proposition
bull Segment Protection has same economic feasibility as that of Backbone Edge Bridges
bull The protection mechanism is applicable to any topologybull Improves network utilization by not performing e2e
protection whenever possiblebull Reduces provisioning complexity of e2e protection
mechanism by protecting portion of e2e transportbull Enables protection of critical portion of a packet transportbull Enables efficient protection of branches of P2MP
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
OAM requirements
bull OAM shall reuse PBB-TE OAM components
bull No need to use unreliable control plane
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
What would IEEE specify
bull Amendment to Qayndash Amend 1ag
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Title
bull IEEE standard for Local and Metropolitan Area Networks --- Virtual Bridged Local Area Networks --- Amendment --- Transport Segment Protection Switching
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Scope What project is
bull The scope of this project is to define feature extension of 8021Q (2005) supporting protection of critical portion of the provisioned or traffic engineered services by offering at-least the same guarantee as offered originally by the traffic engineered services with minimal impact on existing standards
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Scope What Project is not
bull The project will only provide features necessary to support external management plane command or control plane
bull The selection of protection segment and bandwidth management either through management commands or by control plane is outside the scope of this project
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Scope Required Featuresbull The features specified in this project enhance support and rely on the PBB (IEEE
8021ah) PBB-TE (IEEE 8021Qay) and CFM (IEEE-8021ag) standards In doing so it shallndash Maintain the same or better quality of transport as offered by PBB-TEndash End-to-end integrity must be honoredndash Solution must be operationally simple and should not require large
number of provisioning actionndash Solution shall not switch traffic when there is no fault unless required by
management commandsndash Shall have minimal impact on bridge architecturendash Shall support N1 protection group with load sharing supportndash Address the relatively high failure rate of particular links or bridges
within a networkndash Address the likelihood of concurrent failures occurring in different
segments of a networkndash Allow maintenance activities to be performed independently in different
segments of the networkndash Provide an efficient means of protecting portions of a PtMP TESI
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Purpose
bull An important objective of provisioned packet transport is to efficiently protection switch the trafficndash Use less network resourcesndash Sub-50 ms resiliencyndash Build on existing standard building blocksndash Provide aggregate protection of all TESI
bull This project will amend the 1Q standard
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Need for Project
bull Currently there is no mechanism to manage portion of a (provisioned) packet transport that is liable to fail more often than other portion of the packet transport
bull The project will address OAMP and protection switching of critical portion of the end-to-end packet transport and support N1 load sharing
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Stakeholders
bull Developers and users of networking for Provider network environments including networking IC developers switch and NIC vendors and users
Thank-you
Thank-you
Recommended