[6bone] Summer cleanup time for IPv6 aggregation!

[Jeroen Massar]

Roger Jorgensen [mailto:rjorgensen@upctechnology.com] wrote:

> Someone out there has now recently opened up their filters and are
> passing on /48's and lots of other things. Check older stats 
> and you'll
> see that much of this crap wasn't there before.
> 
> 
> My point of view on this can be put this way:
> 
> 1) If you want to have strict aggregation (after the RFC) you 
> filter incoming AND outgoing

One could be "nice" to incoming peers ofcourse, that doesn't put
anything in the global routing table which should belong there.

> 2) If you want less strict aggregation it's okay to allow upto /48's
> both incoming and outgoing (I assume people do filter away not wanted
> announcment if they follow the RFC letter by letter) and incoming.
> Anything smaller than /48's are not accepted under any circumstances)

That's your point of view, there will probably be some smaller parties
then who will have a point of view
that /128's are okay, or people who will have point of view that
ddossing people is normal etc....
It's the GLOBAL routing table we are talking about. Not that peering
session between some friends.
If we would start announcing everything there wouldn't be a need for
RIR's to exist now was there?

"I'll take that small /48 from you and announce it myself, saves me from
going through the RIR's"
And then everybody will be a RIR-alike entity and it _will_ become a
huge mess.

> At 01:17 PM 7/25/2002 +0200, Jeroen Massar wrote:
> <SNIP>
> 
> since I'm part of the IPv6 team here at chello (UPC Technology is more
correct)
> I'll comment on this part.
> 
> >8<---------
> >CHELLO (AS6830) announced 16 route(s)
> >     3ffe:2501:100::/48 path 10566 6939 6830 8733 (TVD -- 52%)
> >     3ffe:8070:1010::/48 path 12199 145 11537 786 109 4618  (INET-TH
--
> >4%)
> >     3ffe:8070:1010::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:2900:2004::/48 path 12199 145 11537 786 109 4618 (INET-TH
--
> >4%)
> >     3ffe:2900:2004::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:1300:7::/48 path 12199 145 11537 786 109 4618 (INET-TH --
4%)
> >     3ffe:1300:7::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:327e:1::/48 path 12199 145 11537 786 109 4618 (INET-TH --
4%)
> >     3ffe:327e:1::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:4005:a::/48 path 12199 145 11537 786 109 4618 (INET-TH --
4%)
> >     3ffe:4005:a::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:80ee:556::/48 path 12199 145 11537 786 109 4618 (INET-TH --
4%)
> >     3ffe:80ee:556::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:200:c::/48 path 10566 6939 6830 2847 ( -- 52%)
> >     3ffe:80b0:1002::/48 path 10566 6939 6830 8733 (TVD -- 52%)
> >     2001:6e0:202::/48 path 12199 145 11537 786 109 5539 1853 6830
8209 ( -- 4%)
> >     3ffe:400b:6002::/48 path 12199 145 11537 786 109 4618 (INET-TH
-- 4%)
> >     3ffe:400b:6002::/48 path 10566 6939 6830 (CHELLO -- 100%)
> >     3ffe:81a0:1012::/48 path 12199 145 11537 786 109 4618 (INET-TH
--4%)
> >     3ffe:81a0:1012::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:2500:322::/48 path 12199 145 11537 786 109 4618 (INET-TH --
4%)
> >     3ffe:2500:322::/48 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:8271:a080::/44 path 12199 145 11537 786 109 4618 (INET-TH
-- 4%)
> >     3ffe:8271:a080::/44 path 10566 6939 6830 (CHELLO -- 52%)
> >     3ffe:82bf::/32 path 10566 6939 6830 24643 (NEXTGEN-LAB -- 52%)
> >     3ffe:2640::/32 path 10566 6939 6830 790 6793 (TELIAFI -- 51%)
> >--------->8
> >And even more /48's, /44's and /32's and even double entries, great
to
> >spread those.
> >
> >inet6num:     3FFE:82B0::/28
> >netname:      WEBONLINE-NET
> >descr:        WebOnline AS
> >
> >Keep those peerings private...
> 
> 3ffe:82bf::/32 is delegated to AS24643, also us. It's been in the list
forever.
> AS8209 is also us, think I maybe should create a 6bone entry for it.

"It's been in the list forever" translates to "we never took care of
cleaning it up"
Maybe one could consider merging them into one AS ?

Also as this is a /28 entry only the /28 should pop up in the global
routing table, nothing else.

Btw... you didn't cover the Thailand prefixes ;)

> and a general comment:
> 
> What's wrong with letting through 3ffe::/16 le /32 ? (know it break
the current
> RFC), but wouldn't it be an idea to let both 2001 and 3ffe 
> space be aggregated upto /32 ? (2001 are, but 3ffe aren't)
Because it breaks the "RIR dealt out the prefix" rule.
eg TLA's having a /24 could then do the "I am a RIR too" game if you
specify it that way.
Which in effect mostly will lead to the "everybody is a RIR" effect
again.

Another way would be revoking all the non /32's from the sixbone space
and let people
keep only one /32, but that won't work as they are (at least some people
say) in active use.
So those 3 extra lines is something we will have to cope with for the
time being.

6bone will go away in the long run. It's a testbed and it should be
tightly policed
to make sure it doesn't make any problems for the productional IPv6
space.
Btw... enterzone for example just requested a pTLA for "testing", they
are using their
RIR space for production. Which is good. And then those filters can go
too...

> And on a later stage, maybe we should change the RFC and 
> allow even something
> bigger than /32 be let through, /40 ? (/48's are too big to 
> be let through 
> on a RFC base)

You want to creat PI space, and there *IS* none.
You can send *ANYTHING* you want to your peers as long as it doesn't
popup in the global routing table.
Repeat after me: Multihoming is currently not possible with IPv6 untill
ipv6mh work is done.

Check: http://arneill-py.sacramento.ca.us/ipv6mh/

Number one in the charter:
8<----------
- Develop IPv6 multihoming solutions that can be deployed in a
reasonable amount of time (before aggregation is broken).
  No IPv6 multihoming, no IPv6.
---------->8

And if all the people/companies/organisations keep announcing all kinds
of wierd
things they won't make that "before aggregation is broken" part.
It's coming along just fine, ofcourse any help is appreciated!

IPv6 - Just keep it clean.

Greets,
 Jeroen