RE: TimeFilter edits

Hi,

While created columns imply that a created row would be reported,
deleted columns will not be reported if the whole row is deleted.
How about simply adding to your current proposal "A deleted row is not
reported."

David Harrington
[email protected]

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Andy Bierman
> Sent: Friday, January 21, 2005 12:23 PM
> To: Randy Presuhn
> Cc: [email protected]
> Subject: Re: [RMONMIB] TimeFilter edits
> 
> At 09:51 PM 1/20/2005, Randy Presuhn wrote:
> >Hi -
> >
> >> From: "Andy Bierman" <[email protected]>
> >> To: <[email protected]>
> >> Sent: Thursday, January 20, 2005 4:47 PM
> >> Subject: [RMONMIB] TimeFilter edits
> >...
> >> The attached file contains proposed edits for the TimeFilter
> >> TC and Appendix.  Please send comments to the list ASAP so Steve
> >> can update the RFC2021-bis draft.
> >...
> >
> >Some people (not me!) like to define sparse columnar objects.
> >If a row already exists, but has holes, and later one of the
> >holes gets plugged, is that covered by the proposed TimeFilter
> >text?
> 
> You're referring to a column that is instantiated sometime
> after the rest of the row?  If any column is created, modified,
> or deleted, the lastChangeTime is updated.  (!! So the edit
> that Dave H asked for in the TC need to change.  
> 
> "A row is considered to be changed when any columnar object
> within the row is created, modified, or deleted."
> 
> Is this text okay?
> 
> 
> 
> >Randy
> 
> Andy
> 
> 
> 
> 
> 
> >_______________________________________________
> >RMONMIB mailing list
> >[email protected]
> >https://www1.ietf.org/mailman/listinfo/rmonmib 
> 
> _______________________________________________
> RMONMIB mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rmonmib
>