From wmaton at ottix.net  Wed Mar 18 00:08:45 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Tue, 17 Mar 2015 20:08:45 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
Message-ID: <alpine.DEB.2.03.1503172001190.20158@ottix.net>


All,

As per certain IANA actions found in draft-ietf-dnsop-rfc6304bis-06.txt, 
the following has now taken place:

- IPv6 records for AS112 have gone live.  For those of you already doing
   the experimental IPv6 connectivity of the past while, I would be
   interested in knowing if you are seeing queries now - shouldn't
   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
   a good time to deploy DSC if you have not already.

https://www.dns-oarc.net/tools/dsc

- Those of you who are otherwise not IPv6 connected, be aware AS112 is
   essentially dual-stack.

- The AS number (112) and the IPv4 and IPv6 network blocks have each
   been registered in the IANA special use registries, formalising
   their use for the Internet community's information.

More info on the progress on the draft towards RFC can be found here:

http://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc6304bis/history/

And of course a reminder to encourage you to participate in the upcoming 
DITL collection scheduled for next month.

Thanks,

wfms

From wmaton at ottix.net  Wed Mar 18 00:59:24 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Tue, 17 Mar 2015 20:59:24 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
Message-ID: <alpine.DEB.2.03.1503172058390.20158@ottix.net>

On Tue, 17 Mar 2015, William F. Maton Sotomayor wrote:

> As per certain IANA actions found in draft-ietf-dnsop-rfc6304bis-06.txt, the 
> following has now taken place:
>
> - IPv6 records for AS112 have gone live.  For those of you already doing
>  the experimental IPv6 connectivity of the past while, I would be
>  interested in knowing if you are seeing queries now - shouldn't
>  be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>  a good time to deploy DSC if you have not already.

20:58:24.570911 IP6 2001:da8:20f:3032::12.20040 > 2620:4f:8000::42.53: 
33269 [1au] PTR? 129.30.168.192.in-addr.arpa. (56)

Well OK, it didn't take long.

wfms

From kato at wide.ad.jp  Wed Mar 18 02:30:16 2015
From: kato at wide.ad.jp (kato at wide.ad.jp)
Date: Wed, 18 Mar 2015 11:30:16 +0900 (JST)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
Message-ID: <20150318.113016.2172721759318406107.kato@wide.ad.jp>

Dear William,

I have two things to clarify:

- As far as I remember, there were some discussion on AS112 servers
  to include IPv6 version of zones such as unspecified, multicast,
  link-local, etc. They are not available at this moment (and we don't
  have to care them), right?

- To implement "blackhole.as112.arpa", the machine should accept
  queries to 192.31.196.1 (in the -06 draft, it was specified as
  TBA-address-v4), and advertisze 192.31.196.0/24 from as112 to
  the global routing table. Also applied to its IPv6 version,
  the machine should accept queries to 2001:4:112::1 (in the
  -06 draft, it was specified as TBA-address-v6), and advertisze
  2001:4:112::/48 from as112 to the global routing table.

I will work to modify our servers and their router within a few
weeks, prior to DITL2015.

-- Akira Kato, WIDE Project

From: "William F. Maton Sotomayor" <wmaton at ottix.net>
Subject: [as112-ops] Important ops message for all AS112 operators
Date: Tue, 17 Mar 2015 20:08:45 -0400 (EDT)

> 
> All,
> 
> As per certain IANA actions found in
> draft-ietf-dnsop-rfc6304bis-06.txt, the following has now taken place:
> 
> - IPv6 records for AS112 have gone live.  For those of you already doing
>   the experimental IPv6 connectivity of the past while, I would be
>   interested in knowing if you are seeing queries now - shouldn't
>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>   a good time to deploy DSC if you have not already.
> 
> https://www.dns-oarc.net/tools/dsc
> 
> - Those of you who are otherwise not IPv6 connected, be aware AS112 is
>   essentially dual-stack.
> 
> - The AS number (112) and the IPv4 and IPv6 network blocks have each
>   been registered in the IANA special use registries, formalising
>   their use for the Internet community's information.
> 
> More info on the progress on the draft towards RFC can be found here:
> 
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc6304bis/history/
> 
> And of course a reminder to encourage you to participate in the
> upcoming DITL collection scheduled for next month.
> 
> Thanks,
> 
> wfms
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops

