From wmaton at ottix.net  Tue Jul  5 00:52:10 2011
From: wmaton at ottix.net (William F. Maton)
Date: Mon, 4 Jul 2011 20:52:10 -0400 (EDT)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
Message-ID: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>


All,

 	Good news:  The DNS-OARC has acquired an IPv6 network block for 
the use of AS112 nodes to anycast with, as a counterpart to its IPv4 
version.  Now, before people go crazy, there are some considerations to 
take into account:

- There's the draft from March to the IETF called
   draft-michaelson-as112-ipv6-00 which undoubtedly seeks input from the
   community;

- I have a draft setup page on converting an existing IPv4 node to use that
   draft's suggested zone list as well as configuring for IPv6 BGP peering,
   in my particular node's case.  The page is here:

 	http://public.as112.net/node/26

   Comments on this hack are welcome; and

- Absolutely, positively NO delegations of IPv6 reverse zones have been
   made, so even if the instructions were followed, the only queries that
   will work are deliberate ones made by an operator trying things out.

Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 and 
I would be very interested if any of the fellow advanced academic and 
research networks that happen to have IPv6 connectivity can see this 
route.

Thanks,

wfms

From ask at develooper.com  Tue Jul  5 02:25:53 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Mon, 4 Jul 2011 19:25:53 -0700
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <B6C042FB-3C12-4B15-86D5-27BE85DF407E@develooper.com>


On Jul 4, 2011, at 17:52, William F. Maton wrote:

> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 and I would be very interested if any of the fellow advanced academic and research networks that happen to have IPv6 connectivity can see this route.

Don't know about academic and research networks, but here at a plain old regular commercial network (AS53582) the route is coming through Hurricane Electric:

  6939 6509 2884 112

I started setting up our AS112 anycast node here with the IPv6 prefix, but I didn't announce it yet.  I'll wait for a message on the mailing list here to say it's time.


 - ask

-- 
http://develooper.com/ - http://askask.com/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1946 bytes
Desc: not available
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20110704/f9ffd496/attachment.bin>

From vlk at lcpe.uni-sofia.bg  Tue Jul  5 04:41:08 2011
From: vlk at lcpe.uni-sofia.bg (Vesselin Kolev)
Date: Tue, 05 Jul 2011 07:41:08 +0300
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <4E1295E4.2030505@lcpe.uni-sofia.bg>

Dear William,

