Call for volunteer authors (was Re: NETCONF over TLS)

[Andy Bierman <ietf@andybierman.com>]

Balazs Lengyel wrote:
> Hello,
> Although we should treat all transports as equal and I have no BIG 
> problems with the draft, I remember that we had problems with the Beep 
> and SOAP transports as well to get people to review and update the 
> transport documents.

This is an important point.
We are still looking for volunteers (who understand the edits)
to take over authorship of the SSH and BEEP transport documents.

We somehow need to document the transport details for supporting notifications.
The update for SSH seems very minor -- there are places where the <rpc>
and/or <rpc-reply> elements are mentioned explicitly, and the <notification>
element also needs to be mentioned.  There are no SSH protocol differences
whatsoever, due to the notification feature.

The BEEP document needs to be reviewed, and updated for notifications.
Clearly the BEEP Profile needs to include the <notification> element,
but there may be other text that needs updating.

The SOAP document would require significant work to support Notifications,
exactly as defined in the draft (e.g., without changes to any of the RPCs).

Of course, the TLS document must support the Notification draft as well.

Notifications is going to be done soon, and transports which do not get
updated to support them will almost certainly be reclassified as Historic.

> Balazs

Andy

--
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/>