From anandb at ripe.net  Wed Mar 18 07:52:05 2015
From: anandb at ripe.net (Anand Buddhdev)
Date: Wed, 18 Mar 2015 08:52:05 +0100
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
Message-ID: <55092EA5.8040403@ripe.net>

On 18/03/15 01:08, William F. Maton Sotomayor wrote:

Hi William,

> - IPv6 records for AS112 have gone live.  For those of you already doing
>   the experimental IPv6 connectivity of the past while, I would be
>   interested in knowing if you are seeing queries now - shouldn't
>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>   a good time to deploy DSC if you have not already.

We refreshed our AS112 kit at AMS-IX last week, and took the opportunity
to set it up with IPv6. And as soon as we announced the IPv6 prefix, we
began getting queries at a substatial rate.

However, we have turned off the IPv6 announcements for now, because we
have an issue with the server's ethernet driver. It begins discarding
packets if too many queries are received over IPv6. Once we have found a
solution for this, we will announce the IPv6 prefix.

Regards,
Anand Buddhdev
RIPE NCC

From wmaton at ottix.net  Wed Mar 18 10:45:27 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 06:45:27 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <20150318.113016.2172721759318406107.kato@wide.ad.jp>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
Message-ID: <alpine.DEB.2.03.1503180640190.20158@ottix.net>

On Wed, 18 Mar 2015, kato at wide.ad.jp wrote:

> Dear William,

Hello!

> I have two things to clarify:
>
> - As far as I remember, there were some discussion on AS112 servers
>  to include IPv6 version of zones such as unspecified, multicast,
>  link-local, etc. They are not available at this moment (and we don't
>  have to care them), right?

Correct.  The DNAME draft is proposing an alternative to a potentially 
endless stream of requests to instruct IANA to do delegations.

> - To implement "blackhole.as112.arpa", the machine should accept
>  queries to 192.31.196.1 (in the -06 draft, it was specified as
>  TBA-address-v4), and advertisze 192.31.196.0/24 from as112 to
>  the global routing table. Also applied to its IPv6 version,
>  the machine should accept queries to 2001:4:112::1 (in the
>  -06 draft, it was specified as TBA-address-v6), and advertisze
>  2001:4:112::/48 from as112 to the global routing table.

Indeed, is is accroding to:

http://tools.ietf.org/html/draft-ietf-dnsop-as112-dname-06

I know the authors lurk on this list, so if these have gone live, it would 
be good to know about these also.

> I will work to modify our servers and their router within a few
> weeks, prior to DITL2015.

OK thank you!

>
> -- Akira Kato, WIDE Project
>
> From: "William F. Maton Sotomayor" <wmaton at ottix.net>
> Subject: [as112-ops] Important ops message for all AS112 operators
> Date: Tue, 17 Mar 2015 20:08:45 -0400 (EDT)
>
>>
>> All,
>>
>> As per certain IANA actions found in
>> draft-ietf-dnsop-rfc6304bis-06.txt, the following has now taken place:
>>
>> - IPv6 records for AS112 have gone live.  For those of you already doing
>>   the experimental IPv6 connectivity of the past while, I would be
>>   interested in knowing if you are seeing queries now - shouldn't
>>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>>   a good time to deploy DSC if you have not already.
>>
>> https://www.dns-oarc.net/tools/dsc
>>
>> - Those of you who are otherwise not IPv6 connected, be aware AS112 is
>>   essentially dual-stack.
>>
>> - The AS number (112) and the IPv4 and IPv6 network blocks have each
>>   been registered in the IANA special use registries, formalising
>>   their use for the Internet community's information.
>>
>> More info on the progress on the draft towards RFC can be found here:
>>
>> http://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc6304bis/history/
>>
>> And of course a reminder to encourage you to participate in the
>> upcoming DITL collection scheduled for next month.
>>
>> Thanks,
>>
>> wfms
>> _______________________________________________
>> as112-ops mailing list
>> as112-ops at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>

wfms

From wmaton at ottix.net  Wed Mar 18 12:31:31 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 08:31:31 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <20150318.113016.2172721759318406107.kato@wide.ad.jp>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
Message-ID: <alpine.DEB.2.03.1503180829180.20158@ottix.net>

