Hello J. Haas and S. Hares,
I have some doubt about "draft-ietf-i2rs-ephemeral-state-00".
1.Chapter 6 Requirements regarding Identity, Secondary-Identity and
Priority
I2RS permits RPC operation to carry priority and a secondary identity as
attribute parameters.
In this draft, it describes that "This secondary identity meta-data MUST
be read-only. operations attempting to alter it MUST be silently ignored.
"
Since identity attribute cannot be changed until the session terminates,
why don't we permit client to send hello message with such infos during
session establishment.
e.g,
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>
urn:ietf:params:netconf:base:1.0
</capability>
<capability>
urn:ietf:params:i2rs:capability:i2rs:1.0?secondary-identity=user1&priority=10
</capability>
</capabilities>
</hello>
It means in this session, the secondary-identity is named "user1", the
default priority is 10
then,if the session wants to change its priority while RPC operation,as
follows
<foo xmlns:i2rs="https://ietf.example.com/i2rs";
i2rs:i2rs-priority="47">
...
</foo>
It means now in this session, the secondary-identity is named "user1", the
priority is 47
furthermore, we can define <set-i2rs-priority> to change current session's
priority,such as
<set-i2rs-priority
xmlns:i2rs="urn:ietf:params:i2rs:capability:i2rs:1.0">
<priority>20</priority>
</set-i2rs-priority>
2.In this draft, Priority is defined as a numeric value,how about its
range statements? Is "i2rs-priority = 255" is the highest?
3.config ephemeral
In this draft,The YANG "config" keyword is extended,like "config
true/false/ephemeral" ,and the basic netconf operation should be extended,
like "get-config" "edit-config" and so on.
why don't we define a new kind of operations,like "get-i2rs" "edit-i2rs"?
Take definition of "get-i2rs" for example.
rpc get-i2rs {
description "This operation can be used to get data from i2rs
data";
input {
leaf private {
description "If the value is true, it means only
data owned by
the same identity will be
retrieved. Otherwise, all i2rs
data will be returned.";
type boolean;
default false;
}
anyxml filter {
description
"Subtree filter to use.";
}
}
output {
anyxml data {
description
"Copy of the i2rs data that matched
the filter criteria (if any). An empty data
container
indicates that the request did not produce any
results.";
}
}
}
If it is feasible, i can define others.
[email protected]
发件人: "i2rs" <[email protected]>
2015/06/24 00:52
收件人
<[email protected]>,
抄送
[email protected]
主题
[i2rs] I-D Action: draft-ietf-i2rs-ephemeral-state-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Interface to the Routing System Working
Group of the IETF.
Title : I2RS Ephemeral State Requirements
Authors : Jeff Haas
Susan Hares
Filename : draft-ietf-i2rs-ephemeral-state-00.txt
Pages : 13
Date : 2015-06-23
Abstract:
This document covers requests to the netmod and netconf Working
Groups for functionality to support the ephemeral state requirements
to implement the I2RS architecture.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/
There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-i2rs-ephemeral-state-00
Please note that it may take a couple of minutes from the time of
submission
until the htmlized version and diff are available at tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and
any attachment transmitted herewith) is privileged and confidential and is
intended for the exclusive use of the addressee(s). If you are not an intended
recipient, any disclosure, reproduction, distribution or other dissemination or
use of the information contained is strictly prohibited. If you have received
this mail in error, please delete it and notify us immediately.
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and
any attachment transmitted herewith) is privileged and confidential and is
intended for the exclusive use of the addressee(s). If you are not an intended
recipient, any disclosure, reproduction, distribution or other dissemination or
use of the information contained is strictly prohibited. If you have received
this mail in error, please delete it and notify us immediately.
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
