Internet DRAFT - draft-liu-opsawg-ipfix-network-slice
draft-liu-opsawg-ipfix-network-slice
OPSAWG Working Group Y. Liu
Internet-Draft ZTE
Intended status: Standards Track 28 June 2023
Expires: 30 December 2023
Export of Network Resource Partition (NRP) Information in IP Flow
Information Export (IPFIX)
draft-liu-opsawg-ipfix-network-slice-00
Abstract
This document introduces new IP Flow Information Export (IPFIX)
Information Elements to identify the Network Resource Partition (NRP)
that the network slice traffic is related with.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 30 December 2023.
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Liu Expires 30 December 2023 [Page 1]
Internet-Draft IPFIX NRP June 2023
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. New IPFIX Information Element . . . . . . . . . . . . . . . . 3
4. Usecases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The definition of the IETF Network Slice and the general principles
of network slicing in the IETF context are specified in
[I-D.ietf-teas-ietf-network-slices]. As described in
[I-D.ietf-teas-ietf-network-slices], an IETF Network Slice enables
connectivity between a set of Service Demarcation Points (SDPs) with
specific Service Level Objectives (SLOs) and Service Level
Expectations (SLEs) over a common underlay network. To meet the
connectivity and performance requirements, network slice services
needs to be mapped to a Network Resource Partition (NRP). An NRP is
a collection of resources (bufferage, queuing, scheduling, etc.) in
the underlay network.
As introduced in [I-D.ietf-teas-ns-ip-mpls], each NRP can be
idenified using a unique NRP-ID in control plane and management
plane. And the NRP-ID may also be encapsulated in data packet to
guide the NRP-specific packet forwarding.
This document defines new IPFIX Information Elements within the
"IPFIX Information Elements" registry [RFC7012] to identify the
Network Resource Partition (NRP) that the network slice traffic is
related with.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here.
Liu Expires 30 December 2023 [Page 2]
Internet-Draft IPFIX NRP June 2023
3. New IPFIX Information Element
This section defines and describes the new IPFIX IE.
* Name: nrpIdentifier
* ElementID: TBD1
* Description: The NRP ID as defined in [I-D.ietf-teas-ns-ip-mpls].
* Abstract Data Type: unsigned32
* Data Type Semantics: identifier
4. Usecases
A typical usecase scenario is to monitoring the network slice traffic
that is forwarded based on NRP specific resource-aware segments
[I-D.ietf-spring-resource-aware-segments] that operate over SR-MPLS
or SRv6 dataplanes. By looking at the SID itself, it is not always
clear as to which NRP it belongs.
Another usecase is the monitoring of the network slice traffic whose
NRP-ID is encapsulated in data packet to determine the Network
Resource Partition Per Hop Behavior.
By using nrpIdentifier(TBD1), and some counters information, it is
possible to answer the following questions (amongst others):
* How many packets are forwarded or dropped?
* If dropped, for which reasons?
* Which NRP is the traffic related with?
5. IANA Considerations
This document requests IANA to add a new IE to the "IPFIX Information
Elements" registry [RFC7012] available at [IANA-IPFIX].
-----------------------------------------------------
| ElementID| Name | Reference |
|---------------------------------------------------|
| TBD1 | NRP-ID | This document |
|---------------------------------------------------|
Liu Expires 30 December 2023 [Page 3]
Internet-Draft IPFIX NRP June 2023
6. Security Considerations
There exists no significant extra security considerations regarding
the allocation of these new IPFIX IEs compared to [RFC7012].
7. References
7.1. Normative References
[I-D.ietf-teas-ns-ip-mpls]
Saad, T., Beeram, V. P., Dong, J., Wen, B., Ceccarelli,
D., Halpern, J. M., Peng, S., Chen, R., Liu, X.,
Contreras, L. M., Rokui, R., and L. Jalil, "Realizing
Network Slices in IP/MPLS Networks", Work in Progress,
Internet-Draft, draft-ietf-teas-ns-ip-mpls-02, 13 March
2023, <https://datatracker.ietf.org/doc/html/draft-ietf-
teas-ns-ip-mpls-02>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013,
<https://www.rfc-editor.org/info/rfc7012>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References
[I-D.ietf-spring-resource-aware-segments]
Dong, J., Bryant, S., Miyasaka, T., Zhu, Y., Qin, F., Li,
Z., and F. Clad, "Introducing Resource Awareness to SR
Segments", Work in Progress, Internet-Draft, draft-ietf-
spring-resource-aware-segments-07, 31 May 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-spring-
resource-aware-segments-07>.
Liu Expires 30 December 2023 [Page 4]
Internet-Draft IPFIX NRP June 2023
[I-D.ietf-teas-ietf-network-slices]
Farrel, A., Drake, J., Rokui, R., Homma, S., Makhijani,
K., Contreras, L. M., and J. Tantsura, "A Framework for
IETF Network Slices", Work in Progress, Internet-Draft,
draft-ietf-teas-ietf-network-slices-21, 15 June 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-teas-
ietf-network-slices-21>.
[IANA-IPFIX]
"IANA, "IP Flow Information Export (IPFIX) Entities"",
<https://www.iana.org/assignments/ipfix/ipfix.xhtml>.
Author's Address
Yao Liu
ZTE
Nanjing
China
Email: liu.yao71@zte.com.cn
Liu Expires 30 December 2023 [Page 5]
