Re: Purely editorial changes to the notification draft

[David Partain <david.partain@ericsson.com>]

Hello again,

On Wednesday 25 July 2007 22:03:21 David Partain wrote:
> I think it would be better to use startTime and stopTime (and other
> similar "keywords") throughout rather than using "start time" sometimes
> and "startTime" in others.  I have, however, not made this change.  I would
> be happy to make changes to startTime and stopTime if others think this is
> a good idea.

The attached diff shows what I mean...

David

--- draft-ietf-netconf-notification-08.txt.orig2	2007-07-25 22:25:23.000000000 +0200
+++ draft-ietf-netconf-notification-08.txt	2007-07-25 22:34:07.000000000 +0200
@@ -373,12 +373,12 @@
          by other parameters will be sent.  See section 3.6 for more
          information on filters.
 
-      Start Time:
+      startTime:
 
          A parameter used to trigger the replay feature and indicate
          that the replay should start at the time specified.  If
          startTime is not present, this is not a replay subscription.
-         It is valid to specify start times that are later than the
+         It is valid to specify a startTime that is later than the
          current time.  If the startTime specified is earlier than the
          log can support, the replay will begin with the earliest
          available notification.  This parameter is of type dateTime.
@@ -392,13 +392,13 @@
 Internet-Draft         NETCONF Event Notifications             July 2007
 
 
-      Stop Time:
+      stopTime:
 
          An optional parameter used with the optional replay feature to
-         indicate the newest notifications of interest.  If stop time is
+         indicate the newest notifications of interest.  If stopTime is
          not present, the notifications will continue until the
          subscription is terminated.  Must be used with and be later
-         than 'startTime'.  It is valid to specify stop times that are
+         than startTime.  It is valid to specify a stopTime that is
          later than the current time.  This parameter is of type
          dateTime.
 
@@ -508,8 +508,8 @@
 
    Closing of the event notification subscription can be done by
    terminating the NETCONF session ( <kill-session> ) or the underlying
-   transport session.  If a stop time is provided when the subscription
-   is created, the subscription will terminate after the stop time
+   transport session.  If stopTime is provided when the subscription
+   is created, the subscription will terminate after stopTime
    is reached.  In this case, the NETCONF session will still be an
    active session.
 
@@ -851,11 +851,11 @@
 3.3.2.  Creating a Subscription with Replay
 
    This feature uses optional parameters to the <create-subscription>
-   command called 'startTime' and 'stopTime'. 'startTime' identifies the
+   command called startTime and stopTime. The startTime identifies the
    earliest date and time of interest for event notifications being
    replayed and also indicates that a subscription will be providing
    replay of notifications.  Events generated before this time are not
-   matched. 'stopTime' specifies the latest date and time of interest
+   matched. The stopTime specifies the latest date and time of interest
    for event notifications being replayed.  If it is not present, then
    notifications will continue to be sent until the subscription is
    terminated.
@@ -864,9 +864,9 @@
    event was generated by the system.
 
    A replayComplete notification is sent to indicate that all of the
-   replay notifications have been sent.  If this subscription has a stop
-   time, then this session becomes a normal NETCONF session again.  If
-   the subscription has no stop time, it can be expected that any
+   replay notifications have been sent.  If this subscription has a stopTime,
+   then this session becomes a normal NETCONF session again.  If
+   the subscription has no stopTime, it can be expected that any
    notifications generated since the start of the subscription creation
    will be sent after the replayComplete notification has been sent,
    followed by notifications as they arise naturally within the system.
@@ -879,7 +879,7 @@
    session becomes normal command-response NETCONF session.
 
    The replayComplete can not be filtered out.  It will always be sent
-   on a replay subscription that specified a stop time.
+   on a replay subscription that specified a stopTime.
 
 3.4.  Notification Management Schema
 
@@ -1204,7 +1204,7 @@
                                 A parameter used to trigger the replay
                                 feature and indicates that the replay
                                 should start at the time specified. If
-                                start time is not present, this is not a
+                                startTime is not present, this is not a
                                 replay subscription.
                             </xs:documentation>
                         </xs:annotation>
@@ -1216,10 +1216,10 @@
                                 An optional parameter used with the
                                 optional replay feature to indicate the
                                 newest notifications of interest. If
-                                stop time is not present, the
+                                stopTime is not present, the
                                 notifications will continue until the
                                 subscription is terminated. Must be used
-                                with 'startTime'.
+                                with startTime.
                             </xs:documentation>
                         </xs:annotation>
                     </xs:element>