Le 18/10/2024 à 13:52, Kessler, Emmanuel a écrit :
Hi Kessler, and all, Hope this email finds you in health!
[...]1) With the addition of the nibble boundary, how do we ensure that the policy complies with the “Registration goal”, which is essential for Internet troubleshooting and avoiding abuse?
Thanks for you email, brother! ...maybe this should be answered by RIPE NCC :-/
Are PIs required to register End Site information ?
You may want to read [1] the "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region — RIPE Network Coordination Centre" __ [1]: https://www.ripe.net/publications/docs/ripe-637/
What type of information is recorded by PI and how is this information made accessible to a requesting Authority?
...while waiting for a more authoritative answer, please, feel free: look at the following references. Ref#1| Information for Law Enforcement Agencies — RIPE Network Coordination Centre https://www.ripe.net/about-us/legal/information-for-law-enforcement-agencies/ Ref#2| RIPE NCC Report: Law Enforcement Agency Requests — RIPE Network Coordination Centre https://www.ripe.net/publications/lea-documents/
What type of information is recorded by the End User, for example about his End-Sites? How they provide information when requested by an Authority, ensuring that they comply with “Registration goal”?
...below are references containing authoritative information regarding the Structure of the RIPE Database. Ref#3| Primary and Secondary Objects | Docs https://docs.db.ripe.net/RIPE-Database-Structure/Primary-and-Secondary-Objects/ Ref#4| Database Objects | Docs https://docs.db.ripe.net/RIPE-Database-Structure/Database-Object/ ...i'm leaving other parts of your question to other WG participants including RIPE NCC ;-)
How to ensure that an IP range is used by a single party and not more?
...imho! it's one of the objectives of RIR delegations:. ...btw, don't forget that it's perfectly fine to have a scenario where the same IP prefix is being announced from different ASNs. That's where you need to create appropriate ROA (Route Origin Authorisations) certificates within the right RPKI CA. So that, a multi-origin routed IP prefix works more securely. ...maybe i didn't understood what you meant :-/ Please, let me know. Thanks. Shalom, --sb.
[...]
-- Best Regards !baya.sylvain [AT cmNOG DOT cm] | cmNOG's Structure <https://www.cmnog.cm/dokuwiki/Structure> | CAMIX's Website <https://www.camix.cm/> | Douala-IX's Looking Glass <https://tools.std.douala-ix.net/lg> | cmNOG's Surveys <https://survey2.cmnog.cm/> | Subscribe to cmNOG's Mailing List <https://lists.cmnog.cm/mailman/listinfo/cmnog> |
__#LASAINTEBIBLE|#Colossiens2:14,13-17«14 IL a effacé l'acte dont les ordonnances nous condamnaient et qui subsistait contre nous, et IL l'a détruit en le clouant à la croix;»#AMEN,#Maranatha,#MerciJÉSUS!
#MaPrière est que tu naisses de nouveau.#Chrétiennement
OpenPGP_0x0387408365AC8594.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
