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/[email protected]/
[db-wg] MNTNER Naming : Consensus
- Previous message (by thread): [db-wg] WHOIS Referrals for transferred number resources
- Next message (by thread): [db-wg] MNTNER Naming : Consensus
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lutz Donnerhacke
L.Donnerhacke at iks-service.de
Thu Oct 1 08:53:24 CEST 2020
So the general scheme is SOURCE-NAME-FUNCTION, i.e. RIPE-NCC-MNT ? Von: db-wg <db-wg-bounces at ripe.net> Im Auftrag von William Sylvester via db-wg Gesendet: Mittwoch, 30. September 2020 21:44 An: db-wg at ripe.net Betreff: [db-wg] MNTNER Naming : Consensus db-wg members, The chairs of the database working group believe there is a consensus to have a standardised name format for creating new MNTNER objects. There was talk of a prefix (MNT-) or a suffix (-MNT). When creating a new standard it doesn't really make sense to introduce a standard with multiple formats. As there are currently 36347 MNTNERs that end with -MNT and 12480 MNTNERs that start with MNT-, we suggest that the standard should be to end with -MNT. We ask the RIPE NCC to take the next steps in moving this request forward, conducting an impact analysis, and proceed with implementation. Best regards. William & denis db-wg chairs -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20201001/1f359b22/attachment.html>
- Previous message (by thread): [db-wg] WHOIS Referrals for transferred number resources
- Next message (by thread): [db-wg] MNTNER Naming : Consensus
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]