Subject: [netmod] New Version Notification for draft-voit-netmod-peer-mount-requirements-02

From: "Eric Voit (evoit)" <[email-masked]>
Date: Thu, 12 Mar 2015 14:42:01 +0000

At IETF 91, there was much good discussion on Peer Mount.  Based on these discussions we authors have split embodied concepts into two separate IETF paths:

(1) YANG Pub/Sub
        draft-ietf-i2rs-pub-sub-requirements
        draft-clemm-netconf-yang-push  (was draft-netmod-clemm-datastore-push)
(2) YANG Peer Mount
        draft-voit-netmod-peer-mount-requirements
        draft-clemm-netmod-mount

These two concepts can stand on their own, but can also work well together.  Why?   Peer Mount is made more effective when remote object changes can be pushed to local applications without fetching.

At this point we authors are spending more time progressing (1) YANG Pub/Sub as it can be used standalone without Peer Mount, and also because the I2RS WG has immediate need.  But (2) YANG Peer Mount is being shown effective in OpenDaylight as Network Element changes are being pushed into SDN applications.   Therefore we will continue to revise the Peer Mount drafts.  But we will be doing at a slower pace.

I will be at IETF 92.  Reach out to me if you want to discuss.  Mailing list comments to any of the drafts are also very appreciated.

Thanks,
Eric 

Eric Voit