[as112-ops] Important ops message for all AS112 operators

[kato at wide.ad.jp]

Dear William,

By now I've configured our AS112 server running in Osaka to
- add new zones of "hostname.as112.net", "hostname.as112.arpa", and
  "empty.as112.arpa" to already configured zones for RFC1918/RFC6890 zones.
- advertise 192.31.196.0/24, 2001:4:112::/48, 2620:4f:8000::/48
(they may not be visible to a remote location, however).
We see about 1/4 packets are in IPv6.

Even only about 10 hours, I've done it prior to DITL2015 :-)

-- Akira Kato

From: "William F. Maton Sotomayor" <wmaton at ottix.net>
Subject: Re: [as112-ops] Important ops message for all AS112 operators
Date: Wed, 18 Mar 2015 13:53:14 -0400 (EDT)

> 
> 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
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops