rfc9633v5.txt | rfc9633.txt | |||
---|---|---|---|---|
skipping to change at line 2668 ¶ | skipping to change at line 2668 ¶ | |||
B.1. Example A-1: Application Flow Aggregation | B.1. Example A-1: Application Flow Aggregation | |||
This example illustrates multiple App-flows with the same source, | This example illustrates multiple App-flows with the same source, | |||
destination, and traffic specification aggregated into a single | destination, and traffic specification aggregated into a single | |||
DetNet flow service sub-layer. Ingress node 1 aggregates App-flows 0 | DetNet flow service sub-layer. Ingress node 1 aggregates App-flows 0 | |||
and 1 into a service sub-layer of DetNet flow 1. Two ways to | and 1 into a service sub-layer of DetNet flow 1. Two ways to | |||
illustrate this are provided in Figures 1 and 2; the JSON operational | illustrate this are provided in Figures 1 and 2; the JSON operational | |||
data model [RFC8259] corresponding to the diagrams is then shown in | data model [RFC8259] corresponding to the diagrams is then shown in | |||
Figure 3. The address format used in this example is IPv6. | Figure 3. The address format used in this example is IPv6. | |||
Please consult the PDF or HTML copy for the Case A-1 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 1: Case A-1: Application Flow Aggregation | Figure 1: Case A-1: Application Flow Aggregation | |||
Please consult the PDF or HTML copy for the Case A-1 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 2: Case A-1: Stack Details for Application Flow Aggregation | Figure 2: Case A-1: Stack Details for Application Flow Aggregation | |||
Figure 3 contains the operational JSON configuration for the ingress | Figure 3 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figures 1 and 2. "app-0" and "app-1" | aggregation node illustrated in Figures 1 and 2. "app-0" and "app-1" | |||
are aggregated into service sub-layer ssl-1. | are aggregated into service sub-layer ssl-1. | |||
{ | { | |||
"ietf-detnet:detnet": { | "ietf-detnet:detnet": { | |||
"traffic-profile": [ | "traffic-profile": [ | |||
skipping to change at line 2882 ¶ | skipping to change at line 2884 ¶ | |||
B.2. Example B-1: Aggregation Using a Forwarding Sub-layer | B.2. Example B-1: Aggregation Using a Forwarding Sub-layer | |||
As illustrated in Figure 4, DetNet service sub-layer flows 1 and 2 | As illustrated in Figure 4, DetNet service sub-layer flows 1 and 2 | |||
are aggregated into a single forwarding sub-layer. For the same | are aggregated into a single forwarding sub-layer. For the same | |||
destination, multiple DetNet flows use a single forwarding path, and | destination, multiple DetNet flows use a single forwarding path, and | |||
service protection is performed by the corresponding service sub- | service protection is performed by the corresponding service sub- | |||
layer of each flow. The corresponding XML operational data for node | layer of each flow. The corresponding XML operational data for node | |||
"Ingress 1" follows. | "Ingress 1" follows. | |||
Please consult the PDF or HTML copy for the Case B-1 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 4: Case B-1: Aggregation Using a Forwarding Sub-layer | Figure 4: Case B-1: Aggregation Using a Forwarding Sub-layer | |||
Figure 5 contains the operational XML configuration for the ingress | Figure 5 contains the operational XML configuration for the ingress | |||
aggregation node illustrated in Figure 4. In this example, "app-0" | aggregation node illustrated in Figure 4. In this example, "app-0" | |||
and "app-1" are in separate service sub-layers with MPLS labels, and | and "app-1" are in separate service sub-layers with MPLS labels, and | |||
the aggregation happens at forwarding sub-layer afl-1, using MPLS | the aggregation happens at forwarding sub-layer afl-1, using MPLS | |||
labels. | labels. | |||
<interfaces | <interfaces | |||
skipping to change at line 3095 ¶ | skipping to change at line 3098 ¶ | |||
B.3. Example B-2: Service Aggregation | B.3. Example B-2: Service Aggregation | |||
As illustrated in Figure 6, DetNet service sub-layer flows 1 and 2 | As illustrated in Figure 6, DetNet service sub-layer flows 1 and 2 | |||
are aggregated into a service sub-layer of an aggregated flow. | are aggregated into a service sub-layer of an aggregated flow. | |||
Multiple DetNet flows with the same requirements for the same | Multiple DetNet flows with the same requirements for the same | |||
destination are aggregated into a single aggregated DetNet flow, and | destination are aggregated into a single aggregated DetNet flow, and | |||
service protection and resource allocation are performed by an | service protection and resource allocation are performed by an | |||
aggregated DetNet flow service sub-layer and forwarding sub-layer. | aggregated DetNet flow service sub-layer and forwarding sub-layer. | |||
The corresponding JSON operational data for node "Ingress 1" follows. | The corresponding JSON operational data for node "Ingress 1" follows. | |||
Please consult the PDF or HTML copy for the Case B-2 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 6: Case B-2: Example Service Aggregation | Figure 6: Case B-2: Example Service Aggregation | |||
Figure 7 contains the operational JSON configuration for the ingress | Figure 7 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 6. In this example, service | aggregation node illustrated in Figure 6. In this example, service | |||
sub-layer ssl-1 for DetNet flow DN-1 and ssl-2 for DetNet flow DN-2 | sub-layer ssl-1 for DetNet flow DN-1 and ssl-2 for DetNet flow DN-2 | |||
aggregate at service sub-layer DetNet flow asl-1. In this example, | aggregate at service sub-layer DetNet flow asl-1. In this example, | |||
an aggregation service sub-layer, asl-1, is created to aggregate | an aggregation service sub-layer, asl-1, is created to aggregate | |||
ssl-1 and ssl2, and that label is encapsulated in a separate | ssl-1 and ssl2, and that label is encapsulated in a separate | |||
forwarding sub-layer, afl-1, with MPLS labels. | forwarding sub-layer, afl-1, with MPLS labels. | |||
skipping to change at line 3378 ¶ | skipping to change at line 3382 ¶ | |||
B.4. Example C-1: DetNet Relay Service Sub-layer | B.4. Example C-1: DetNet Relay Service Sub-layer | |||
Figure 8 illustrates the DetNet relay node's forwarding sub-layer | Figure 8 illustrates the DetNet relay node's forwarding sub-layer | |||
flows 1 and 2 aggregated into a single forwarding sub-layer. Service | flows 1 and 2 aggregated into a single forwarding sub-layer. Service | |||
protection and resource allocation are performed by the corresponding | protection and resource allocation are performed by the corresponding | |||
service sub-layer and forwarding sub-layer of each flow. Figure 8 | service sub-layer and forwarding sub-layer of each flow. Figure 8 | |||
illustrates both aggregation and disaggregation, and the | illustrates both aggregation and disaggregation, and the | |||
corresponding JSON operational data follows. | corresponding JSON operational data follows. | |||
Please consult the PDF or HTML copy for the Case C-1 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 8: Case C-1: Example Service Aggregation/Disaggregation | Figure 8: Case C-1: Example Service Aggregation/Disaggregation | |||
Figure 9 contains the operational JSON configuration for the ingress | Figure 9 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 8. In this example, a relay | aggregation node illustrated in Figure 8. In this example, a relay | |||
performing aggregation at the forwarding sub-layer is illustrated. | performing aggregation at the forwarding sub-layer is illustrated. | |||
Two DetNet flows -- DN-1 and DN-2 -- are replicated at each service | Two DetNet flows -- DN-1 and DN-2 -- are replicated at each service | |||
sub-layer. The two forwarding sub-layers for the upper path are | sub-layer. The two forwarding sub-layers for the upper path are | |||
aggregated at the forwarding sub-layer with label 20000, and the two | aggregated at the forwarding sub-layer with label 20000, and the two | |||
forwarding sub-layers for the lower path are aggregated at the | forwarding sub-layers for the lower path are aggregated at the | |||
skipping to change at line 4178 ¶ | skipping to change at line 4183 ¶ | |||
Disaggregation | Disaggregation | |||
Figure 11 illustrates the DetNet relay node's service sub-layer flows | Figure 11 illustrates the DetNet relay node's service sub-layer flows | |||
1 and 2 aggregated into a single forwarding sub-layer. Service | 1 and 2 aggregated into a single forwarding sub-layer. Service | |||
protection is performed by the corresponding service sub-layer of | protection is performed by the corresponding service sub-layer of | |||
each flow, and resource allocation is performed by an aggregated | each flow, and resource allocation is performed by an aggregated | |||
forwarding sub-layer for all aggregated flows. Figure 11 illustrates | forwarding sub-layer for all aggregated flows. Figure 11 illustrates | |||
both aggregation and disaggregation, and the corresponding JSON | both aggregation and disaggregation, and the corresponding JSON | |||
operational data follows. | operational data follows. | |||
Please consult the PDF or HTML copy for the Case C-2 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 11: Case C-2: Example Service Aggregation/Disaggregation | Figure 11: Case C-2: Example Service Aggregation/Disaggregation | |||
Figure 12 contains the operational JSON configuration for the ingress | Figure 12 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 11. In this example, a relay | aggregation node illustrated in Figure 11. In this example, a relay | |||
performing aggregation at the forwarding sub-layer is illustrated. | performing aggregation at the forwarding sub-layer is illustrated. | |||
Two DetNet flows -- DN-1 and DN-2 -- are replicated at each service | Two DetNet flows -- DN-1 and DN-2 -- are replicated at each service | |||
sub-layer. Each replicated flow for the service sub-layer for the | sub-layer. Each replicated flow for the service sub-layer for the | |||
upper path is aggregated at the single forwarding sub-layer with MPLS | upper path is aggregated at the single forwarding sub-layer with MPLS | |||
label 20000, and each replicated flow for the service sub-layer for | label 20000, and each replicated flow for the service sub-layer for | |||
skipping to change at line 4763 ¶ | skipping to change at line 4769 ¶ | |||
Figure 14 illustrates the DetNet relay node's service sub-layer flows | Figure 14 illustrates the DetNet relay node's service sub-layer flows | |||
1 and 2 aggregated into a service sub-layer flow. Multiple DetNet | 1 and 2 aggregated into a service sub-layer flow. Multiple DetNet | |||
flows with the same requirements that can use the same path are | flows with the same requirements that can use the same path are | |||
aggregated into a single aggregated DetNet flow, and service | aggregated into a single aggregated DetNet flow, and service | |||
protection and resource allocation are performed by the service sub- | protection and resource allocation are performed by the service sub- | |||
layer and forwarding sub-layer of the aggregated DetNet flow. | layer and forwarding sub-layer of the aggregated DetNet flow. | |||
Figure 14 illustrates both aggregation and disaggregation, and the | Figure 14 illustrates both aggregation and disaggregation, and the | |||
corresponding JSON operational data follows. | corresponding JSON operational data follows. | |||
Please consult the PDF or HTML copy for the Case C-3 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 14: Case C-3: Example Service Aggregation/Disaggregation | Figure 14: Case C-3: Example Service Aggregation/Disaggregation | |||
Figure 15 contains the operational JSON configuration for the ingress | Figure 15 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 14. In this example, a relay | aggregation node illustrated in Figure 14. In this example, a relay | |||
performing aggregation at the service sub-layer is illustrated. Two | performing aggregation at the service sub-layer is illustrated. Two | |||
DetNet flows -- DN-1 and DN-2 -- are relayed at each service sub- | DetNet flows -- DN-1 and DN-2 -- are relayed at each service sub- | |||
layer with MPLS labels 101 and 104, respectively, and each service | layer with MPLS labels 101 and 104, respectively, and each service | |||
sub-layer is aggregated at a single service sub-layer flow and | sub-layer is aggregated at a single service sub-layer flow and | |||
replicated. Figure 16 contains the operational JSON configuration | replicated. Figure 16 contains the operational JSON configuration | |||
skipping to change at line 5428 ¶ | skipping to change at line 5435 ¶ | |||
Figure 17 illustrates the DetNet relay node's forwarding sub-layer | Figure 17 illustrates the DetNet relay node's forwarding sub-layer | |||
flows 1 and 2 aggregated into a service sub-layer DetNet flow. | flows 1 and 2 aggregated into a service sub-layer DetNet flow. | |||
Multiple DetNet flows with the same requirements that can use the | Multiple DetNet flows with the same requirements that can use the | |||
same path are aggregated into a single aggregated DetNet flow. | same path are aggregated into a single aggregated DetNet flow. | |||
Service protection is performed by the service sub-layer of the | Service protection is performed by the service sub-layer of the | |||
aggregated DetNet flow, and resource allocation is performed by the | aggregated DetNet flow, and resource allocation is performed by the | |||
forwarding sub-layer of each aggregated DetNet flow. Figure 17 | forwarding sub-layer of each aggregated DetNet flow. Figure 17 | |||
illustrates both aggregation and disaggregation, and the | illustrates both aggregation and disaggregation, and the | |||
corresponding JSON operational data follows. | corresponding JSON operational data follows. | |||
Please consult the PDF or HTML copy for the Case C-4 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 17: Case C-4: Example Service Aggregation/Disaggregation | Figure 17: Case C-4: Example Service Aggregation/Disaggregation | |||
Figure 18 contains the operational JSON configuration for the ingress | Figure 18 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 17. In this example, a relay | aggregation node illustrated in Figure 17. In this example, a relay | |||
performing aggregation at the service sub-layer is illustrated. Two | performing aggregation at the service sub-layer is illustrated. Two | |||
DetNet flows -- DN-1 and DN-2 -- are relayed at each service sub- | DetNet flows -- DN-1 and DN-2 -- are relayed at each service sub- | |||
layer. The two DetNet forwarding sub-layer flows with MPLS labels | layer. The two DetNet forwarding sub-layer flows with MPLS labels | |||
20004 and 20005 are aggregated at the single service sub-layer DetNet | 20004 and 20005 are aggregated at the single service sub-layer DetNet | |||
flow and then replicated. Figure 19 contains the operational JSON | flow and then replicated. Figure 19 contains the operational JSON | |||
skipping to change at line 6209 ¶ | skipping to change at line 6217 ¶ | |||
B.8. Example D-1: Transit Node Forwarding Sub-layer Aggregation/ | B.8. Example D-1: Transit Node Forwarding Sub-layer Aggregation/ | |||
Disaggregation | Disaggregation | |||
As illustrated in Figure 20, at the transit node, forwarding sub- | As illustrated in Figure 20, at the transit node, forwarding sub- | |||
layer flows 1 and 2 are aggregated into a single forwarding sub- | layer flows 1 and 2 are aggregated into a single forwarding sub- | |||
layer. Resource allocation is performed by the corresponding | layer. Resource allocation is performed by the corresponding | |||
forwarding sub-layer for all aggregated flows. Figure 20 illustrates | forwarding sub-layer for all aggregated flows. Figure 20 illustrates | |||
both aggregation and disaggregation, and the corresponding JSON | both aggregation and disaggregation, and the corresponding JSON | |||
operational data follows. | operational data follows. | |||
Please consult the PDF or HTML copy for the Case D-1 diagram. | (Artwork only available as svg: see | |||
https://www.rfc-editor.org/rfc/rfc9633.html) | ||||
Figure 20: Case D-1: Example Transit Node Forwarding Aggregation/ | Figure 20: Case D-1: Example Transit Node Forwarding Aggregation/ | |||
Disaggregation | Disaggregation | |||
Figure 21 contains the operational JSON configuration for the ingress | Figure 21 contains the operational JSON configuration for the ingress | |||
aggregation node illustrated in Figure 20. In this example, a | aggregation node illustrated in Figure 20. In this example, a | |||
transit node performing aggregation at the forwarding sub-layer is | transit node performing aggregation at the forwarding sub-layer is | |||
illustrated. Two DetNet flows -- DN-1 and DN-2 -- are transmitted at | illustrated. Two DetNet flows -- DN-1 and DN-2 -- are transmitted at | |||
each forwarding sub-layer. The DetNet forwarding sub-layer flows | each forwarding sub-layer. The DetNet forwarding sub-layer flows | |||
with MPLS labels 10002 and 10006 are aggregated at the single | with MPLS labels 10002 and 10006 are aggregated at the single | |||
End of changes. 9 change blocks. | ||||
9 lines changed or deleted | 18 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |