Re: Draft B: NETCONF Montreal Interim Meeting Minutes

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Mon, Aug 14, 2006 at 08:41:03AM -0700, Andy Bierman wrote:
 
> Trying again with less bugs, as an attachment.

Attached are some cosmetic fixes. There is one hidden question I like
to comment on:

> f) The WG needs to investigate the use of SSH channels
>    for separation of operations and notifications.
> 
>    [ed. - does this imply multiple NETCONF sessions over
>    a single SSH connection? What exactly does this mean?]

SSH has the nice feature that it provides independent channels running
over the same underlying TCP session and sharing the same SSH session
keys etc. which makes them pretty lightweight mechanisms to separate
different NETCONF notification channels or to seperate NETCONF
notification channels from the "normal" NETCONF RPC channel.

There was some discussion during the meeting whether the SSH mapping
document actually allows us to make use of SSH channels or not. Item
f) quoted above was recorded as an action item to carefully re-read
draft-ietf-netconf-ssh-<latest> and to figure out what the document
actually says and to compare that to what the intention was the
document should be saying.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

--- interim_minutes_B.txt	2006-08-16 01:40:37.000000000 +0200
+++ interim_minutes_C.txt	2006-08-16 01:32:36.000000000 +0200
@@ -11,7 +11,7 @@
 Simon Leinen <simon@switch.ch>
 Andy Bierman <ietf@andybierman.com>
 
-Notes: Andy Bierman, Juergen Shoenwaelder
+Notes: Andy Bierman, Juergen Schoenwaelder
 Minutes: Andy Bierman
 
 -----------------------------------------------
@@ -555,7 +555,7 @@
    in this working group (part 1 above).  
 
 g) The configuration of stream selection and notification
-   suppression filters in in scope (part 2 above).
+   suppression filters are in scope (part 2 above).
 
 h) Notification suppression filtering is data-model and 
    stream dependent.
@@ -573,7 +573,7 @@
 3.1) Long-Lived RPC vs. Mixed-Mode RPC
 
 It is assumed that a new RPC method will be created for
-the manager to use to cause the agent to start the delivery
+the manager to cause the agent to start the delivery
 of notifications.  All parameters needed to configure
 the session-specific delivery of notifications should
 be passed as parameters (by reference or by value).