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/ncc-services-wg@ripe.net/
[ncc-services-wg] Re: [routing-wg] Analysis of the ‘Maximum Length’ Option in Certification ROAs
- Previous message (by thread): [ncc-services-wg] Re: [routing-wg] Analysis of the ‘Maximum Length’ Option in Certification ROAs
- Next message (by thread): [ncc-services-wg] Proposal to Introduce SHA2 Passwords in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Band
alexb at ripe.net
Wed Apr 20 17:49:04 CEST 2011
On 19 Apr 2011, at 21:40, Randy Bush wrote: > hi alex, > > one thing that interests me which i did not see in your analysis. or > maybe i just need more coffee. > > how many, what proportion of, bgp announcements were for prefixes longer > than the allocation in the roa and were properly described by a max-len? Good question, let me look into that. Right now the analysis just focussed on the amount of prefixes that would be invalid because of incorrect usage of MaxLength, but it's quite likely a number of ROAs were created simply with /24 as MaxLength to allow for the freedom to deaggregate (or ease of use), when in reality the AS is only announcing a less specific aggregate. > as to your choices, i would go with 1 or 2 (make it a mandatory blank > field, forcing the user to make an explicit decision). 3 and 4 are > horrible. Duly noted. -A
- Previous message (by thread): [ncc-services-wg] Re: [routing-wg] Analysis of the ‘Maximum Length’ Option in Certification ROAs
- Next message (by thread): [ncc-services-wg] Proposal to Introduce SHA2 Passwords in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]