On 2/2/15 6:53 PM, 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
Support. In fact, the traceability draft calls out pub-sub in 7.4.3.
It would be nice to see this use case mentioned in the Voit draft.
Joe
The current I2RS charter states:
“The I2RS working group works to develop a high-level architecture
thatdescribes the basic building-blocks necessary to enable the specific
usecases, and that will lead to an understanding of the abstract
informational models and requirements for encodings and protocols for
the I2RS interfaces.”
This draft is part of setting the requirements for the I2RS protocol.
As Andy has noted in early email, there may be nothing specific to I2RS
in draft-voit-i2rs-pub-sub-requirements-00.txt. It may be something
that should be just a part of the netconf/restconf functionality. As
part of the adoption of this draft, the I2RS chairs would like to hear
your opinion of Andy’s statement. Andy also suggests that
draft-netmod-clemm-datastore-push-00 should also be part of the I2RS
requirements.
http://www.ietf.org/mail-archive/web/i2rs/current/msg02252.html
[chair hat-off] IMHO, I think Andy is correct. [chair-hat on ].
If the WG approves adoption of
draft-voit-i2rs-pub-sub-requirements-00.txt and the WG feels these
drafts should be netmod WG drafts with I2RS holding a requirement
drafts, the I2RS chairs will do the right thing to make it happen. If
enough people comment that draft-netmod-clemm-datastore-push-00 should
be part of the I2RS requirements, we will do a WG adoption of call for
this requirement.
Sue Hares
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
