This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] Update convention

Previous message (by thread): [db-wg] Request for unsuscription
Next message (by thread): [db-wg] Update convention

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Niall O'Reilly Niall.oReilly at ucd.ie
Fri Jun 16 01:30:34 CEST 2006

Begin forwarded message:
> domain:        3.5.3.e164.arpa
> nserver:       ns01.3.5.3.e164.arpa 137.43.132.54
> nserver:       ns02.3.5.3.e164.arpa 213.190.149.193
> nserver:       enum1.eu.afilias.info
> notify:        ENUM-353-OPS at LISTSERV.HEANET.IE
> changed:       Niall.oReilly at ucd.ie 20060614
> changed:       someone at comreg.ie 20040323
> changed:       hostmaster at ripe.net 20041222
> source:        RIPE
> ***Error: Required attribute "descr" is missing
> ***Error: Required attribute "admin-c" is missing
> ***Error: Required attribute "tech-c" is missing
> ***Error: Required attribute "zone-c" is missing

I thought we used to have a convention that attributes to be left  
unchanged
in an existing object could validly be omitted in the update request.

Did I miss a considered change, or am I doing some "wishful  
recollection"?

/Niall

Previous message (by thread): [db-wg] Request for unsuscription
Next message (by thread): [db-wg] Update convention

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]