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.2: removal of cross notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at ripe.net
Mon Mar 10 11:01:12 CET 2003
On 2003-03-10 15:47:51 +1000, Sanjaya wrote: > > 1. I just want to point out that the example is not exactly correct? > 192.168.201.0/24 is not more specific than 192.168.101.0/24. They > don't even overlap ;-) Yikes! I guess that should be 192.168.0.0/16. :( > 2. Just to confirm my understanding: the successful creation of a > more specific inetnum will trigger a notification to all mnt-nfy: of > the parent block's mnt-lower(s). Is this correct? That is correct, and a *failed* creation of a more specific inetnum will trigger notification to all "upd-to:" of the same maintainers. -- Shane Kerr RIPE NCC
- Previous message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific
- Next message (by thread): [db-wg] Proposed change 2003.2: removal of cross notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]