draft-ietf-ccamp-transport-nbi-app-statement-10.txt   draft-ietf-ccamp-transport-nbi-app-statement-11.txt 
CCAMP Working Group I. Busi CCAMP Working Group I. Busi
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational D. King Intended status: Informational D. King
Old Dog Consulting Old Dog Consulting
H. Zheng H. Zheng
Huawei Huawei
Y. Xu Y. Xu
CAICT CAICT
Expires: May 2020 November 19, 2019 Expires: January 8, 2021 July 7, 2020
Transport Northbound Interface Applicability Statement Transport Northbound Interface Applicability Statement
draft-ietf-ccamp-transport-nbi-app-statement-10 draft-ietf-ccamp-transport-nbi-app-statement-11
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 19, 2020. This Internet-Draft will expire on January 8, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 55, line 12 skipping to change at page 55, line 12
[RFC8341] Bierman, A., Bjorklund, M., "Network Configuration Access [RFC8341] Bierman, A., Bjorklund, M., "Network Configuration Access
Control Model", RFC 8341, March 2018. Control Model", RFC 8341, March 2018.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, August 2018. Version 1.3", RFC 8446, August 2018.
[ACTN-YANG] Zhang, X. et al., "Applicability of YANG models for [ACTN-YANG] Zhang, X. et al., "Applicability of YANG models for
Abstraction and Control of Traffic Engineered Networks", Abstraction and Control of Traffic Engineered Networks",
draft-zhang-teas-actn-yang, work in progress. draft-zhang-teas-actn-yang, work in progress.
[RFC-FOLD] Watsen, K. et al., "Handling Long Lines in Artwork in [RFC8792] Watsen, K. et al., "Handling Long Lines in Artwork in
Internet-Drafts and RFCs", draft-ietf-netmod-artwork- Internet-Drafts and RFCs", RFC8792, 10.17487/8792,
folding, work in progress June 2020, <https://www.rfc-editor.org/info/rfc8792>.
[TE-TUTORIAL] Bryskin, I. et al., "TE Topology and Tunnel Modeling [TE-TUTORIAL] Bryskin, I. et al., "TE Topology and Tunnel Modeling
for Transport Networks", draft-ietf-teas-te-topo-and- for Transport Networks", draft-ietf-teas-te-topo-and-
tunnel-modeling, work in progress tunnel-modeling, work in progress
[ONF TR-527] ONF Technical Recommendation TR-527, "Functional [ONF TR-527] ONF Technical Recommendation TR-527, "Functional
Requirements for Transport API", June 2016. Requirements for Transport API", June 2016.
[MEF 55] Metro Ethernet Forum, "Lifecycle Service Orchestration [MEF 55] Metro Ethernet Forum, "Lifecycle Service Orchestration
(LSO): Reference Architecture and Framework", Technical (LSO): Reference Architecture and Framework", Technical
skipping to change at page 57, line 22 skipping to change at page 57, line 22
This section describes the various ways JSON fragments are used in This section describes the various ways JSON fragments are used in
the I-D processing and how to manage them. the I-D processing and how to manage them.
Let's call "folded-JSON" the JSON embedded in the I-D: it fits the Let's call "folded-JSON" the JSON embedded in the I-D: it fits the
72 chars width and it is acceptable for it to be invalid JSON. 72 chars width and it is acceptable for it to be invalid JSON.
We then define "unfolded-JSON" a valid JSON fragment having the same We then define "unfolded-JSON" a valid JSON fragment having the same
contents of the "folded-JSON " without folding, i.e. limits on the contents of the "folded-JSON " without folding, i.e. limits on the
text width. The folding/unfolding operation may be done according to text width. The folding/unfolding operation may be done according to
[RFC-FOLD]. The "unfolded-JSON" can be edited by the authors using [RFC8792]. The "unfolded-JSON" can be edited by the authors using
JSON editors with the advantages of syntax validation and pretty- JSON editors with the advantages of syntax validation and pretty-
printing. printing.
Both the "folded" and the "unfolded" JSON fragments can include Both the "folded" and the "unfolded" JSON fragments can include
comments having descriptive fields and directives we'll describe comments having descriptive fields and directives we'll describe
later to facilitate the reader and enable some automatic processing. later to facilitate the reader and enable some automatic processing.
The presence of comments in the "unfolded-JSON" fragment makes it an The presence of comments in the "unfolded-JSON" fragment makes it an
invalid JSON encoding of YANG data. Therefore we call "naked JSON" invalid JSON encoding of YANG data. Therefore we call "naked JSON"
the JSON where the comments have been stripped out: not only it is the JSON where the comments have been stripped out: not only it is
 End of changes. 6 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/