We (AS5421, Sofia University "St. Kliment Ohridski") receive prefix
2620:4f:8000::0/48 through GEANT2 (AS20965,http://www.geant2.net/) and
also through our commercial uplink (AS8717). You can see the quagga
vtysh dump bellow:

[quaggaterm at border-lozenets ~]$ vtysh -e "sh bgp 2620:4f:8000::0/48"
BGP routing table entry for 2620:4f:8000::/48
Paths: (2 available, best #2, table Default-IP-Routing-Table)
  Advertised to non peer-group peers:
  2001:67c:20d0:ffff::3 2001:67c:20d0:ffff::4 2001:67c:20d0:ffff::5
2001:67c:20d0:ffff::7 2001:67c:20d0:ffff::8 2001:67c:20d0:ffff::9
2001:67c:20d0:ffff::a 2001:67c:20d0:ffff::b 2001:67c:20d0:ffff::c
2001:67c:20d0:ffff::d 2001:67c:20d0:ffff::e 2001:67c:20d0:ffff::f
2001:67c:20d0:ffff::10
  8717 6939 6509 2884 112
    2001:67c:20d0:fffe:ffff:ffff:ffff:fffe from
2001:67c:20d0:fffe:ffff:ffff:ffff:fffe (212.50.10.31)
    (fe80::219:e203:c3b5:67c1)
      Origin IGP, localpref 50, valid, external
      Community: 0:90 0:6695
      Extended Community: RT:8717:90 RT:8717:8717 SoO:8717:90 ?
      Last update: Tue Jul  5 07:07:06 2011

  6802 20965 6509 2884 112
    2001:4b58:acad:252::25 from 2001:4b58:acad:252::25 (194.141.252.13)
    (fe80::205:9aff:fefd:781a)
      Origin IGP, localpref 100, valid, external, best
      Last update: Sat Jul  2 19:51:50 2011


In addition, GEANT2 looking glass portal is publicly accessible here:

https://tools.geant.net/portal/links/lg/

You can measure visibility of 2620:4f:8000::0/48 at all GEANT2 POPs
across Europe. Looking glass platform is directly connected to JunOS
interface, so the output is JunOS formatted.


Best regards

     Vesselin Kolev - VK1242-RIPE



On 07/05/2011 03:52 AM, William F. Maton wrote:
>
> All,
>
>     Good news:  The DNS-OARC has acquired an IPv6 network block for
> the use of AS112 nodes to anycast with, as a counterpart to its IPv4
> version.  Now, before people go crazy, there are some considerations
> to take into account:
>
> - There's the draft from March to the IETF called
>   draft-michaelson-as112-ipv6-00 which undoubtedly seeks input from the
>   community;
>
> - I have a draft setup page on converting an existing IPv4 node to use
> that
>   draft's suggested zone list as well as configuring for IPv6 BGP
> peering,
>   in my particular node's case.  The page is here:
>
>     http://public.as112.net/node/26
>
>   Comments on this hack are welcome; and
>
> - Absolutely, positively NO delegations of IPv6 reverse zones have been
>   made, so even if the instructions were followed, the only queries that
>   will work are deliberate ones made by an operator trying things out.
>
> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48
> and I would be very interested if any of the fellow advanced academic
> and research networks that happen to have IPv6 connectivity can see
> this route.
>
> Thanks,
>
> wfms
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops


From clement at cavadore.net  Tue Jul  5 06:49:26 2011
From: clement at cavadore.net (Clement Cavadore)
Date: Tue, 05 Jul 2011 08:49:26 +0200
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <1309848566.30876.7.camel@puisard>

On Mon, 2011-07-04 at 20:52 -0400, William F. Maton wrote:
> All,
> 
>  	Good news:  The DNS-OARC has acquired an IPv6 network block for 
> the use of AS112 nodes to anycast with, as a counterpart to its IPv4 
> version.  Now, before people go crazy, there are some considerations to 
> take into account:
> 
> - There's the draft from March to the IETF called
>    draft-michaelson-as112-ipv6-00 which undoubtedly seeks input from the
>    community;
> 
> - I have a draft setup page on converting an existing IPv4 node to use that
>    draft's suggested zone list as well as configuring for IPv6 BGP peering,
>    in my particular node's case.  The page is here:
> 
>  	http://public.as112.net/node/26
> 
>    Comments on this hack are welcome; and

Great news, Will have a look on this :)

> - Absolutely, positively NO delegations of IPv6 reverse zones have been
>    made, so even if the instructions were followed, the only queries that
>    will work are deliberate ones made by an operator trying things out.
> 
> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 and 
> I would be very interested if any of the fellow advanced academic and 
> research networks that happen to have IPv6 connectivity can see this 
> route.
> 

Here is how it's seen from AS34019:

   Network            Next Hop              Path
*>i 2620:4f:8000::/48 2001:7f8:54::10       6939 6509 2884 112 i
*   2620:4f:8000::/48 2001:7f8:43::6939:1   6939 6509 2884 112 i

Best regards,
-- 
Cl?ment Cavadore


From ask at develooper.com  Tue Jul  5 07:14:29 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Tue, 5 Jul 2011 00:14:29 -0700
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <715D77C5-0330-47F9-A2F0-DC3EDD6987B6@develooper.com>


On Jul 4, 2011, at 17:52, William F. Maton wrote:

> 	http://public.as112.net/node/26
> 
>  Comments on this hack are welcome; and

- in named.conf, the IPv6 addresses need to be in an listen-on-v6 block (rather than in the listen-on block).

- "b.e.f.ip6.arpa" is listed twice in your example.

- in the db.empty6 example, the opening "(" for the SOA needs to be on the SOA line rather than on the next line.


  - ask

-- 
http://develooper.com/ - http://askask.com/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1946 bytes
Desc: not available
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20110705/19d30713/attachment.bin>

From kbrint at qwest.net  Tue Jul  5 16:19:28 2011
From: kbrint at qwest.net (kevin brintnall)
Date: Tue, 5 Jul 2011 11:19:28 -0500
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <20110705161928.GC58166@qwest.com>

On Mon, Jul 04, 2011 at 08:52:10PM -0400, William F. Maton wrote:
> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 and 
> I would be very interested if any of the fellow advanced academic and 
> research networks that happen to have IPv6 connectivity can see this 
> route.

AS 209 sees this network via "6939 6509 2884 112".

-- 
 kevin brintnall <kbrint at qwest.net>
 Network Engineer, Qwest

From clement at cavadore.net  Tue Jul  5 17:57:54 2011
From: clement at cavadore.net (Clement Cavadore)
Date: Tue, 05 Jul 2011 19:57:54 +0200
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <1309888674.30876.15.camel@puisard>

Hi William,


On Mon, 2011-07-04 at 20:52 -0400, William F. Maton wrote:
> All,
> 
>  	Good news:  The DNS-OARC has acquired an IPv6 network block for 
> the use of AS112 nodes to anycast with, as a counterpart to its IPv4 
> version.  Now, before people go crazy, there are some considerations to 
> take into account:
> 
> - There's the draft from March to the IETF called
>    draft-michaelson-as112-ipv6-00 which undoubtedly seeks input from the
>    community;
> 
> - I have a draft setup page on converting an existing IPv4 node to use that
>    draft's suggested zone list as well as configuring for IPv6 BGP peering,
>    in my particular node's case.  The page is here:
> 
>  	http://public.as112.net/node/26
> 
>    Comments on this hack are welcome; and
> 
> - Absolutely, positively NO delegations of IPv6 reverse zones have been
>    made, so even if the instructions were followed, the only queries that
>    will work are deliberate ones made by an operator trying things out.
> 
> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 and 
> I would be very interested if any of the fellow advanced academic and 
> research networks that happen to have IPv6 connectivity can see this 
> route.

I started announcing it from our AS112 node (and configured our DNS
server to be authoritative on the listed zones). 
Hope it's not too early ? If so, let me know, and we will stop the BGP
session waiting for your go.

Best regards,

-- 
Cl?ment Cavadore


From wmaton at ottix.net  Thu Jul 14 18:33:41 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 14 Jul 2011 14:33:41 -0400 (EDT)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <1309888674.30876.15.camel@puisard>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
Message-ID: <Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>


(Catching up on a lot of email, so here's a nice-sized reply...)

On Tue, 5 Jul 2011, Clement Cavadore wrote:

> I started announcing it from our AS112 node (and configured our DNS
> server to be authoritative on the listed zones).
> Hope it's not too early ? If so, let me know, and we will stop the BGP
> session waiting for your go.

Clement:  I don't think it's any harm, as it will be interesting to see to 
which path the IPv6 traffic settles on for its destination. :-)

It might be a useful exercise to map out where the traffic borderlines are 
with the two nodes currently reachable via IPv6.  I had forgotten that one 
of the IPv6 upstreams for my node is CANARIE, which then went off and get 
free IPv6 transit for itself and downstreams, so I only expected to get as 
far as the research networks.

The DNS-OARC presnetation from a couple of years ago about locating AS112 
nodes had a couple of slides that demonstrated odd paths and why having 
more AS112 nodes closer to their bad-boy sources is a bonus.

My point in advertising the IPv6 route was to see if:

a) anyone noticed (looks like they did not)
b) how far I could push the /48 into the current IPv6 Internet

I want to thank everyone for their feedback on the AS ditance the path 
travelled.  I'll be updating the as112.net web pages as well based on 
feedback on the format of one of the examples.

Aleksi:  I've had a chance to read "Subject: [as112-ops] Extensible AS112 
Service".  I've not used DNAME myself before so I can't comment on it 
except to say that it seems to be under re-consideration in DNSEXT at the 
IETF (rfc2672bis if I remember right...).

But that leads to another issue.  Joe Abley put it very well in a recent 
post to DNSOP that there lies an opportunity to clean up RFC 6304 
(yes, the two AS112 drafts are now RFCs as of last night) in terms of:

- utilizing the registry created by RFC 6303

- creating the mechanism that tells AS112 nodes/operators that the
   registry has been updated, therefore the nodes should/shall follow

- then there's the long-running question of junk TLDs, like .local.

