Skip to content

Commit

Permalink
Script updating gh-pages from 08faa22. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jun 29, 2024
1 parent 003223b commit 0ba3882
Show file tree
Hide file tree
Showing 2 changed files with 40 additions and 45 deletions.
42 changes: 20 additions & 22 deletions draft-ietf-netmod-immutable-flag.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1041,7 +1041,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Ma, et al.</td>
<td class="center">Expires 26 December 2024</td>
<td class="center">Expires 31 December 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1057,12 +1057,12 @@
<a href="https://www.rfc-editor.org/rfc/rfc6241" class="eref">6241</a>, <a href="https://www.rfc-editor.org/rfc/rfc8040" class="eref">8040</a>, <a href="https://www.rfc-editor.org/rfc/rfc8526" class="eref">8526</a> (if approved)</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-06-24" class="published">24 June 2024</time>
<time datetime="2024-06-29" class="published">29 June 2024</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Standards Track</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2024-12-26">26 December 2024</time></dd>
<dd class="expires"><time datetime="2024-12-31">31 December 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1129,7 +1129,7 @@ <h2 id="name-status-of-this-memo">
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 26 December 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 31 December 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1402,13 +1402,13 @@ <h2 id="name-conventions-and-definitions">
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
described in BCP 14 <span>[<a href="#RFC2119" class="cite xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="cite xref">RFC8174</a>]</span> when, and only when, they
appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow"></a></p>
<p id="section-2-2">The following terms are defined in <span>[<a href="#RFC6241" class="cite xref">RFC6241</a>]</span>:<a href="#section-2-2" class="pilcrow"></a></p>
<p id="section-2-2">The document uses the following definition in <span>[<a href="#RFC6241" class="cite xref">RFC6241</a>]</span>:<a href="#section-2-2" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-2-3.1">
<p id="section-2-3.1.1">configuration data<a href="#section-2-3.1.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-2-4">The following terms are defined in <span>[<a href="#RFC7950" class="cite xref">RFC7950</a>]</span>:<a href="#section-2-4" class="pilcrow"></a></p>
<p id="section-2-4">The document uses the following definition in <span>[<a href="#RFC7950" class="cite xref">RFC7950</a>]</span>:<a href="#section-2-4" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-2-5.1">
<p id="section-2-5.1.1">data node<a href="#section-2-5.1.1" class="pilcrow"></a></p>
Expand Down Expand Up @@ -1438,13 +1438,10 @@ <h2 id="name-conventions-and-definitions">
<p id="section-2-5.9.1">data tree<a href="#section-2-5.9.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-2-6">The following terms are defined in <span>[<a href="#RFC8341" class="cite xref">RFC8341</a>]</span>:<a href="#section-2-6" class="pilcrow"></a></p>
<p id="section-2-6">The document uses the following definition in <span>[<a href="#RFC8341" class="cite xref">RFC8341</a>]</span>:<a href="#section-2-6" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-2-7.1">
<p id="section-2-7.1.1">access operation<a href="#section-2-7.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-2-7.2">
<p id="section-2-7.2.1">write access<a href="#section-2-7.2.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-2-8">This document defines the following term:<a href="#section-2-8" class="pilcrow"></a></p>
Expand Down Expand Up @@ -1496,11 +1493,11 @@ <h3 id="name-definition">
same as the immutability of its parent node in the data tree (<a href="#interior" class="auto internal xref">Section 6</a>).
The immutable metadata annotation value for a top-level instance
node is "false" if not specified.<a href="#section-4.1-1" class="pilcrow"></a></p>
<p id="section-4.1-2">Note that "immutable" metadata annotation is used to annotate data node
<p id="section-4.1-2">Note that "immutable" metadata annotations are used to annotate data node
instances. A list may have multiple instances in the data tree,
servers can annotate some of the instances as immutable, while others as
servers may annotate some of the instances as immutable, while others as
mutable.<a href="#section-4.1-2" class="pilcrow"></a></p>
<p id="section-4.1-3">Servers <span class="bcp14">MUST</span> ignore any immutable metadata annotation sent from the client.<a href="#section-4.1-3" class="pilcrow"></a></p>
<p id="section-4.1-3">Servers <span class="bcp14">MUST</span> ignore any immutable annotations sent from the client.<a href="#section-4.1-3" class="pilcrow"></a></p>
</section>
</div>
<div id="with-immutable">
Expand Down Expand Up @@ -1549,7 +1546,7 @@ <h4 id="name-netconf-extensions-to-suppo">
<h4 id="name-restconf-extensions-to-supp">
<a href="#section-4.2.2" class="section-number selfRef">4.2.2. </a><a href="#name-restconf-extensions-to-supp" class="section-name selfRef">RESTCONF Extensions to Support "with-immutable"</a>
</h4>
<p id="section-4.2.2-1">This document extends Sections <a href="https://rfc-editor.org/rfc/rfc8040#section-4.8" class="relref">4.8</a> and <a href="https://rfc-editor.org/rfc/rfc8040#section-9.1.1" class="relref">9.1.1</a> of <span>[<a href="#RFC8040" class="cite xref">RFC8040</a>]</span> to add query
<p id="section-4.2.2-1">This document extends Sections <a href="https://rfc-editor.org/rfc/rfc8040#section-4.8" class="relref">4.8</a> and <a href="https://rfc-editor.org/rfc/rfc8040#section-9.1.1" class="relref">9.1.1</a> of <span>[<a href="#RFC8040" class="cite xref">RFC8040</a>]</span> to add a query
parameter named "with-immutable" to the GET operation. If present, this parameter
requests that the server includes the "immutable" metadata annotations in its
response. This parameter is only allowed with no values carried. If it has
Expand Down Expand Up @@ -1654,13 +1651,14 @@ <h2 id="name-immutability-of-interior-no">
recursively applied to descendants, which may reset the immutability
state as needed, thereby affecting their descendants. There is no limit
to the number of times the immutability state may change in a data tree.<a href="#section-6-1" class="pilcrow"></a></p>
<p id="section-6-2">If the "immutable" metadata annotation for returned child nodes are omitted,
<p id="section-6-2">If the "immutable" metadata annotation for returned child node is omitted,
it has the same immutability as its parent node. The immutability of top
hierarchy of returned nodes is false by default. Servers may suppress the
annotation if it is inherited from its parent node or uses the default value
as the top-level node, but are not precluded from returning the annotation
on every single element.<a href="#section-6-2" class="pilcrow"></a></p>
<p id="section-6-3">For example, given the following application configuration XML snippets:<a href="#section-6-3" class="pilcrow"></a></p>
<p id="section-6-3">For example, the following XML snippets shows applications configuration a
server might return:<a href="#section-6-3" class="pilcrow"></a></p>
<div class="alignLeft art-text artwork" id="section-6-4">
<pre>
&lt;applications im:immutable="false"&gt;
Expand All @@ -1677,15 +1675,15 @@ <h2 id="name-immutability-of-interior-no">
&lt;/applications&gt;
</pre><a href="#section-6-4" class="pilcrow"></a>
</div>
<p id="section-6-5">In this example, there are two "application" list entries inside "applications"
<p id="section-6-5">In the example, there are two "application" list entries inside "applications"
container node. The "immutable" metadata attribute for applications container
instance is "false", which is also its default value as the top-level element,
and thus can be omitted. The "application" list entry named "ssh" is immutable
with the immutability of its child node "port-number" being explicitly toggled.
The other child nodes inheriting immutability from their parent node thus are
also immutable. The "immutable" metadata attribute for application list entry
named "my-ssh" is "false", which is also its inherited value from its parent
node, and thus can be omitted.<a href="#section-6-5" class="pilcrow"></a></p>
The other child nodes inside "ssh" application instance inherit immutability
from their parent node thus are also immutable. The "immutable" metadata attribute
for application list entry named "my-ssh" is "false", which is also the same
value as its parent node, and thus can be omitted.<a href="#section-6-5" class="pilcrow"></a></p>
</section>
</div>
<div id="system-configuration-datastore-interactions">
Expand All @@ -1694,7 +1692,7 @@ <h2 id="name-system-configuration-datast">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-system-configuration-datast" class="section-name selfRef">System Configuration Datastore Interactions</a>
</h2>
<p id="section-7-1">Immutable configuration can only be created, updated and deleted by the server,
thus it is present in &lt;system&gt;, if implemented. That said, the existence of
and it is present in &lt;system&gt;, if implemented. That said, the existence of
immutable configuration is independent of whether &lt;system&gt; is implemented or
not. Not all system configuration data is immutable. Immutable configuration
does not appear in &lt;running&gt; unless it is explicitly provided by the client
Expand Down
43 changes: 20 additions & 23 deletions draft-ietf-netmod-immutable-flag.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ netmod Q. Ma, Ed.
Internet-Draft Q. Wu
Updates: 6241, 8040, 8526 (if approved) Huawei
Intended status: Standards Track B. Lengyel, Ed.
Expires: 26 December 2024 Ericsson
Expires: 31 December 2024 Ericsson
H. Li
HPE
24 June 2024
29 June 2024


YANG Metadata Annotation for Immutable Flag
Expand Down Expand Up @@ -55,7 +55,7 @@ Status of This Memo
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 26 December 2024.
This Internet-Draft will expire on 31 December 2024.

Copyright Notice

Expand Down Expand Up @@ -205,11 +205,11 @@ Table of Contents
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.

The following terms are defined in [RFC6241]:
The document uses the following definition in [RFC6241]:

* configuration data

The following terms are defined in [RFC7950]:
The document uses the following definition in [RFC7950]:

* data node

Expand All @@ -229,12 +229,10 @@ Table of Contents

* data tree

The following terms are defined in [RFC8341]:
The document uses the following definition in [RFC8341]:

* access operation

* write access

This document defines the following term:

immutable flag: A read-only state value the server provides to
Expand Down Expand Up @@ -271,13 +269,12 @@ Table of Contents
in the data tree (Section 6). The immutable metadata annotation
value for a top-level instance node is "false" if not specified.

Note that "immutable" metadata annotation is used to annotate data
Note that "immutable" metadata annotations are used to annotate data
node instances. A list may have multiple instances in the data tree,
servers can annotate some of the instances as immutable, while others
servers may annotate some of the instances as immutable, while others
as mutable.

Servers MUST ignore any immutable metadata annotation sent from the
client.
Servers MUST ignore any immutable annotations sent from the client.

4.2. "with-immutable" Parameter

Expand Down Expand Up @@ -314,7 +311,7 @@ Table of Contents

4.2.2. RESTCONF Extensions to Support "with-immutable"

This document extends Sections 4.8 and 9.1.1 of [RFC8040] to add
This document extends Sections 4.8 and 9.1.1 of [RFC8040] to add a
query parameter named "with-immutable" to the GET operation. If
present, this parameter requests that the server includes the
"immutable" metadata annotations in its response. This parameter is
Expand Down Expand Up @@ -392,15 +389,15 @@ Table of Contents
limit to the number of times the immutability state may change in a
data tree.

If the "immutable" metadata annotation for returned child nodes are
If the "immutable" metadata annotation for returned child node is
omitted, it has the same immutability as its parent node. The
immutability of top hierarchy of returned nodes is false by default.
Servers may suppress the annotation if it is inherited from its
parent node or uses the default value as the top-level node, but are
not precluded from returning the annotation on every single element.

For example, given the following application configuration XML
snippets:
For example, the following XML snippets shows applications
configuration a server might return:

<applications im:immutable="false">
<application im:immutable="true">
Expand All @@ -415,22 +412,22 @@ Table of Contents
</application>
</applications>

In this example, there are two "application" list entries inside
In the example, there are two "application" list entries inside
"applications" container node. The "immutable" metadata attribute
for applications container instance is "false", which is also its
default value as the top-level element, and thus can be omitted. The
"application" list entry named "ssh" is immutable with the
immutability of its child node "port-number" being explicitly
toggled. The other child nodes inheriting immutability from their
parent node thus are also immutable. The "immutable" metadata
attribute for application list entry named "my-ssh" is "false", which
is also its inherited value from its parent node, and thus can be
omitted.
toggled. The other child nodes inside "ssh" application instance
inherit immutability from their parent node thus are also immutable.
The "immutable" metadata attribute for application list entry named
"my-ssh" is "false", which is also the same value as its parent node,
and thus can be omitted.

7. System Configuration Datastore Interactions

Immutable configuration can only be created, updated and deleted by
the server, thus it is present in <system>, if implemented. That
the server, and it is present in <system>, if implemented. That
said, the existence of immutable configuration is independent of
whether <system> is implemented or not. Not all system configuration
data is immutable. Immutable configuration does not appear in
Expand Down

0 comments on commit 0ba3882

Please sign in to comment.