On Wed, 18 Mar 2015, kato at wide.ad.jp wrote:

> - To implement "blackhole.as112.arpa", the machine should accept
>  queries to 192.31.196.1 (in the -06 draft, it was specified as
>  TBA-address-v4), and advertisze 192.31.196.0/24 from as112 to
>  the global routing table. Also applied to its IPv6 version,
>  the machine should accept queries to 2001:4:112::1 (in the
>  -06 draft, it was specified as TBA-address-v6), and advertisze
>  2001:4:112::/48 from as112 to the global routing table.

Sorry, one more thing:  I seem to recall seeing 192.31.196.0/24 in martian 
filters in the past, so if that's used, we may see some interesting 
issues.

wfms

From nick at inex.ie  Wed Mar 18 12:44:18 2015
From: nick at inex.ie (Nick Hilliard)
Date: Wed, 18 Mar 2015 12:44:18 +0000
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503180829180.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net>
Message-ID: <55097322.2030101@inex.ie>

On 18/03/2015 12:31, William F. Maton Sotomayor wrote:
> Sorry, one more thing:  I seem to recall seeing 192.31.196.0/24 in martian
> filters in the past, so if that's used, we may see some interesting issues.

this prefix is still defined in the Level3 IRR DB as a martian:

% whois -h rr.level3.net rs-martians

I don't know whether Level 3 uses this on their networks, but it would be a
good idea to check with them before providing a service on 192.31.196.0/24.

Nick


From wmaton at ottix.net  Wed Mar 18 12:51:04 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 08:51:04 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <55097322.2030101@inex.ie>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
Message-ID: <alpine.DEB.2.03.1503180849560.20158@ottix.net>

On Wed, 18 Mar 2015, Nick Hilliard wrote:

> On 18/03/2015 12:31, William F. Maton Sotomayor wrote:
>> Sorry, one more thing:  I seem to recall seeing 192.31.196.0/24 in martian
>> filters in the past, so if that's used, we may see some interesting issues.
>
> this prefix is still defined in the Level3 IRR DB as a martian:
>
> % whois -h rr.level3.net rs-martians
>
> I don't know whether Level 3 uses this on their networks, but it would be a
> good idea to check with them before providing a service on 192.31.196.0/24.

Indeed.  I'm not subscribed to any of the *NOG's any more, perhaps it 
would be good for someone to let the community (and Level 3) know what's 
coming.

wfms

From nick at inex.ie  Wed Mar 18 13:09:59 2015
From: nick at inex.ie (Nick Hilliard)
Date: Wed, 18 Mar 2015 13:09:59 +0000
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503180849560.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
 <alpine.DEB.2.03.1503180849560.20158@ottix.net>
Message-ID: <55097927.8090107@inex.ie>

On 18/03/2015 12:51, William F. Maton Sotomayor wrote:
> Indeed.  I'm not subscribed to any of the *NOG's any more, perhaps it would
> be good for someone to let the community (and Level 3) know what's coming.

some active measurement from e.g. RIPE atlas would probably also be a
sensible idea.

Nick


From iortiz at ripe.net  Wed Mar 18 13:31:48 2015
From: iortiz at ripe.net (=?windows-1252?Q?I=F1igo_Ortiz_de_Urbina_Cazenave?=)
Date: Wed, 18 Mar 2015 14:31:48 +0100
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <55097927.8090107@inex.ie>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
 <alpine.DEB.2.03.1503180849560.20158@ottix.net> <55097927.8090107@inex.ie>
Message-ID: <55097E44.30205@ripe.net>

On 18/03/15 14:09, Nick Hilliard wrote:
> some active measurement from e.g. RIPE atlas would probably also be a
> sensible idea.

Actually, as part of an unrelated exercise we scheduled measurement
#1896798 [1] two days ago.

We are currently analysing the results and we were also considering
extending the experiment to the new IPv6 counterparts.

Since there is an apparent interest in also measuring the reachability
of 192.31.196.1, we'll put some though into that as well.

FWIW the initial analysis of measurement #1896798 shows 101 and 148
distinct nsid and hostname.bind values respectively.

We're not such a small group of operators after all :-)

Cheers,

I?igo Ortiz de Urbina Cazenave
RIPE NCC