Aleksi, could you please re-propose to DNSOP what you suggested on this 
mailing list to leverage the collective wisdom there to see if using DNAME 
is a viable solution?  Just refer to either my I-D or George's so they 
know what it's about.  The IETF meeting is just a couple of weeks from 
now.

All that to say that there may be either an rfc6304bis the may evolve from 
this as a new doc replacing the old one or just a simple update.

BTW, I added Stephane Bortzmeyer's excellent write-ups as links from 
http://as112.net/ - of course in French. :-)

Thanks,

wfms

From clement at cavadore.net  Thu Jul 14 18:50:03 2011
From: clement at cavadore.net (Clement Cavadore)
Date: Thu, 14 Jul 2011 20:50:03 +0200
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
Message-ID: <1310669403.1445.55.camel@puisard>

On Thu, 2011-07-14 at 14:33 -0400, William F. Maton wrote:
> Clement:  I don't think it's any harm, as it will be interesting to see to 
> which path the IPv6 traffic settles on for its destination. :-)

Great. Regarding the node we run @Hivane/34019, we are in the process of
connecting it directly to some parisian IXes. At the moment, we have
contacted FranceIX, Equinix-Paris, and Sfinx, and FranceIX accepted the
connexion.

> It might be a useful exercise to map out where the traffic borderlines are 
> with the two nodes currently reachable via IPv6.  I had forgotten that one 
> of the IPv6 upstreams for my node is CANARIE, which then went off and get 
> free IPv6 transit for itself and downstreams, so I only expected to get as 
> far as the research networks.

How do you think to proceed ? Using various lg/route-servers ?

> The DNS-OARC presnetation from a couple of years ago about locating AS112 
> nodes had a couple of slides that demonstrated odd paths and why having 
> more AS112 nodes closer to their bad-boy sources is a bonus.

It sure may be a bonus. However, routing seems to be weird. For example,
in Paris, we receive almost much traffic from... .kr ! :-)


Regards,

-- 
Cl?ment Cavadore
French Froggie


From nick at inex.ie  Thu Jul 14 18:50:08 2011
From: nick at inex.ie (Nick Hilliard)
Date: Thu, 14 Jul 2011 19:50:08 +0100
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
Message-ID: <4E1F3A60.4060106@inex.ie>

On 14/07/2011 19:33, William F. Maton wrote:
> - then there's the long-running question of junk TLDs, like .local.

I have quite a strong opinion that forward domains should not be hosted on
AS112 for security reasons.

Nick


From jvanoppen at spectrumnet.us  Thu Jul 14 18:52:36 2011
From: jvanoppen at spectrumnet.us (John van Oppen)
Date: Thu, 14 Jul 2011 18:52:36 +0000
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <4E1F3A60.4060106@inex.ie>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
	<4E1F3A60.4060106@inex.ie>
Message-ID: <AF24AE2D4A4D334FB9B667985E2AE763A9AF3E@mail1-sea.office.spectrumnet.us>

Nick - 

Whch sercurity reasons are you eluding to?    It seems most issues would also apply for the in-addr.arpa space as well.    


John

From nick at inex.ie  Thu Jul 14 18:59:53 2011
From: nick at inex.ie (Nick Hilliard)
Date: Thu, 14 Jul 2011 19:59:53 +0100
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <AF24AE2D4A4D334FB9B667985E2AE763A9AF3E@mail1-sea.office.spectrumnet.us>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
	<4E1F3A60.4060106@inex.ie>
	<AF24AE2D4A4D334FB9B667985E2AE763A9AF3E@mail1-sea.office.spectrumnet.us>
Message-ID: <4E1F3CA9.20908@inex.ie>

On 14/07/2011 19:52, John van Oppen wrote:
> Whch sercurity reasons are you eluding to?    It seems most issues would
> also apply for the in-addr.arpa space as well.

For the most part, people use ptr records in an advisory capacity only.
However, A/AAAA records are generally used for actual connection attempts.
 So if AS112 were to host .local / .lan / etc, that could be used to
redirect TCP connection attempts from lan boxes to machines of the AS112
operator's choice.  This is trivial to abuse.

Nick

From wmaton at ottix.net  Thu Jul 14 20:37:49 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 14 Jul 2011 16:37:49 -0400 (EDT)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <1310669403.1445.55.camel@puisard>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net> 
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
	<1310669403.1445.55.camel@puisard>
Message-ID: <Pine.LNX.4.64.1107141632290.24997@iskra.ottix.net>

On Thu, 14 Jul 2011, Clement Cavadore wrote:

> On Thu, 2011-07-14 at 14:33 -0400, William F. Maton wrote:
>> Clement:  I don't think it's any harm, as it will be interesting to see to
>> which path the IPv6 traffic settles on for its destination. :-)
>
> Great. Regarding the node we run @Hivane/34019, we are in the process of
> connecting it directly to some parisian IXes. At the moment, we have
> contacted FranceIX, Equinix-Paris, and Sfinx, and FranceIX accepted the
> connexion.

Good stuff!

>> It might be a useful exercise to map out where the traffic borderlines are
>> with the two nodes currently reachable via IPv6.  I had forgotten that one
>> of the IPv6 upstreams for my node is CANARIE, which then went off and get
>> free IPv6 transit for itself and downstreams, so I only expected to get as
>> far as the research networks.
>
> How do you think to proceed ? Using various lg/route-servers ?

I've gotten to the point that I'm too lazy to go look these up through 
route-views.  So now I'm writing a program that will go off and fetch 
those, ostensibly to help update the official list.  The data it pulls 
could be used to make a limited view of the public AS112 landscape.

>> The DNS-OARC presnetation from a couple of years ago about locating AS112
>> nodes had a couple of slides that demonstrated odd paths and why having
>> more AS112 nodes closer to their bad-boy sources is a bonus.
>
> It sure may be a bonus. However, routing seems to be weird. For example,
> in Paris, we receive almost much traffic from... .kr ! :-)

That's not a good thing.  I suspect - no, I know that if we get an 
actual IPv6 delegation between our two servers, some of those lookups are 
bound to take IPv6 tunnels (I remember the state of IPv6 connectivity an 
.kr) and the whole thing just goes down-hill after that....

