[ncc-services-wg] Recent Database update changes

On Wed, 13 Oct 2004, Denis Walker wrote:

> 2) Handling of keywords in the Subject: line of a mail update.
> 
/----/
> 
> We could easily make another change, if users would prefer it, so that
> keywords will ONLY be accepted if they follow the KEYWORDS: tag. This would
> make the default behaviour ignore the whole Subject: line and not report any
> of it as errors if the KEYWORDS: tag is not found. This default behaviour may
> be more appropriate to the way the Subject: line is currently used in most
> cases. Please let us know if this is preferred.

I prefer the second option. We don't need these keywords very often but
always use own keywords (ticket number, action, object name) so that reply 
from RIPE can be merged directly to ticketing system

> 3) Differnce in notification messages

I'd like to have an option to get unified diff. The context length might
be even so big that you get full object together. Something like this:

 person:       Test Person
 address:      Singel 258
 address:      Amsterdam
 phone:        +31 20 535 4444
 nic-hdl:      TP10-DB-TEST
 changed:      dbtest at ripe.net 20020101
-notify:       case040-1 at ripe.net
+changed:      dbtest at ripe.net 20040101
+notify:       case040-2 at ripe.net
 source:       DB-TEST

Without any context it is anyway hard to understand the diff output
sepcially in aut-num object where import and export entries may have more
than one line. If you don't change the first line then you may loose the
context and diff like this doesn't give you any information about what
peer was actually changed.


<               accept ANY
===
>               accept ANY AND NOT {0.0.0.0/0}


-- 
Cougar

Data Telecom OÜ                                   Marko Veelma
Laki 11B, 12915 Tallinn                           marko.veelma at data.ee
Phone +372 881 0299            data telecom       Phone +372 881 0289
Fax +372 654 2942             --------------      GSM +372 50 92042