Hi all, I support a change of the current policy. We had a case ourselves (Anycast services) where we preferred a aggregatable prefix rather than individual /48s. Unfortunately, we could not convince the RIPE NCC during the discussion and ultimately opted for separate /48s instead of delaying the project further. In our network design a sub allocation from our PA space was not feasible. I can agree with Gert's concerns that the new policy version is very detailed. I fear that this problem might require a broader, more global perspective and may not be resolved easily. One potential solution might be to amend the policy to allow LIRs with PA space to more easily acquire larger PI allocations for infrastructure purposes. This would help in our mentioned case above. The question remains whether such a distinction would be desirable and broadly acceptable. There was also a discussion somewhere regarding the statement in section 2.9.2: "a Layer 2 connection between two End Sites does not make them one End Site as long as both End Sites have different routing policies." In my opinion, the "Layer 2" should simply be removed. The precise nature of the connection is irrelevant for this paragraph. As long as we have no alternative proposal, I fully support the current one and would like to see it accepted. Regards, Bene On 11/14/24 08:38, Tobias Fiebig via address-policy-wg wrote:
Moin,
TL;DR: If you: - Support the proposal; OR - Are ok with the proposal/see no issue in moving it forward; OR - Can live with the proposal if thereafter a thorough cleanup effort of the whole policy starts, please speak up now. -------------
The extended discussion phase of 2024-01 is drawing closer to its end.
After the presentation at the last meeting there was a lot of positive feedback, and a couple of people promised to write on the mailinglist (which, contrary to offline comments, counts).
The major comment during the session was Gert noting that the proposal uses a lot of text. My counter point was that the grown policy we currently have necessitates that amount of text to account for all the corner cases and (excuse my German) 'Sonderlocken' we created over the decades.
My point on that is that fixing this needs a more comprehensive revision of the policy foundation, which will take us several years;
My suggestion is: - Implement 2024-01 - Start working on the more fundamental clean-up thereafter, as this will take long
In any case, I do need some feedback from you; Otherwise, this will not be able to move in any direction.
With best regards, Tobias
-- Karlsruher Institut für Technologie (KIT) Scientific Computing Center (SCC) Benedikt Neuffer Netze und Telekommunikation (NET) Zirkel 2 Gebäude 20.20 Raum 156 76131 Karlsruhe Telefon: +49 721 608-46342 Fax: +49 721 608-47763 E-Mail: benedikt.neuffer@kit.edu Matrix: @iv4011:kit.edu Web: https://www.scc.kit.edu Sitz der Körperschaft: Kaiserstraße 12, 76131 Karlsruhe KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Signaturversion: 24.3.0 beta