I'm wondering if there isn't some way to satisfy the theoretical with 
doing a practical, limited-time trial and having just one IPv6 .arpa 
subnet delegated at us to confirm this?

wfms

From wmaton at ottix.net  Thu Jul 14 20:41:55 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 14 Jul 2011 16:41:55 -0400 (EDT)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <4E1F3CA9.20908@inex.ie>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
	<4E1F3A60.4060106@inex.ie>
	<AF24AE2D4A4D334FB9B667985E2AE763A9AF3E@mail1-sea.office.spectrumnet.us>
	<4E1F3CA9.20908@inex.ie>
Message-ID: <Pine.LNX.4.64.1107141640290.24997@iskra.ottix.net>

On Thu, 14 Jul 2011, Nick Hilliard wrote:

> On 14/07/2011 19:52, John van Oppen wrote:
>> Whch sercurity reasons are you eluding to?    It seems most issues would
>> also apply for the in-addr.arpa space as well.
>
> For the most part, people use ptr records in an advisory capacity only.
> However, A/AAAA records are generally used for actual connection attempts.
> So if AS112 were to host .local / .lan / etc, that could be used to
> redirect TCP connection attempts from lan boxes to machines of the AS112
> operator's choice.  This is trivial to abuse.

For that reason and for the politics involving the zones in question, I'm 
favouring that those continue to be dealt with in a separate document.  I 
was contemplating doing that in -cull but I decided that subject needed 
further reflection on its own.

wfms

From chris at in-berlin.de  Thu Jul 14 20:47:07 2011
From: chris at in-berlin.de (Christian Seitz)
Date: Thu, 14 Jul 2011 22:47:07 +0200 (CEST)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
Message-ID: <Pine.LNX.4.64.1107142233350.14278@tigger.berli.net>

Hello,

On Mon, 4 Jul 2011, William F. Maton wrote:

> 	Good news:  The DNS-OARC has acquired an IPv6 network block for the 
> use of AS112 nodes to anycast with, as a counterpart to its IPv4 version. 
> Now, before people go crazy, there are some considerations to take into 
> account:
[...]
> Speaking of trying things out, the IPv6 netblock is 2620:4f:8000::0/48 
> and I would be very interested if any of the fellow advanced academic 
> and research networks that happen to have IPv6 connectivity can see this 
> route.

I have also configured our local node in Berlin, Germany to be 
authoritative for the listed IPv6 zones and started to announce the 
netblock. Our AS112 node is behind AS29670.

Some month or even years ago I sent an email to get listed on 
http://public.as112.net/node/10, but the node is still not listed there.

Who			Individual Network Berlin e.V.
Where			Berlin, Germany
Unicast Adresses	192.109.42.100, 2001:67c:1400:1200::1
Transit AS		29670

Regards, Chris
-- 
Individual Network Berlin e.V. : support at in-berlin.de : vorstand at in-berlin.de
Tel +49-30-45494343 ::: Fax +49-30-45494344 :::: Web http://www.in-berlin.de/
IN-Berlin e.V. : Christian Seitz (1. Vors.) : Lehrter Str. 53 :: 10557 Berlin
Amtsgericht Charlottenburg 95 - VR 15669 Nz ::::::: USt.Ident-Nr. DE188894648

From wmaton at ottix.net  Thu Jul 14 21:21:50 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 14 Jul 2011 17:21:50 -0400 (EDT)
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: <Pine.LNX.4.64.1107142233350.14278@tigger.berli.net>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<Pine.LNX.4.64.1107142233350.14278@tigger.berli.net>
Message-ID: <Pine.LNX.4.64.1107141720540.24997@iskra.ottix.net>


On Thu, 14 Jul 2011, Christian Seitz wrote:

> I have also configured our local node in Berlin, Germany to be authoritative 
> for the listed IPv6 zones and started to announce the netblock. Our AS112 
> node is behind AS29670.

When it rains it pours. :-)

> Some month or even years ago I sent an email to get listed on 
> http://public.as112.net/node/10, but the node is still not listed there.

Consider it fixed - but, do you have a link to any statistics you gather 
for your node?

wfms

From wmaton at ottix.net  Thu Jul 14 21:25:32 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 14 Jul 2011 17:25:32 -0400 (EDT)
Subject: [as112-ops] aleksi, you're email is bouncing
Message-ID: <Pine.LNX.4.64.1107141725210.24997@iskra.ottix.net>



wfms

From vixie at isc.org  Fri Jul 15 20:35:52 2011
From: vixie at isc.org (Paul Vixie)
Date: Fri, 15 Jul 2011 20:35:52 +0000
Subject: [as112-ops] IPv6 network block for AS112 and experiments
In-Reply-To: Your message of "Thu, 14 Jul 2011 19:50:08 +0100."
	<4E1F3A60.4060106@inex.ie>
References: <Pine.LNX.4.64.1107042039450.21250@iskra.ottix.net>
	<1309888674.30876.15.camel@puisard>
	<Pine.LNX.4.64.1107141409450.24997@iskra.ottix.net>
	<4E1F3A60.4060106@inex.ie>
Message-ID: <99437.1310762152@nsa.vix.com>

> Date: Thu, 14 Jul 2011 19:50:08 +0100
> From: Nick Hilliard <nick at inex.ie>
> 
> I have quite a strong opinion that forward domains should not be hosted on
> AS112 for security reasons.

strong +1.

From ask at develooper.com  Mon Jul 18 16:21:38 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Mon, 18 Jul 2011 09:21:38 -0700
Subject: [as112-ops] Routing Assets / LOA for AS112
Message-ID: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>

Hi everyone,

For the IPv4 AS112 we just announce it to whoever listens; which I think is mostly just our peering connections.  I didn't actually check if our transit providers took the announcements; they all had excellent AS112 coverage anyway.

For the upcoming IPv6 AS112 I wanted to see if the transit providers would take the announcement.  One yesterday just did with a reference to the AS112 website.  Another this morning asked for an RADB entry or a LOA.  Did anyone else run into this?

I think I can clue them into having http://public.as112.net/ substitute for an LOA, but automated filter generators really want data from RADB.


 - ask

-- 
http://develooper.com/ - http://askask.com/

