[ipv6-wg] Draft Minutes (v1) of IPv6 WG session RIPE51

[Microsoft/OpenTransit folks, look for '3ffe:8310::/28' for the Teredo
prefix question]

On Fri, 2005-10-21 at 06:01 -0700, David Kessens wrote:
> Please see enclosed the first version of the minutes of our session at RIPE51.
> 
> I plan to declare the minutes final if I don't receive any comments
> for significant changes by November 4th 2005.
<SNIP>

Just a couple of notes, thus no comments on the minutes themselves, as I
was not present, thus I might repeat some obvious things that where
already said during the meeting.

{There are at least two typo's look for the braces}

>    Conclusion: as we cannot force people to filter, we will see more
>    specifics anyways (David Kessens)

What I have seen is that a number of times, when more specifics are
announced, eg /48's that the 'better quality' networks filter them out,
the prefix will then be carried only by 'less qualitity' networks or
more politically correct, the route goes a couple of times around the
world. Notorious are mostly Korean 'transit providers' who seem to
accept anything.

<SNIP> {NOTE: the typo in IljiTsch's name on the next line}

>    Iljisch v B.: DNS is not auto-configurable in IPv6 like it is in
>    IPv4 so I would like to use 6bone to get an ipv6 assignment for an
>    experiment for well-known ipv6 DNS resolver addresses.

Iljitsch, for this there is of course:
http://www.ripe.net/ripe/docs/ipv6policy.html#experiment-assignments
No need for 6bone space :)

Next to that, dhcpv6 of course works eg using dibbler, which provides
the same mechanism.

I am also in favor of the idea that Iljitsch has and to have a single IP
address (which has to be part of a /32 or so to be not filtered...)
which is the 'closest' dns service. I tried this in sort of a way at the
last IETF though, but the word 'anycast' freaks out quite some people,
see section 4 of the following for the relevant part:
http://unfix.org/~jeroen/archive/drafts/draft-massar-dnsop-service-00.txt
Though I understood that that doc hit on about 5 holy wars or so :)

>    Geoff H. : IANA has released a statment that 6bone dies on
>    06/06/2006.
> 

{NOTE: GerT with a T}

>    Gerd D.: exactly, what will people do when this happens?
>    
>    No uniform policy on what to do with 6bone prefixes. Some people
>    will start filtering while others won't bother.

From RFC3701:
8<---------------
   Thus after the 6bone phaseout date June 6, 2006, it is the intent
   that no 6bone 3FFE prefixes, of any size/length, be used on the
   Internet in any form.  Network operators may filter 3FFE prefixes on
   their borders to ensure these prefixes are not misused.
--------------->8

Nothing states though how to handle the case where people are announcing
these prefixes, my intention is to start contacting people who are
currently still using their prefix and reminding them that they need to
drop it. This is the same situation when some ISP simply starts
announcing eg 2005:1234:/32, what happens? People accept it or? Provided
one has enough resources (read: cash) I actually guess most ISP's can be
convinced/bribed that they will be accepted and IANA/RIR's are out of
the loop.  Then again remembering the 2003::/16 prefix from Microsoft,
that got filtered quite hard by many, though I guess also because of
some 'anti-m$' thoughts there ;)
Which leads to another nice question, Teredo's are per default using a
6bone prefix (3ffe:8310::/28).... what is happening with that one
because I assume that won't disappear from this planet 1,2,3!?
At the moment that prefix is being announced by Microsoft (AS8070)
The 3ffe:831f::/32 is also announced by OpenTransit (AS5511):

inet6num:     3FFE:831F::/32
netname:      WANADOO-EXP-IPV6-6BONE
descr:        France Telecom Wanadoo IPV6 experimentations
country:      FR
admin-c:      ML50-6BONE
tech-c:       ML50-6BONE
mnt-by:       FT-BRX
changed:      gestionip.ft at francetelecom.com 20050721
source:       6BONE

That date is pretty new btw, clearly from GRH most ISP's also accept it.

When folks got 6bone pTLA's they also agreed to read the 6bone
mailinglist, but it has been seen already quite some times that many
don't, directly contacting is thus going to be required.

http://www.sixxs.net/tools/grh/dfp/6bone/
8<----------------------
The database currently holds 144 IPv6 DFP's.
Of which 31 (21.53%) are returned to the pool, 29 (20.14%) IPv6 DFP's
didn't have a routing entry.
Thus 84 (58.33%) networks are currently announced.
---------------------->8
about 60% left...

Another related note on this subject; what is going to happen to
www.6bone.net ? Is it going to be updated to something nice referring to
information about IPv6 or? There are also quite a number of broken links
on that page and most of the information is outdated or has been
revised.

>    In general, people advised David Kessens who maintains the 6bone
>    registry to stop accepting registry changes by the close date but to
>    keep the data online for some time to come with proper warning
>    message when information is accessed.

The registry is a good thing to keep, it is like having an old phone
book around and your phonebills from that era, one can lookup the
'historical' data in there. So I agree with the above.

Greets,
 Jeroen

PS: I did a presentation about SixXS / Deploying IPv6 at SwiNOG #11, for
interrested people, see: http://www.swinog.ch/meetings/swinog11/
Misses the words and it is indeed quite big but pictures tell quite a
bit.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-wg/attachments/20051022/b6df9e38/attachment.sig>