Sharon,
Hi Ideally we will issue updates to the various transport mapping documents with any required changes in order to be able to support notifications. Presumably we can't start that work until the documents are published as RFCs. We've been holding the text in our document for safe keeping (although I agree the BEEP text is a bit broken currently). Are we suggesting now is the time to remove this text from the document? Where would it go?
Once again I think we are suffering the poor choices we have made in the past by both having multiple transports and by requiring that each capability be available to each mapping. Yes, we said that. If we stick to that, the best approach to implement this silliness is to actually do what you did and stick this stuff in one document that updates all three. Just get people to test each and you should be able to easily get to proposed this way. If you really want three documents, then I assure this working group that we will not have three separate but equal mappings, because it is as likely as not for each capability you will not have an author or implementation available.
This having been said, I've given you the basis for text that should be sufficient for BEEP.
Eliot -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/netconf/>