From md at Linux.IT  Mon Jul 18 16:25:32 2011
From: md at Linux.IT (Marco d'Itri)
Date: Mon, 18 Jul 2011 18:25:32 +0200
Subject: [as112-ops] Routing Assets / LOA for AS112
In-Reply-To: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
References: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
Message-ID: <20110718162532.GA30916@bongo.bofh.it>

On Jul 18, Ask Bj?rn Hansen <ask at develooper.com> wrote:

> For the upcoming IPv6 AS112 I wanted to see if the transit providers would take the announcement.  One yesterday just did with a reference to the AS112 website.  Another this morning asked for an RADB entry or a LOA.  Did anyone else run into this?

I have already asked Netnod (who controls the AS112 object in the RIPE
IRR) to create a route6 object for the IPv6 network, but this is still
pending because the person who deals with this is away.

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20110718/d2a3440e/attachment.pgp>

From jabley at hopcount.ca  Mon Jul 18 16:27:41 2011
From: jabley at hopcount.ca (Joe Abley)
Date: Mon, 18 Jul 2011 12:27:41 -0400
Subject: [as112-ops] Routing Assets / LOA for AS112
In-Reply-To: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
References: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
Message-ID: <32F2F89E-50DC-4014-826A-2810915D8028@hopcount.ca>


On 2011-07-18, at 12:21, Ask Bj?rn Hansen wrote:

> Hi everyone,
> 
> For the IPv4 AS112 we just announce it to whoever listens; which I think is mostly just our peering connections.  I didn't actually check if our transit providers took the announcements; they all had excellent AS112 coverage anyway.
> 
> For the upcoming IPv6 AS112 I wanted to see if the transit providers would take the announcement.  One yesterday just did with a reference to the AS112 website.  Another this morning asked for an RADB entry or a LOA.  Did anyone else run into this?

Yes, frequently.

Once upon a time I suggested writing an LOA in the form of an RFC which people could refer to. With hindsight, it might have been nice to include such a thing as an appendix to RFC6304.

In the mean time perhaps we could arrange for Autonomica to write us up a nice LOA which people could download from the as112 web page. (Autonomica, since the 192.175.48.0/24 route object in the RIPE db is maintained by NETNOD-MNT right now.)

> I think I can clue them into having http://public.as112.net/ substitute for an LOA, but automated filter generators really want data from RADB.

Liman has been happy to add things to the AS112 aut-num in the past when asked. Maybe just ask him?

aut-num:        AS112
as-name:        ROOTSERV
descr:          Root Server Technical Operations Assn
descr:          See: http://www.as112.net/
descr:          $Id: aut-num:AS112,v 1.7 2010-05-20 12:24:16 nico Exp $
import:         from AS3277 action pref=100; accept ANY
import:         from AS3292 action pref=100; accept ANY
import:         from AS8763 action pref=100; accept ANY
import:         from AS8674 action pref=100; accept ANY
import:         from AS12041 action pref=100; accept ANY
import:         from AS12779 action pref=100; accept ANY
import:         from AS15431 action pref=100; accept ANY
import:         from AS16150 action pref=100; accept ANY
import:         from AS26299 action pref=100; accept ANY
import:         from AS23518 action pref=100; accept ANY
export:         to AS3277 announce AS112
export:         to AS3292 announce AS112
export:         to AS8763 announce AS112
export:         to AS8674 announce AS112
export:         to AS12041 announce AS112
export:         to AS12779 announce AS112
export:         to AS15431 announce AS112
export:         to AS16150 announce AS112
export:         to AS23518 announce AS112
export:         to AS26299 announce AS112
admin-c:        NAC16-RIPE
tech-c:         NTC6-RIPE
mnt-by:         NETNOD-MNT
source:         RIPE # Filtered


Joe


From ask at develooper.com  Tue Jul 19 17:45:54 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Tue, 19 Jul 2011 10:45:54 -0700
Subject: [as112-ops] Routing Assets / LOA for AS112
In-Reply-To: <32F2F89E-50DC-4014-826A-2810915D8028@hopcount.ca>
References: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
	<32F2F89E-50DC-4014-826A-2810915D8028@hopcount.ca>
Message-ID: <7F3DB130-8A2F-4481-B828-CC4A4F9667FE@develooper.com>


On Jul 18, 2011, at 9:27, Joe Abley wrote:

>> I think I can clue them into having http://public.as112.net/substitute for an LOA, but automated filter generators really want data from RADB.
> 
> Liman has been happy to add things to the AS112 aut-num in the past when asked. Maybe just ask him?

I'll do that.   It seemed like that might be impolite, so I wanted to check here first.  Thanks!  :-)

By the way, according  to `peval` there's a route6 object for AS112 now:

$ peval 'afi ipv6, ipv4 (AS112)'
({192.175.48.0/24}) OR ({2620:4F:8000::/48})



 - ask

-- 
http://develooper.com/ - http://askask.com/



From wmaton at ottix.net  Wed Jul 20 20:25:04 2011
From: wmaton at ottix.net (William F. Maton)
Date: Wed, 20 Jul 2011 16:25:04 -0400 (EDT)
Subject: [as112-ops] Routing Assets / LOA for AS112
In-Reply-To: <7F3DB130-8A2F-4481-B828-CC4A4F9667FE@develooper.com>
References: <0BFD3DAD-7997-4267-825B-2C1339D525B3@develooper.com>
	<32F2F89E-50DC-4014-826A-2810915D8028@hopcount.ca>
	<7F3DB130-8A2F-4481-B828-CC4A4F9667FE@develooper.com>
Message-ID: <Pine.LNX.4.64.1107201619440.16192@iskra.ottix.net>

On Tue, 19 Jul 2011, Ask Bj?rn Hansen wrote:

> On Jul 18, 2011, at 9:27, Joe Abley wrote:
>
>>> I think I can clue them into having http://public.as112.net/substitute for an LOA, but automated filter generators really want data from RADB.
>>
>> Liman has been happy to add things to the AS112 aut-num in the past when asked. Maybe just ask him?
>
> I'll do that.   It seemed like that might be impolite, so I wanted to check here first.  Thanks!  :-)

Sounds good and thanks.

> By the way, according  to `peval` there's a route6 object for AS112 now:
>
> $ peval 'afi ipv6, ipv4 (AS112)'
> ({192.175.48.0/24}) OR ({2620:4F:8000::/48})

peval?!  Is that still around? ;-)

