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] Proposed change 2003.1: notification for more-specific

• Previous message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific
• Next message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific

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

Tim McGinnis mctim at ripe.net
Mon Mar 10 16:26:37 CET 2003

O
> 
> p.s. I also think that "upd-to:" and "mnt-nfy:" are probably not the
>      best names.  But what can we expect of a standard with things
>      like "mntner:" and "aggr-mtd:"?   (These names can't be to
>      shorten them, or we wouldn't have "peering-set:" and
>      "mbrs-by-ref:")?  Would it make sense to make an alias for
>      "upd-to:" of something reasonable, e.g. "auth-fail-nfy:"?
> 

You beauty!!

and one for the other "mnt-nfy", something reasonable, e.g. "hey-your-update-worked"



-- 

 
McTim

• Previous message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific
• Next message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific

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

[ db-wg Archives ]