1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
.. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
.. Licensed under the Creative Commons License, Attribution 4.0 Intl.
(the "License"); you may not use this documentation except in compliance
with the License. You may obtain a copy of the License at
.. https://creativecommons.org/licenses/by/4.0/
.. Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Scope
=====
- The audience for this document are xNF providers, NCSPs and other
interested 3rd parties who need to know the design, build and lifecycle
management requirements for xNFs to be compliant with ONAP.
- These requirements are strictly from a standpoint of what the xNF
developer needs to know to operate and be compliant with ONAP.
- Requirements that are not applicable to xNF providers such as those
that applicable to service providers are not included in this document.
- These requirements are applicable to the current release of ONAP.
- Scope of the ONAP versions/release and future functionality
- The VNF Requirements should include support for the functionality of the
ONAP E-E use cases.
- These requirements apply to xNFs at both ONAP Design-Time and ONAP Run-Time.
- Network Service Descriptions are beyond the scope of these requirements.
References
-----------------------
This section contains a list of normative and informative references along
with information on acquiring the identified references. Normative references
are required to be implemented by this document. Informative references are
for informational purposes only.
Normative References
^^^^^^^^^^^^^^^^^^^^^^^
+---------------+-----------------------------------------------------+
| Reference | Description |
+===============+=====================================================+
| [RFC 2119] | IETF RFC2119, Key words for use in RFCs to Indicate |
| | Requirement Levels, S. Bradner, March 1997. |
+---------------+-----------------------------------------------------+
Informative References
^^^^^^^^^^^^^^^^^^^^^^^^
+---------------+-----------------------------------------------------+
| Reference | Description |
+===============+=====================================================+
| | |
+---------------+-----------------------------------------------------+
Reference Acquisition
^^^^^^^^^^^^^^^^^^^^^^^
IETF Specifications:
- Internet Engineering Task Force (IETF) Secretariat, 48377 Fremont Blvd.,
Suite 117, Fremont, California 94538, USA; Phone: +1-510-492-4080,
Fax: +1-510-492-4001.
Submitting Feedback
------------------------------------
To report issues on this document, please perform one of the following steps:
1. Log a JIRA defect against the document within the VNF Requirements
(VNFRQTS) project at https://jira.onap.org/projects/VNFRQTS.
Note: This will require a Linux Foundation ID to login to JIRA.
2. Send an email to onap-discuss@lists.onap.org with subject line
starting with the tag [vnfrqts]. Note: This will require subscribing
to the onap-discuss email discussion list. Refer to the following
instructions to subscribe to the mail list:
https://wiki.onap.org/display/DW/Mailing+Lists
|