[1] https://atlas.ripe.net/api/v1/measurement/1896798/?format=json

From wmaton at ottix.net  Wed Mar 18 13:36:31 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 09:36:31 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <55097E44.30205@ripe.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
 <alpine.DEB.2.03.1503180849560.20158@ottix.net> <55097927.8090107@inex.ie>
 <55097E44.30205@ripe.net>
Message-ID: <alpine.DEB.2.03.1503180932370.20158@ottix.net>

On Wed, 18 Mar 2015, I?igo Ortiz de Urbina Cazenave wrote:

> On 18/03/15 14:09, Nick Hilliard wrote:
>> some active measurement from e.g. RIPE atlas would probably also be a
>> sensible idea.
>
> Actually, as part of an unrelated exercise we scheduled measurement
> #1896798 [1] two days ago.

Very cool.

> We are currently analysing the results and we were also considering
> extending the experiment to the new IPv6 counterparts.

In a forth-coming presentation, I'll be sharing my results from querying 
about 7 million open resolvers, which yielded some more AS112 node 
hideouts.  Most interesting result:  There's a node in New Caledonia. 
Good on them for the record is to be believed!

> Since there is an apparent interest in also measuring the reachability
> of 192.31.196.1, we'll put some though into that as well.

I started announcing from OttIX, and already hit some martian filters very 
close by.  I've not been as thorough with the IPv6 counterpart but suspect 
that's making it through.

> FWIW the initial analysis of measurement #1896798 shows 101 and 148
> distinct nsid and hostname.bind values respectively.

nsid, yeah that reminds me....

> We're not such a small group of operators after all :-)

The more the merrier! :-)

wfms

From nick at inex.ie  Wed Mar 18 14:37:24 2015
From: nick at inex.ie (Nick Hilliard)
Date: Wed, 18 Mar 2015 14:37:24 +0000
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503180849560.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
 <alpine.DEB.2.03.1503180849560.20158@ottix.net>
Message-ID: <55098DA4.4050308@inex.ie>

On 18/03/2015 12:51, William F. Maton Sotomayor wrote:
> Indeed.  I'm not subscribed to any of the *NOG's any more, perhaps it would
> be good for someone to let the community (and Level 3) know what's coming.

Also, there are no route: objects for any of these new prefixes. This is
also going to cause some trouble for the organisations who use prefix
filtering based on irrdbs.

Nick




From wmaton at ottix.net  Wed Mar 18 14:41:21 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 10:41:21 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <55098DA4.4050308@inex.ie>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
 <alpine.DEB.2.03.1503180829180.20158@ottix.net> <55097322.2030101@inex.ie>
 <alpine.DEB.2.03.1503180849560.20158@ottix.net>
 <55098DA4.4050308@inex.ie>
Message-ID: <alpine.DEB.2.03.1503181040570.20158@ottix.net>

On Wed, 18 Mar 2015, Nick Hilliard wrote:

> On 18/03/2015 12:51, William F. Maton Sotomayor wrote:
>> Indeed.  I'm not subscribed to any of the *NOG's any more, perhaps it would
>> be good for someone to let the community (and Level 3) know what's coming.
>
> Also, there are no route: objects for any of these new prefixes. This is
> also going to cause some trouble for the organisations who use prefix
> filtering based on irrdbs.

Just freshly registered some minutes ago.  Let's see how quickly the 
mirroring to the IRR gets that out.
wfms

From nick at inex.ie  Wed Mar 18 16:27:41 2015
From: nick at inex.ie (Nick Hilliard)
Date: Wed, 18 Mar 2015 16:27:41 +0000
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
Message-ID: <5509A77D.9030302@inex.ie>

On 18/03/2015 00:08, William F. Maton Sotomayor wrote:
 > - IPv6 records for AS112 have gone live.  For those of you already doing
>   the experimental IPv6 connectivity of the past while, I would be
>   interested in knowing if you are seeing queries now - shouldn't
>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>   a good time to deploy DSC if you have not already.

the INEX as112 node on 193.242.111.6 has now gone live on ipv6 and we're
seeing a small amount of v6 traffic.  Once the route: object situation has
been fixed up, we'll probably see a good deal more.

Nick

