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]/
[routing-wg] Adding "::" notation to RIPE DB
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Bensley
james at inter.link
Sun Nov 13 14:48:17 CET 2022
From: Alexander Zubkov <green at qrator.net> Sent: 13 November 2022 14:12 To: James Bensley Cc: Netmaster (exAS286); routing-wg at ripe.net Subject: Re: [routing-wg] Adding "::" notation to RIPE DB I think the idea is that RIPE::AS-65534:AS-EXAMPLE addresses AS-65534:AS-EXAMPLE object in the RIPE database. Is there reasons to allow to have both RIPE::AS-65534:AS-EXAMPLE and AS-65534:AS-EXAMPLE in the single RIPE database? ________________________________________ Hi Alexander, That is what I'm saying: I agree, one name needs to point to the other, so that we don't have two objects in the database, only one object. I just wasn't clear about how the pointing would work and if it would affect anything else in the DB beyond get request (like create or delete requests). But I guess there will only every be objects called "AS-65534:AS-EXAMPLE" in the DB (as per my original email to the list), "RIPE::" would be stripped from the front of the query if present, and stripped from responses if the query comes from a legacy client (as per your suggestion). Cheers, James.
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]