Yes, I inserted a route6 object a while ago into a local IRR which gets 
mirrored by the RADB.

As regards to the LOA, I think since DNS-OARC holds the paperwork for the 
prefixes, they should create one for both and I can post it for people to 
point at or download.  Now I just have to figure out how to teach that 
drupal thing to accept uploads...

wfms

From nick at inex.ie  Thu Jul 21 15:09:49 2011
From: nick at inex.ie (Nick Hilliard)
Date: Thu, 21 Jul 2011 16:09:49 +0100
Subject: [as112-ops] Extensible AS112 Service
In-Reply-To: <4DEC4F4E.50404@trex.fi>
References: <Pine.LNX.4.64.1105130857170.16420@iskra.ottix.net>
	<4DEC4F4E.50404@trex.fi>
Message-ID: <4E28413D.7090303@inex.ie>

On 06/06/2011 04:53, Aleksi Suhonen wrote:
> We'd have the following DNAME records:
> 
> 168.192.in-addr.arpa.  IN DNAME   168.192.in-addr.arpa.empty.as112.net.
> 10.in-addr.arpa.       IN DNAME   10.in-addr.arpa.empty.as112.net.
> ... and so on ...
[...]
> If I've understood correctly, this would make efforts to add DNSSEC to
> AS112 a whole lot simpler too, because there would only be one DNSSEC
> delegation path. The DNAMEs would only exist - and be signed at - the upper
> level zone. As opposed to: Each zone delegated with normal NS records would
> have its own DNSSEC sign path.
[...]
> How does this sound?

In theory, great.  The problem is that in theory, theory and practice ought
to be the same, but in practice they usually aren't.

My (cursory) reading of draft-ietf-dnsext-rfc2672bis-dname indicates that
DNSSEC wouldn't actually work in the way that you're expecting it to.  I
don't view this as a critical problem.

Also, while DNAME is standards track, it's never been used in anger before.
 So while it would certainly seem to fix some problems associated with the
operation of AS112, we have no telemetry to indicate how well or badly it
would work.  If we were to use it for AS112, it would certainly be very
interesting and would likely shake out a whole pile of implementation
problems (which has a lot of merit from the point of view of protocol
development), I would question whether this would be an appropriate first
large-scale production use of DNAMEs.

Nick


From wmaton at ottix.net  Thu Jul 21 15:33:19 2011
From: wmaton at ottix.net (William F. Maton)
Date: Thu, 21 Jul 2011 11:33:19 -0400 (EDT)
Subject: [as112-ops] Extensible AS112 Service
In-Reply-To: <4E28413D.7090303@inex.ie>
References: <Pine.LNX.4.64.1105130857170.16420@iskra.ottix.net>
	<4DEC4F4E.50404@trex.fi> <4E28413D.7090303@inex.ie>
Message-ID: <Pine.LNX.4.64.1107211129530.16192@iskra.ottix.net>

On Thu, 21 Jul 2011, Nick Hilliard wrote:

> On 06/06/2011 04:53, Aleksi Suhonen wrote:
>> We'd have the following DNAME records:
>>
>> 168.192.in-addr.arpa.  IN DNAME   168.192.in-addr.arpa.empty.as112.net.
>> 10.in-addr.arpa.       IN DNAME   10.in-addr.arpa.empty.as112.net.
>> ... and so on ...
> [...]
>> If I've understood correctly, this would make efforts to add DNSSEC to
>> AS112 a whole lot simpler too, because there would only be one DNSSEC
>> delegation path. The DNAMEs would only exist - and be signed at - the upper
>> level zone. As opposed to: Each zone delegated with normal NS records would
>> have its own DNSSEC sign path.
> [...]
>> How does this sound?
>
> In theory, great.  The problem is that in theory, theory and practice ought
> to be the same, but in practice they usually aren't.
>
> My (cursory) reading of draft-ietf-dnsext-rfc2672bis-dname indicates that
> DNSSEC wouldn't actually work in the way that you're expecting it to.  I
> don't view this as a critical problem.

My little grey cells started to dance when I re-read this bit, which 
was then excited more when I started to think about DNAME and IPv6 in 
the reverse zone....and I couldn't quite come up why.  Anyways, to 
complete the tangent, I came across RFC 3363, and section 4:

4.  DNAME in IPv6 Reverse Tree

    The issues for DNAME in the reverse mapping tree appears to be
    closely tied to the need to use fragmented A6 in the main tree: if
    one is necessary, so is the other, and if one isn't necessary, the
    other isn't either.  Therefore, in moving RFC 2874 to experimental,
    the intent of this document is that use of DNAME RRs in the reverse
    tree be deprecated.

Of course this is an Informational RFC.

> Also, while DNAME is standards track, it's never been used in anger before.
> So while it would certainly seem to fix some problems associated with the
> operation of AS112, we have no telemetry to indicate how well or badly it
> would work.  If we were to use it for AS112, it would certainly be very
> interesting and would likely shake out a whole pile of implementation
> problems (which has a lot of merit from the point of view of protocol
> development), I would question whether this would be an appropriate first
> large-scale production use of DNAMEs.

+1

wfms

From wmaton at ottix.net  Tue Jul 26 18:00:11 2011
From: wmaton at ottix.net (William F. Maton)
Date: Tue, 26 Jul 2011 14:00:11 -0400 (EDT)
Subject: [as112-ops] IETF DNSOP participation request
Message-ID: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>


All,
 	Hopefully I am being accurate in my rendreing of notes related to 
the discussions over AS112 drafts in the IETF DNSOP woring group that just 
took place a few minutes ago.

 	The DNSOP working group co-chairs would like to solicit 
participation from AS112 operators, considering topics such as what to do 
with lameness, how to get all AS112 operators to stick to IANA 
instructions related to delegation of new zones, etc.

 	I suppose the best thing for operators to do is to subscribe to 