From clement at cavadore.net  Wed Mar 18 16:36:14 2015
From: clement at cavadore.net (Clement Cavadore)
Date: Wed, 18 Mar 2015 17:36:14 +0100
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <alpine.DEB.2.03.1503172058390.20158@ottix.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <alpine.DEB.2.03.1503172058390.20158@ottix.net>
Message-ID: <1426696574.4625.1.camel@banga.hivane.net>

On Tue, 2015-03-17 at 20:59 -0400, William F. Maton Sotomayor wrote:
> Well OK, it didn't take long.

Yep, we see some IPv6 traffic now:

http://noc.hivane.net/cgi-bin/dsc-grapher.pl?binsize=60&window=86400&plot=client_subnet_accum&server=as112


Regards,
-- 
Cl?ment Cavadore
Hivane
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20150318/50656acc/attachment-0001.sig>

From wmaton at ottix.net  Wed Mar 18 16:47:17 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 12:47:17 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <1426696574.4625.1.camel@banga.hivane.net>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <alpine.DEB.2.03.1503172058390.20158@ottix.net>
 <1426696574.4625.1.camel@banga.hivane.net>
Message-ID: <alpine.DEB.2.03.1503181246570.20158@ottix.net>


Thanks, we're seeing quite a lot here as well, but our DSC graphs are 
delayed a bit. :-/

On Wed, 18 Mar 2015, Clement Cavadore wrote:

> On Tue, 2015-03-17 at 20:59 -0400, William F. Maton Sotomayor wrote:
>> Well OK, it didn't take long.
>
> Yep, we see some IPv6 traffic now:
>
> http://noc.hivane.net/cgi-bin/dsc-grapher.pl?binsize=60&window=86400&plot=client_subnet_accum&server=as112
>
>
> Regards,
> -- 
> Cl?ment Cavadore
> Hivane
>

wfms

From wmaton at ottix.net  Wed Mar 18 16:52:03 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 12:52:03 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <5509A77D.9030302@inex.ie>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <5509A77D.9030302@inex.ie>
Message-ID: <alpine.DEB.2.03.1503181251230.20158@ottix.net>

On Wed, 18 Mar 2015, Nick Hilliard wrote:

> On 18/03/2015 00:08, William F. Maton Sotomayor wrote:
> > - IPv6 records for AS112 have gone live.  For those of you already doing
>>   the experimental IPv6 connectivity of the past while, I would be
>>   interested in knowing if you are seeing queries now - shouldn't
>>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>>   a good time to deploy DSC if you have not already.
>
> the INEX as112 node on 193.242.111.6 has now gone live on ipv6 and we're
> seeing a small amount of v6 traffic.  Once the route: object situation has
> been fixed up, we'll probably see a good deal more.

Thanks for that.  I've updated another long-ago forgotten IRR which should 
be happy as well.  I suspect folks will take time to get around to 
generating their filters.

  wfms

From wmaton at ottix.net  Wed Mar 18 17:53:14 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Wed, 18 Mar 2015 13:53:14 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <20150318.113016.2172721759318406107.kato@wide.ad.jp>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <20150318.113016.2172721759318406107.kato@wide.ad.jp>
Message-ID: <alpine.DEB.2.03.1503181351370.20158@ottix.net>


Further on this:

blackhole.as112.arpa has address 192.31.196.1
blackhole.as112.arpa has IPv6 address 2001:4:112::1

For AS112-YOW's part, we've now done this but I'm not seeing the routes 
for -dname- get out there yet from our node.  But we're ready.

Others would be well advised to read Mr. Kato's note below.

Thanks all,

On Wed, 18 Mar 2015, kato at wide.ad.jp wrote:

