About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

RE: [6bone] Re: [ipv6-wg@localhost] Update on IPv6 filter recommendation

  • To: "'John Fraizer'" < >
  • From: "Jeroen Massar" < >
  • Date: Tue, 13 May 2003 20:09:21 +0200
  • Cc: < >
    < >
  • Organization: Unfix

John Fraizer [
] wrote: > On Tue, 13 May 2003, Jeroen Massar wrote: > > > John Fraizer wrote: > > > > > I don't think that an exception should be made for > microallocations at > > > all. To paraphrase what ARIN says, there is no guarantee > that address > > > space that they assign will be globally routable. > > > > You should note that that also goes for the rest of the allocations. > > 69/8 in IPv4 anyone ? :) > > The alloocations I have seen have problems out of 69/8 were not > micro-allocations. They were /19's and /18's. I'm sure that > there are a few /20's in there with a token /24 perhaps but, the ones I > have knowledge of were _real_ allocations and not micro-allocations. Yes, but what I meant is the fact that a RIR can't possibly guarantee routability of a prefix. Which was the case seen with 69/8. Even then if a big transit doesn't want to carry your prefix for $reason it won't be reachable either ;) Greets, Jeroen

  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community