the DNSOP mailing list (see http://tools.ietf.org/wg/dnsop/charters) and 
comment on both AS112 drafts presently under consideration for working 
group adoption.

 	The idea I have proposed is to split my draft into 2:  One that is 
simply an instruction to IANA like the AS112 IPv6 draft is, and the other 
for discussing delegation mechanisms like DNAME, obervations on lameness, 
other zones for delegation, etc.

Thanks,

wfms

From warren at kumari.net  Tue Jul 26 18:18:21 2011
From: warren at kumari.net (Warren Kumari)
Date: Tue, 26 Jul 2011 14:18:21 -0400
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
Message-ID: <01018FF7-D03F-49B9-93B0-6440EE6A491A@kumari.net>


On Jul 26, 2011, at 2:00 PM, William F. Maton wrote:

> 
> All,
> 	Hopefully I am being accurate in my rendreing of notes related to the discussions over AS112 drafts in the IETF DNSOP woring group that just took place a few minutes ago.
> 
> 	The DNSOP working group co-chairs would like to solicit participation from AS112 operators, considering topics such as what to do with lameness, how to get all AS112 operators to stick to IANA instructions related to delegation of new zones, etc.

As asked in the dnssop meeting, couldn't much of the "lameness, how to get all AS112 operators to stick to IANA instructions related to delegation of new zones, etc." issues be address by simply making AS112 be omniscient? As decisions to have AS112 answer /not answer for zones get made, delegations can simply be added and removed. 

Obviously this would require synthesizing answers[0], and not having manually configured zones (and not having the servers be recursive as they would then answer incorrectly for non-delegated space and?)

This was specifically not asked on the dnsop list as I want to know what ops thought first?.

W

[0]: Yes, yes i *did* feel dirty writing that?.
> 
> 	I suppose the best thing for operators to do is to subscribe to the DNSOP mailing list (see http://tools.ietf.org/wg/dnsop/charters) and comment on both AS112 drafts presently under consideration for working group adoption.
> 
> 	The idea I have proposed is to split my draft into 2:  One that is simply an instruction to IANA like the AS112 IPv6 draft is, and the other for discussing delegation mechanisms like DNAME, obervations on lameness, other zones for delegation, etc.
> 
> Thanks,
> 
> wfms
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
> 


From wmaton at ottix.net  Tue Jul 26 18:31:54 2011
From: wmaton at ottix.net (William F. Maton)
Date: Tue, 26 Jul 2011 14:31:54 -0400 (EDT)
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <01018FF7-D03F-49B9-93B0-6440EE6A491A@kumari.net>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<01018FF7-D03F-49B9-93B0-6440EE6A491A@kumari.net>
Message-ID: <Pine.LNX.4.64.1107261426520.16192@iskra.ottix.net>

On Tue, 26 Jul 2011, Warren Kumari wrote:

> As asked in the dnssop meeting, couldn't much of the "lameness, how to 
>get all AS112 operators to stick to IANA instructions related to 
>delegation of new zones, etc." issues be address by simply making AS112 
>be omniscient? As decisions to have AS112 answer /not answer for zones 
>get made, delegations can simply be added and removed.

So this is such a radically simple idea on the surface, it's hard not to 
like it.

On the otherhand, it would be interesting to see if done, how much more 
load would suddenly be shifted to AS112 nodes by default.  (I still 
believe there are 6bone nodes out there asking for resolution of 3ffe::/16 
addresses.)

What do as112-operators here think?

> Obviously this would require synthesizing answers[0], and not having 
>manually configured zones (and not having the servers be recursive as 
>they would then answer incorrectly for non-delegated space and?)
>
> This was specifically not asked on the dnsop list as I want to know 
>what ops thought first?.
>
> W
>
> [0]: Yes, yes i *did* feel dirty writing that?.
>>
>> 	I suppose the best thing for operators to do is to subscribe to the DNSOP mailing list (see http://tools.ietf.org/wg/dnsop/charters) and comment on both AS112 drafts presently under consideration for working group adoption.
>>
>> 	The idea I have proposed is to split my draft into 2:  One that is simply an instruction to IANA like the AS112 IPv6 draft is, and the other for discussing delegation mechanisms like DNAME, obervations on lameness, other zones for delegation, etc.
>>
>> Thanks,
>>
>> wfms
>> _______________________________________________
>> as112-ops mailing list
>> as112-ops at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>>
>
>

wfms

From pk at DENIC.DE  Tue Jul 26 20:15:16 2011
From: pk at DENIC.DE (Peter Koch)
Date: Tue, 26 Jul 2011 22:15:16 +0200
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
Message-ID: <20110726201516.GJ6394@x27.adm.denic.de>

On Tue, Jul 26, 2011 at 02:00:11PM -0400, William F. Maton wrote:

> 	The DNSOP working group co-chairs would like to solicit 
> participation from AS112 operators, considering topics such as what to do 
> with lameness, how to get all AS112 operators to stick to IANA 
> instructions related to delegation of new zones, etc.
> 
> 	I suppose the best thing for operators to do is to subscribe to 
> the DNSOP mailing list (see http://tools.ietf.org/wg/dnsop/charters) and 
> comment on both AS112 drafts presently under consideration for working 
> group adoption.

the point is that we (==dnsop) want the discussion to be in one place and need
it to be under IETF list regime, thus on dnsop at ietf.org.

Among the questions to be answered there is how AS112 operators (those on any of the
lists and those not) can implement any change to the list of served zones.

-Peter

From wmaton at ottix.net  Tue Jul 26 22:03:31 2011
From: wmaton at ottix.net (William F. Maton)
Date: Tue, 26 Jul 2011 18:03:31 -0400 (EDT)
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <20110726201516.GJ6394@x27.adm.denic.de>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<20110726201516.GJ6394@x27.adm.denic.de>
Message-ID: <Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>

On Tue, 26 Jul 2011, Peter Koch wrote:

> the point is that we (==dnsop) want the discussion to be in one place and need
> it to be under IETF list regime, thus on dnsop at ietf.org.
>
> Among the questions to be answered there is how AS112 operators (those on any of the
> lists and those not) can implement any change to the list of served zones.

Peter - thanks for clarifying.

AS112 operators, please speak up on dnsop.

wfms

From vixie at isc.org  Tue Jul 26 22:26:09 2011
From: vixie at isc.org (Paul Vixie)
Date: Tue, 26 Jul 2011 22:26:09 +0000
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: Your message of "Tue, 26 Jul 2011 14:31:54 -0400."
	<Pine.LNX.4.64.1107261426520.16192@iskra.ottix.net>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<01018FF7-D03F-49B9-93B0-6440EE6A491A@kumari.net>
	<Pine.LNX.4.64.1107261426520.16192@iskra.ottix.net>
Message-ID: <20058.1311719169@nsa.vix.com>

> Date: Tue, 26 Jul 2011 14:31:54 -0400 (EDT)
> From: "William F. Maton" <wmaton at ottix.net>
> 
> What do as112-operators here think?

i'd be comfortable with the omniscience approach.

From md at Linux.IT  Tue Jul 26 22:16:36 2011
From: md at Linux.IT (Marco d'Itri)
Date: Wed, 27 Jul 2011 00:16:36 +0200
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<20110726201516.GJ6394@x27.adm.denic.de>
	<Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>
Message-ID: <20110726221636.GA14071@bongo.bofh.it>

On Jul 27, "William F. Maton" <wmaton at ottix.net> wrote:

> AS112 operators, please speak up on dnsop.
FWIW, I have already configured the zones and will start announcing the
v6 network in a few days.

-- 
ciao,
Marco

From as112-ops at trex.fi  Wed Jul 27 04:58:30 2011
From: as112-ops at trex.fi (Aleksi Suhonen)
Date: Wed, 27 Jul 2011 07:58:30 +0300
Subject: [as112-ops] Extensible AS112 Service
In-Reply-To: <4E28413D.7090303@inex.ie>
References: <Pine.LNX.4.64.1105130857170.16420@iskra.ottix.net>	<4DEC4F4E.50404@trex.fi>
	<4E28413D.7090303@inex.ie>
Message-ID: <4E2F9AF6.9030308@trex.fi>

On 07/21/11 18:09, Nick Hilliard wrote:
> Also, while DNAME is standards track, it's never been used in anger before.
>   So while it would certainly seem to fix some problems associated with the
> operation of AS112, we have no telemetry to indicate how well or badly it
> would work.  If we were to use it for AS112, it would certainly be very
> interesting and would likely shake out a whole pile of implementation
> problems (which has a lot of merit from the point of view of protocol
> development), I would question whether this would be an appropriate first
> large-scale production use of DNAMEs.

I believe the new Chinese TLDs are already using DNAMEs to link the 
traditional charset zone and the simplified charset zone together. I 
understand that there are also other IDN TLDs out there that do 
something similar, but I don't have any pointers for those.

William F. Maton quoted RFC3363 and RFC2874. Those were doing something 
completely different and in a completely different way than what I was 
suggesting here. They aren't even compatible with the current ip6.arpa 
zone and they are irrelevant to this discussion.

However, Marco D'Itri pointed out that the default lifetimes for the 
CNAMEs generated by DNAMEs are very short. This means that the DNAMEs I 
suggested wouldn't deflect the load from the reverse root servers very 
efficiently, unless they started giving longer lifetimes to DNAME and 
CNAME records. This would probably require changing running code on 
crucial infrastructure.

-- 
	+358 4567 02048 / http://www.trex.fi/
	Aleksi Suhonen / TREX  Tampere Region Exchange Oy

From ask at develooper.com  Wed Jul 27 03:47:45 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Tue, 26 Jul 2011 23:47:45 -0400
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <20110726221636.GA14071@bongo.bofh.it>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<20110726201516.GJ6394@x27.adm.denic.de>
	<Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>
	<20110726221636.GA14071@bongo.bofh.it>
Message-ID: <D31AC6E9-BC71-4D64-8435-89725A620438@develooper.com>


On Jul 26, 2011, at 18:16, Marco d'Itri wrote:

>> AS112 operators, please speak up on dnsop.
> FWIW, I have already configured the zones and will start announcing the
> v6 network in a few days.

I did the same over the last week or two (from AS53582).  If you are in North America you might get our node with:

   dig +short -t txt hostname.as112.net  @2620:4f:8000::42


 - ask

-- 
http://develooper.com/ - http://askask.com/



From md at Linux.IT  Wed Jul 27 14:14:21 2011
From: md at Linux.IT (Marco d'Itri)
Date: Wed, 27 Jul 2011 16:14:21 +0200
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <D31AC6E9-BC71-4D64-8435-89725A620438@develooper.com>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<20110726201516.GJ6394@x27.adm.denic.de>
	<Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>
	<20110726221636.GA14071@bongo.bofh.it>
	<D31AC6E9-BC71-4D64-8435-89725A620438@develooper.com>
Message-ID: <20110727141421.GA5798@bongo.bofh.it>

On Jul 27, Ask Bj?rn Hansen <ask at develooper.com> wrote:

> I did the same over the last week or two (from AS53582).  If you are in North America you might get our node with:
> 
>    dig +short -t txt hostname.as112.net  @2620:4f:8000::42

I am receiving this route, but the IP is not replying to pings or DNS
queries (source: attila.bofh.it).

-- 
ciao,
Marco

From ask at develooper.com  Wed Jul 27 15:19:24 2011
From: ask at develooper.com (=?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?=)
Date: Wed, 27 Jul 2011 11:19:24 -0400
Subject: [as112-ops] IETF DNSOP participation request
In-Reply-To: <20110727141421.GA5798@bongo.bofh.it>
References: <Pine.LNX.4.64.1107261348370.16192@iskra.ottix.net>
	<20110726201516.GJ6394@x27.adm.denic.de>
	<Pine.LNX.4.64.1107261803000.16192@iskra.ottix.net>
	<20110726221636.GA14071@bongo.bofh.it>
	<D31AC6E9-BC71-4D64-8435-89725A620438@develooper.com>
	<20110727141421.GA5798@bongo.bofh.it>
Message-ID: <6192E725-B415-4E1D-9234-51ABF50E74B4@develooper.com>


On Jul 27, 2011, at 10:14, Marco d'Itri wrote:

>> I did the same over the last week or two (from AS53582).  If you are in North America you might get our node with:
>> 
>>   dig +short -t txt hostname.as112.net  @2620:4f:8000::42
> 
> I am receiving this route, but the IP is not replying to pings or DNS
> queries (source: attila.bofh.it).

Thanks; it should be better now.   25% of our IPv6 traffic went through a router that didn't always know what to do with it; grrh.

One of the frustrating things deploying IPv6 is that most of the external (outsourced) monitoring we use isn't working for IPv6 (yet).


 - ask

-- 
http://develooper.com/ - http://askask.com/



