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] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Tue Nov 29 20:44:36 CET 2022
Cynthia Revström wrote on 29/11/2022 18:56: > I agree with Nick. > However there are currently as-set objects in RIPE based on aut-num > objects in RIPE-NONAUTH. > I think it might be worth considering if these should be cleaned up. > I posted about this about a week ago in a separate thread on db-wg. right, yes, you're correct. I've included a list below. The RIPE NCC can't stand over the authenticity of these objects because the AS in question isn't a RIPE-authenticated ASN. So RIPE-NONAUTH would be an appropriate place for them. Changing this should not be service affecting, because the AS in question is already RIPE-NONAUTH. Having said that, "should not" is not the same as "will not". Some of these objects are stale. Some of them are legacy resources, but can be subject to the same approach as defined in ripe-731. Do we need a policy change to move these, e.g. similar to ripe-731, or simply including them in the scope of ripe-731? Nick -- AS702:AS-AT-CUSTOMER AS702:AS-BE-CUSTOMER AS702:AS-CH-CUSTOMER AS702:AS-CUSTOMER AS702:AS-CZ-CUSTOMER AS702:AS-DE-CUSTOMER AS702:AS-DK-CUSTOMER AS702:AS-ES-CUSTOMER AS702:AS-EURO-CUSTOMER AS702:AS-FI-CUSTOMER AS702:AS-FR-CUSTOMER AS702:AS-GR-CUSTOMER AS702:AS-HU-CUSTOMER AS702:AS-IE-CUSTOMER AS702:AS-IT-CUSTOMER AS702:AS-NL-CUSTOMER AS702:AS-NO-CUSTOMER AS702:AS-PT-CUSTOMER AS702:AS-SE-CUSTOMER AS702:AS-UK-CUSTOMER AS4004:AS-TO-AIX AS9327:AS-HOPCOUNT AS12041:AS-AFILIAS AS12041:AS-PEERS AS12041:AS-SET AS12041:AS-SET:AS12287 AS12041:AS-SET:AS13714 AS12041:AS-SET:AS13901 AS12041:AS-SET:AS40490 AS12041:AS-TRANSIT AS12287:AS-AFILIAS AS13657:AS-EGATE AS13657:AS-PEERS AS13657:AS-TRANSIT AS13714:AS-AFILIAS AS13810:AS-AFILIAS AS13901:AS-AFILIAS AS17400:AS-CUSTOMERS AS19551:AS-GLOBAL AS20375:AS-CUSTOMERS AS21003:AS-LTT AS24115:AS-GENEVA AS24115:AS-PARIS AS24115:AS-ZURICH AS26754:AS-PEERS AS36692:AS-UMBRELLA AS36925:AS-MEDI AS36925:AS-PROVIDERS AS36997:AS-TRANSIT AS37002:AS-ALL AS37012:AS-ALL AS37133:AS-327707 AS37148:AS-GLOBACOM AS37155:AS-PROVIDERS AS37183:AS-SET AS37284:AS-ALJEEL AS37314:AS-CUSTOMERS AS37314:AS-CUSTOMERS:AS328074 AS37314:AS-JINX AS37314:AS-NAPAFRICA AS37314:AS-NEOTEL AS37314:AS-SEACOM AS37366:AS-PROVIDERS AS37558:AS-LITC AS38193:AS-PEERS-RIPE AS396071:AS-COMPLETE AS396071:AS-CUSTOMERS AS40490:AS-AFILIAS AS55293:AS-A2HOSTING AS58580:AS-ALL AS62512:AS-CUSTOMER AS135164:AS-PEERS AS135183:AS-INSTALINKS AS327717:AS-26754 AS327717:AS-26754:AS-328015 AS327717:AS-328015 AS327717:AS-328084 AS327938:AS-PEERS
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]