rfc9613v2.txt | rfc9613.txt | |||
---|---|---|---|---|
skipping to change at line 127 ¶ | skipping to change at line 127 ¶ | |||
or as a consequence of an MPLS packet being processed by a router. | or as a consequence of an MPLS packet being processed by a router. | |||
A network action may affect router state or MPLS packet | A network action may affect router state or MPLS packet | |||
forwarding, or it may affect the MPLS packet in some other way. | forwarding, or it may affect the MPLS packet in some other way. | |||
Network Action Indicator (NAI): An indication in the MPLS packet | Network Action Indicator (NAI): An indication in the MPLS packet | |||
that a certain network action is to be performed. | that a certain network action is to be performed. | |||
Ancillary Data (AD): Data in an MPLS packet associated with a given | Ancillary Data (AD): Data in an MPLS packet associated with a given | |||
network action that may be used as input to process the network | network action that may be used as input to process the network | |||
action or may result from processing the network action. | action or may result from processing the network action. | |||
Ancillary data may be associated with: | ||||
* Both the control or maintenance information and the data | * Both the control or maintenance information and the data | |||
traffic carried by the Label Switched Path (LSP). | traffic carried by the Label Switched Path (LSP). | |||
* Only the control or maintenance information. | * Only the control or maintenance information. | |||
* Only the data traffic carried by the LSP. | * Only the data traffic carried by the LSP. | |||
In-Stack Data: Ancillary data carried within the MPLS label stack. | In-Stack Data: Ancillary data carried within the MPLS label stack. | |||
skipping to change at line 188 ¶ | skipping to change at line 189 ¶ | |||
1. Any solutions MUST maintain the properties of extensibility, | 1. Any solutions MUST maintain the properties of extensibility, | |||
flexibility, and efficiency inherent in the split between the | flexibility, and efficiency inherent in the split between the | |||
control plane context and simple data plane used in MPLS and | control plane context and simple data plane used in MPLS and | |||
SHOULD describe how this is achieved. | SHOULD describe how this is achieved. | |||
2. Any solutions to these requirements MUST be based on and MUST | 2. Any solutions to these requirements MUST be based on and MUST | |||
NOT restrict the generality of the MPLS architecture [RFC3031] | NOT restrict the generality of the MPLS architecture [RFC3031] | |||
[RFC3032] [RFC5331]. | [RFC3032] [RFC5331]. | |||
3. If extensions to the MPLS data plane are required, they MUST NOT | 3. If extensions to the MPLS data plane are required, they MUST be | |||
be inconsistent with the MPLS architecture [RFC3031], [RFC3032] | consistent with the MPLS architecture [RFC3031] [RFC3032] | |||
and [RFC5331]. | [RFC5331]. | |||
4. Solutions meeting the requirements set out in this document MUST | 4. Solutions meeting the requirements set out in this document MUST | |||
be able to coexist with existing MPLS mechanisms. | be able to coexist with existing MPLS mechanisms. | |||
5. Subject to the constraints in these requirements, a Network | 5. Subject to the constraints in these requirements, a Network | |||
Action solution MAY carry MNA information in-stack, post-stack, | Action solution MAY carry MNA information in-stack, post-stack, | |||
or both in-stack and post-stack. | or both in-stack and post-stack. | |||
6. Solutions MUST NOT require an implementation to support in-stack | 6. Solutions MUST NOT require an implementation to support in-stack | |||
ancillary data, unless the implementation chooses to support a | ancillary data, unless the implementation chooses to support a | |||
End of changes. 2 change blocks. | ||||
3 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |