On Mon, Feb 02, 2015 at 06:53:16PM -0500, Susan Hares wrote:
> This begins a 2 week WG Adoption call for:
> draft-voit-i2rs-pub-sub-requirements-00 (2/2 to 2/16/2015). You can access
> the draft at:
>
> http://www.ietf.org/id/draft-voit-i2rs-pub-sub-requirements-00.txt
>
I like to point out that some statements in the draft are either
unclear or wrong.
o limited support for pushed notification of changes. (Currently
notifications are for configuration data only. And even then,
subscription mechanisms for such notifications are undefined.)
RFC 5277 defines a <create-subscription> mechanism. RFC 6470 defines
notifications that allow to track changes in a configuration
datastore. So why is the subscription mechanisms undefined?
But in more general terms, I am wondering what the scope of this work
is. Is the goal to provide a mechanism similar to what we have already
for 'config true' datastores for 'config false' datastores or is the
goal to replace the existing mechanism with a new mechanism that will
cover both 'config true' and 'config false' datastores?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