> Dear William,
>
> I have two things to clarify:
>
> - As far as I remember, there were some discussion on AS112 servers
>  to include IPv6 version of zones such as unspecified, multicast,
>  link-local, etc. They are not available at this moment (and we don't
>  have to care them), right?
>
> - To implement "blackhole.as112.arpa", the machine should accept
>  queries to 192.31.196.1 (in the -06 draft, it was specified as
>  TBA-address-v4), and advertisze 192.31.196.0/24 from as112 to
>  the global routing table. Also applied to its IPv6 version,
>  the machine should accept queries to 2001:4:112::1 (in the
>  -06 draft, it was specified as TBA-address-v6), and advertisze
>  2001:4:112::/48 from as112 to the global routing table.
>
> I will work to modify our servers and their router within a few
> weeks, prior to DITL2015.
>
> -- Akira Kato, WIDE Project
>
> From: "William F. Maton Sotomayor" <wmaton at ottix.net>
> Subject: [as112-ops] Important ops message for all AS112 operators
> Date: Tue, 17 Mar 2015 20:08:45 -0400 (EDT)
>
>>
>> All,
>>
>> As per certain IANA actions found in
>> draft-ietf-dnsop-rfc6304bis-06.txt, the following has now taken place:
>>
>> - IPv6 records for AS112 have gone live.  For those of you already doing
>>   the experimental IPv6 connectivity of the past while, I would be
>>   interested in knowing if you are seeing queries now - shouldn't
>>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>>   a good time to deploy DSC if you have not already.
>>
>> https://www.dns-oarc.net/tools/dsc
>>
>> - Those of you who are otherwise not IPv6 connected, be aware AS112 is
>>   essentially dual-stack.
>>
>> - The AS number (112) and the IPv4 and IPv6 network blocks have each
>>   been registered in the IANA special use registries, formalising
>>   their use for the Internet community's information.
>>
>> More info on the progress on the draft towards RFC can be found here:
>>
>> http://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc6304bis/history/
>>
>> And of course a reminder to encourage you to participate in the
>> upcoming DITL collection scheduled for next month.
>>
>> Thanks,
>>
>> wfms
>> _______________________________________________
>> as112-ops mailing list
>> as112-ops at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>

wfms

From wmaton at ottix.net  Thu Mar 19 13:24:39 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Thu, 19 Mar 2015 09:24:39 -0400 (EDT)
Subject: [as112-ops] Important ops message for all AS112 operators
In-Reply-To: <5509A77D.9030302@inex.ie>
References: <alpine.DEB.2.03.1503172001190.20158@ottix.net>
 <5509A77D.9030302@inex.ie>
Message-ID: <alpine.DEB.2.03.1503190923440.20158@ottix.net>

On Wed, 18 Mar 2015, Nick Hilliard wrote:

> On 18/03/2015 00:08, William F. Maton Sotomayor wrote:
> > - IPv6 records for AS112 have gone live.  For those of you already doing
>>   the experimental IPv6 connectivity of the past while, I would be
>>   interested in knowing if you are seeing queries now - shouldn't
>>   be but who knows, NATs behind IPv6 wouldn't surprise me.  It may be
>>   a good time to deploy DSC if you have not already.
>
> the INEX as112 node on 193.242.111.6 has now gone live on ipv6 and we're
> seeing a small amount of v6 traffic.  Once the route: object situation has
> been fixed up, we'll probably see a good deal more.

Things are looking a little better this morning, but I still see some 
reach problems over the high-performance NSPs.  Will rattle some contacts.

wfms

From wmaton at ottix.net  Mon Mar 23 11:30:50 2015
From: wmaton at ottix.net (William F. Maton Sotomayor)
Date: Mon, 23 Mar 2015 07:30:50 -0400 (EDT)
Subject: [as112-ops] DITL 2015 test dates
Message-ID: <alpine.DEB.2.03.1503230722450.20158@ottix.net>


All
 	For those interested in participating (and you are encouraged to 
do so), there is a test run for DITL.  Here are some details:

- Refresh your memories about what DITL is about:

         https://www.dns-oarc.net/oarc/data/ditl

- Ensure your patched NTP/clock sync software is functioning on your
   participating servers;

- To have a look at the latest 'ditl-' capture software suite located
   here:

         https://dnscap.dns-oarc.net/

- And familiarise yourselves with the upload process which hasn't changed
   over the course of the years:

         https://www.dns-oarc.net/ditl/2011/

Note that if you do chose to participate, it's a good idea to join the
DITL mailing list where questions and discussions for the event are best
held.

For particpating in the testing for AS112 operators, you can test your 
DITL upload capabilities (and we thank you for your
contribution), by using the following in your settings.sh file:

START_T='2015-03-30 11:00:00'
STOP_T='2015-03-31 13:00:00'

wfms

PS If you are not an AS112 operator, you should not be on this list.

