Date: Sun, 26 Jul 2009 20:48:06 -0500
Subject: AT&T. Layer 6-8 needed.
All,
It appears at AT&T (including DSL, and my own home service via u-verse)
has unilaterally and without explanation started blocking websites.
I have confirmed this with multiple tests. (It actually appears that
these sites are being blocked at a local-global scale -- that is, each
city/hub seems to have blackholes for the sites).
The sites I know of I'll list below (see Reddit for a discussion), but
this is clearly and absolutely unacceptable. Please, comments on the nature
of the sites are OT.. Let's keep this thread that way. (Away from being OT,
that is).
If any T folk are around, and have gotten wind of this (all comments /
direct emails will be off record), a reply would be appreciated.
No ears enclosing clue will be reached via normal channels at ~950E on a
Sunday, but this is clearly a problem needing addressing, resolution, action
and, who knows - suit?
Thanks in advance all for insight, comments,
-jamie
AT&Tが始めたWebサイトブロックについて、情報を集っています。
続々と情報が寄せられている模様。。。
7/27/2009
6/16/2009
RIPE-ncc-service-wg@June 15, 2009
Date: Mon, 15 Jun 2009 16:33:36 +0200
Subject: [ncc-services-wg] New emergency RIPE NCC PGP Key
[Apologies for duplicate emails]
Dear Colleagues,
On Monday, 15 June 2009, a hardware failure caused us to lose access to
the RIPE NCC PGP secret key, which signs email from our ticketing system.
We performed an emergency key rollover to rectify this problem.
Details on key-management policy can be found on our website at:
https://www.ripe.net/rs/pgp/index.html
If you have any comments or questions about this, please contact
.
Kind Regards,
Brian Riddle
RIPE NCC
ハードウェア障害でPGP秘密鍵を失ったということで、緊急で新しい鍵が出ています。
セキュリティを向上させる為に色々なアーキテクチャがありますが、ハードウェア障害には
弱いですね。現場での迅速な対応に頭が下がります。
Subject: [ncc-services-wg] New emergency RIPE NCC PGP Key
[Apologies for duplicate emails]
Dear Colleagues,
On Monday, 15 June 2009, a hardware failure caused us to lose access to
the RIPE NCC PGP secret key, which signs email from our ticketing system.
We performed an emergency key rollover to rectify this problem.
Details on key-management policy can be found on our website at:
https://www.ripe.net/rs/pgp/index.html
If you have any comments or questions about this, please contact
Kind Regards,
Brian Riddle
RIPE NCC
ハードウェア障害でPGP秘密鍵を失ったということで、緊急で新しい鍵が出ています。
セキュリティを向上させる為に色々なアーキテクチャがありますが、ハードウェア障害には
弱いですね。現場での迅速な対応に頭が下がります。
5/30/2009
ARIN-announce@May 29, 2009
Date: Fri, 29 May 2009 11:23:58 -0400
Subject: [arin-announce] Policy Proposal: Open Access To IPv6
Please be advised that the following policy proposal has been
posted to the ARIN Public Policy Mailing List. All discussion of the
proposal must take place on the PPML.
Regards,
Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Policy Proposal Name: Open Access To IPv6
Proposal Originator: Stacy Hughes and Cathy Aronson
Proposal Version: 1.0
Date: 29 May 2009
Proposal type: modify
Policy term: permanent
Policy statement:
1) Remove "by advertising that connectivity through its single
aggregated address allocation" from article 3 of section 6.5.1.1
2) Remove article 4 of section 6.5.1.1, ?be an existing, known ISP in
the ARIN region or have a plan for making at least 200 end-site
assignments to other organizations within 5 years? in its entirety.
Rationale: It is acknowledged that these concepts have been put before
the community in the past. However, with the wisdom of actual
operational experience, the necessity of promoting IPv6 adoption
throughout our region, and emerging native v6 only network models, it
becomes obvious that these modifications to the NRPM are necessary.
Removing the 200 end site requirement enables smaller, but no less
important and viable, networks access to IPv6. Removing the ?known ISP?
requirement enfranchises new, native v6 businesses that can drive
innovation and expansion in the Internet industry, as well as other
industries. Removing the requirement for a single aggregate announcement
benefits the NRPM itself, as it has been decided by the community that
it should not contain routing advice.
Timetable for implementation: immediately upon BoT ratification
ARINでIPv6割当ての条件緩和の提案が出ました。
200ユーザ規則撤廃はいいとして、
経路分割はある程度制限掛けないとIPv6でも経路爆発が起きるかもしれないけど・・・
Subject: [arin-announce] Policy Proposal: Open Access To IPv6
Please be advised that the following policy proposal has been
posted to the ARIN Public Policy Mailing List. All discussion of the
proposal must take place on the PPML.
Regards,
Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Policy Proposal Name: Open Access To IPv6
Proposal Originator: Stacy Hughes and Cathy Aronson
Proposal Version: 1.0
Date: 29 May 2009
Proposal type: modify
Policy term: permanent
Policy statement:
1) Remove "by advertising that connectivity through its single
aggregated address allocation" from article 3 of section 6.5.1.1
2) Remove article 4 of section 6.5.1.1, ?be an existing, known ISP in
the ARIN region or have a plan for making at least 200 end-site
assignments to other organizations within 5 years? in its entirety.
Rationale: It is acknowledged that these concepts have been put before
the community in the past. However, with the wisdom of actual
operational experience, the necessity of promoting IPv6 adoption
throughout our region, and emerging native v6 only network models, it
becomes obvious that these modifications to the NRPM are necessary.
Removing the 200 end site requirement enables smaller, but no less
important and viable, networks access to IPv6. Removing the ?known ISP?
requirement enfranchises new, native v6 businesses that can drive
innovation and expansion in the Internet industry, as well as other
industries. Removing the requirement for a single aggregate announcement
benefits the NRPM itself, as it has been decided by the community that
it should not contain routing advice.
Timetable for implementation: immediately upon BoT ratification
ARINでIPv6割当ての条件緩和の提案が出ました。
200ユーザ規則撤廃はいいとして、
経路分割はある程度制限掛けないとIPv6でも経路爆発が起きるかもしれないけど・・・
5/28/2009
UKNOF@May 27, 2009
Date: Wed, 27 May 2009 18:36:08 -0400
Subject: [uknof] UKNOF13 Remote participation
Update is I'm pleased to say that the meeting connectivity and
webcasting were up and running as of the end of today.
For those of you coming in remotely, the webcast (via flash) will be
available on:
http://uknof.bogons.net/uknof13.html
And the meeting chatroom will be jabber on:
xmpp:uknof@conference.dns-oarc.net
also #uknof on irc.terahertz for IRC die-hards.
All slide decks that have been submitted are linked to from the meeting
web page. I'd appreciate the co-operation of those speakers who have
still to submit getting theirs to me ASAP so we can link to these too.
Planned start time is 10:00 BST.
A big thank you to Andy, Brandon, James, Tom and Will for their hard
work in getting all this set up in advance.
See you all tomorrow !
Keith
日本時間の明日夜から始まるUKNOF13のリモート参加に関するお知らせ。
チャンピオンズリーグが終わってほとぼり冷めたころっていうのが絶妙なスケジューリング！
Subject: [uknof] UKNOF13 Remote participation
Update is I'm pleased to say that the meeting connectivity and
webcasting were up and running as of the end of today.
For those of you coming in remotely, the webcast (via flash) will be
available on:
http://uknof.bogons.net/uknof13.html
And the meeting chatroom will be jabber on:
xmpp:uknof@conference.dns-oarc.net
also #uknof on irc.terahertz for IRC die-hards.
All slide decks that have been submitted are linked to from the meeting
web page. I'd appreciate the co-operation of those speakers who have
still to submit getting theirs to me ASAP so we can link to these too.
Planned start time is 10:00 BST.
A big thank you to Andy, Brandon, James, Tom and Will for their hard
work in getting all this set up in advance.
See you all tomorrow !
Keith
日本時間の明日夜から始まるUKNOF13のリモート参加に関するお知らせ。
チャンピオンズリーグが終わってほとぼり冷めたころっていうのが絶妙なスケジューリング！
5/26/2009
LACNIC-Anuncios@May 25, 2009
Date: Mon, 25 May 2009 11:14:48 -0300
From: Alexandra Dans
To: anuncios@lacnic.net
Subject: [LACNIC/Anuncios] LACNIC XII- DIA 1/DAY 1 TUTORIAL
Message-ID: <4A1AA7D8.9080406@lacnic.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
[Disculpen Duplicados]
[Apologies for Duplicates]
～ポルトガル語版、スペイン語版は省略～
----------------------------
This Monday May 25th , during the LACNIC XII annual meeting in Panama (-
5 UTC), two tutorials will be launched: from 9:00 am to 11:00 am the
tutorial: ?LACNIC Registration System? and from 2:15pm to 6:00 pm, the
tutorial: ?Interconnection and Peering?.
All of you interested in following the webcasting can access from:
http://lacnic.net/en/eventos/lacnicxii/participacion.html
It is also possible to participate in the discussions through electronic
messaging (Jabber/XMPP). You can find detailed information to access
this service at:
http://lacnic.net/en/eventos/lacnicxii/participacion.html
Please note that we have an email account, webcasting@lacnic.net
, in order to
receive your comments about the webcasting and messaging services
Kind Regards
LACNIC
ようやく春のポリシーミーティング最終戦。
激しい議論が期待できるかな？
From: Alexandra Dans
To: anuncios@lacnic.net
Subject: [LACNIC/Anuncios] LACNIC XII- DIA 1/DAY 1 TUTORIAL
Message-ID: <4A1AA7D8.9080406@lacnic.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
[Disculpen Duplicados]
[Apologies for Duplicates]
～ポルトガル語版、スペイン語版は省略～
----------------------------
This Monday May 25th , during the LACNIC XII annual meeting in Panama (-
5 UTC), two tutorials will be launched: from 9:00 am to 11:00 am the
tutorial: ?LACNIC Registration System? and from 2:15pm to 6:00 pm, the
tutorial: ?Interconnection and Peering?.
All of you interested in following the webcasting can access from:
http://lacnic.net/en/eventos/lacnicxii/participacion.html
It is also possible to participate in the discussions through electronic
messaging (Jabber/XMPP). You can find detailed information to access
this service at:
http://lacnic.net/en/eventos/lacnicxii/participacion.html
Please note that we have an email account, webcasting@lacnic.net
receive your comments about the webcasting and messaging services
Kind Regards
LACNIC
ようやく春のポリシーミーティング最終戦。
激しい議論が期待できるかな？
5/23/2009
APNIC-sig-policy@May 22, 2009
Date: Fri, 22 May 2009 15:39:36 +1000
Subject: [sig-policy] APNIC EC returns prop-050: IPv4 address
transfers to Policy SIG
-----------------------------------------------------------------------
APNIC EC returns "IPv4 address transfers" to Policy SIG
-----------------------------------------------------------------------
Dear colleagues
The APNIC EC (Executive Council), at its meeting on 21 May 2009,
returned prop-050, "IPv4 address transfers", to the Policy SIG for
further discussion. Minutes from this meeting will be available after
they have been adopted at the June 2009 EC meeting.
Below is the official notification from the EC:
This is a response to the Policy Development Manager from the
APNIC Executive Council.
The APNIC Policy SIG Chair formally requested the APNIC EC to
endorse Proposal-50 on the 20th May.
According to the APNIC Policy Development Process: "The EC, in
their capacity as representatives of the membership, will be asked
to endorse the consensus proposals arising from the OPM and the
SIG mailing lists for implementation at the next EC meeting. In
reviewing the proposals for implementation, the EC may refer
proposals back to the SIG for further discussion with clearly
stated reasons."
In its meeting of the 21st May the APNIC Executive Council has
decided to refer Proposal-50 back to the Policy SIG. The reason
for this referral is that the EC is not of the opinion that the
proposal has gathered a clear consensus in favour of the policy,
and the EC notes that the proposal, taken in isolation, has
engendered significant concerns within the community relating to
the adequacy of safeguards against potential abuse as a
consequence of implementation this policy.
regards,
Geoff Huston
Executive Secretary to the APNIC EC
for the APNIC EC
For a detailed history of the proposal, see:
Regards
IPv4アドレス移転ポリシーはAPNIC ECの会議で差し戻しに決定。
もう少し詳細な議論が必要でしたね。やはり。
Subject: [sig-policy] APNIC EC returns prop-050: IPv4 address
transfers to Policy SIG
-----------------------------------------------------------------------
APNIC EC returns "IPv4 address transfers" to Policy SIG
-----------------------------------------------------------------------
Dear colleagues
The APNIC EC (Executive Council), at its meeting on 21 May 2009,
returned prop-050, "IPv4 address transfers", to the Policy SIG for
further discussion. Minutes from this meeting will be available after
they have been adopted at the June 2009 EC meeting.
Below is the official notification from the EC:
This is a response to the Policy Development Manager from the
APNIC Executive Council.
The APNIC Policy SIG Chair formally requested the APNIC EC to
endorse Proposal-50 on the 20th May.
According to the APNIC Policy Development Process: "The EC, in
their capacity as representatives of the membership, will be asked
to endorse the consensus proposals arising from the OPM and the
SIG mailing lists for implementation at the next EC meeting. In
reviewing the proposals for implementation, the EC may refer
proposals back to the SIG for further discussion with clearly
stated reasons."
In its meeting of the 21st May the APNIC Executive Council has
decided to refer Proposal-50 back to the Policy SIG. The reason
for this referral is that the EC is not of the opinion that the
proposal has gathered a clear consensus in favour of the policy,
and the EC notes that the proposal, taken in isolation, has
engendered significant concerns within the community relating to
the adequacy of safeguards against potential abuse as a
consequence of implementation this policy.
regards,
Geoff Huston
Executive Secretary to the APNIC EC
for the APNIC EC
For a detailed history of the proposal, see:
Regards
IPv4アドレス移転ポリシーはAPNIC ECの会議で差し戻しに決定。
もう少し詳細な議論が必要でしたね。やはり。
5/21/2009
RIPE-ncc-services-wg@May 20, 2009
Date: Wed, 20 May 2009 14:33:15 +0200
Subject: [ncc-services-wg] Website Launch: www.IPv6ActNow.org
[Apologies for duplicate emails.]
Dear Colleagues,
The RIPE NCC is pleased to announce the launch of the IPv6 Act Now! website.
www.IPv6ActNow.org is a one stop website that explains IPv6 in terms
that everyone can understand and provides a variety of useful
information aimed at promoting the global adoption of IPv6.
The site is for anyone with an interest in IPv6, including network
engineers, company directors, law enforcement agencies, government
representatives and civil society.
The site content is regularly updated and includes:
- Education, advice and opinions from the experts
- Latest IPv6-related news stories
- Videos and articles from Internet community leaders
- Current IPv4 exhaustion and IPv6 uptake statistics
- The RIPE community's statement on IPv6 deployment, including a list
of organisations supporting this statement
- Information on community-developed IPv6 distribution policies
- Useful links to other sources of information about IPv6
- A forum for everyone to share experiences, ask questions and find
answers
The site also includes contributions from other Regional Internet
Registries (RIRs) and industry partners.
We invite you to take a look around the site. We hope that you find it
useful.
If you have and comments or suggestions about IPv6ActNow!, please
contact us at.
Regards,
Paul Rendek
Head of External Relations and Communication
RIPE NCC
RIPE NCCではIPv6への移行に関する情報を纏めた模様。
全く動向を追えていなかったエンジニアがキャッチアップするのにいいサイトかも。
Subject: [ncc-services-wg] Website Launch: www.IPv6ActNow.org
[Apologies for duplicate emails.]
Dear Colleagues,
The RIPE NCC is pleased to announce the launch of the IPv6 Act Now! website.
www.IPv6ActNow.org is a one stop website that explains IPv6 in terms
that everyone can understand and provides a variety of useful
information aimed at promoting the global adoption of IPv6.
The site is for anyone with an interest in IPv6, including network
engineers, company directors, law enforcement agencies, government
representatives and civil society.
The site content is regularly updated and includes:
- Education, advice and opinions from the experts
- Latest IPv6-related news stories
- Videos and articles from Internet community leaders
- Current IPv4 exhaustion and IPv6 uptake statistics
- The RIPE community's statement on IPv6 deployment, including a list
of organisations supporting this statement
- Information on community-developed IPv6 distribution policies
- Useful links to other sources of information about IPv6
- A forum for everyone to share experiences, ask questions and find
answers
The site also includes contributions from other Regional Internet
Registries (RIRs) and industry partners.
We invite you to take a look around the site. We hope that you find it
useful.
If you have and comments or suggestions about IPv6ActNow!, please
contact us at
Regards,
Paul Rendek
Head of External Relations and Communication
RIPE NCC
RIPE NCCではIPv6への移行に関する情報を纏めた模様。
全く動向を追えていなかったエンジニアがキャッチアップするのにいいサイトかも。
5/20/2009
AusNOG@May 19, 2009
date Tue, May 19, 2009 at 2:41 PM
subject [AusNOG] PPC1 landing
Cheers,
jsl
写真の添付のみっていうメールはメーリングリストでははじめて見たな(笑)
PPC-1の陸揚げの光景だと思うのですが。
subject [AusNOG] PPC1 landing
Cheers,
jsl
写真の添付のみっていうメールはメーリングリストでははじめて見たな(笑)
PPC-1の陸揚げの光景だと思うのですが。
5/19/2009
viops@May 18, 2009
date Mon, May 18, 2009 at 8:10 AM
subject [viops:245] Oracle Buys VirtualIron 13.May.2009
なんとなく忘れそうなのでメモ。
OracleがVirtualIronを買収
------------------------------------------------------------
http://www.oracle.com/virtualiron/index.html
On May 13, 2009, Oracle announced it has agreed to acquire
Virtual Iron Software, Inc. (Virtual Iron),
a provider of server virtualization management software.
The transaction is subject to customary closing conditions
and is expected to close this summer.
Until the deal closes, each company will continue to operate
independently.
------------------------------------------------------------
次はKVM(Kernel-base Virtual Machine)+QEMUあたりが、話題になる
可能性？
Unified I/O と Virtual Switch Consolidation(統合)が、
ちゃくちゃくと進んできている様子。
--
Naoto
オラクル、元気ですね。
景気がいいのか、底値で買えるチャンスと踏んだか・・・
#昔、拡大路線のキャリアは粉飾で自滅していきました・・・。オラクルは固定客がいるからキャリアとは違うでしょうが。
subject [viops:245] Oracle Buys VirtualIron 13.May.2009
なんとなく忘れそうなのでメモ。
OracleがVirtualIronを買収
------------------------------------------------------------
http://www.oracle.com/virtualiron/index.html
On May 13, 2009, Oracle announced it has agreed to acquire
Virtual Iron Software, Inc. (Virtual Iron),
a provider of server virtualization management software.
The transaction is subject to customary closing conditions
and is expected to close this summer.
Until the deal closes, each company will continue to operate
independently.
------------------------------------------------------------
次はKVM(Kernel-base Virtual Machine)+QEMUあたりが、話題になる
可能性？
Unified I/O と Virtual Switch Consolidation(統合)が、
ちゃくちゃくと進んできている様子。
--
Naoto
オラクル、元気ですね。
景気がいいのか、底値で買えるチャンスと踏んだか・・・
#昔、拡大路線のキャリアは粉飾で自滅していきました・・・。オラクルは固定客がいるからキャリアとは違うでしょうが。
denog@May 18, 2009
Date: Mon, 18 May 2009 09:06:13 +0200
Subject: Beering Köln
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Moin,
hat jemand von Euch Lust am Donnerstag um 19 Uhr ein DENOG-Beering/Futtern in
Köln zu machen?
Mr6Tux hat als Location das Tacoloco IV (http://www.tacoloco.de/) in Hürth
vorgeschlagen.
Wir sind jetzt schon zu viert. Wer noch dazu kommen will kann sich ja kurz hier
oder im IRC melden damit wir ggf. einen Tisch reservieren können.
Gruß
--Kay / frapzzt
-----BEGIN PGP SIGNATURE-----
久々にdenogだ！と思ったらBeeringEventのお誘いだった。
さすがドイツ人。
日本でもなぜかこの時期に日比谷で"オクトーバーフェスト"やってますね。
オクトーバー・・・
Subject: Beering Köln
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Moin,
hat jemand von Euch Lust am Donnerstag um 19 Uhr ein DENOG-Beering/Futtern in
Köln zu machen?
Mr6Tux hat als Location das Tacoloco IV (http://www.tacoloco.de/) in Hürth
vorgeschlagen.
Wir sind jetzt schon zu viert. Wer noch dazu kommen will kann sich ja kurz hier
oder im IRC melden damit wir ggf. einen Tisch reservieren können.
Gruß
--Kay / frapzzt
-----BEGIN PGP SIGNATURE-----
久々にdenogだ！と思ったらBeeringEventのお誘いだった。
さすがドイツ人。
日本でもなぜかこの時期に日比谷で"オクトーバーフェスト"やってますね。
オクトーバー・・・
5/17/2009
JANOG@May 16, 2009
date Sat, May 16, 2009 at 1:41 AM
subject [janog:08906] IPv6 Firewall
許です。
この間、IPv6のFirewallを書いててちょっと気がついたので、ここにも
書いておきます。
# きっかけは、某所のWebサービスが見られない場所があると言う話を
# 某所で聞いたことですが。
IPv6は、IPv4と違ってパケットをFragmentしません。その代わり、
Path-MTU Discoveryを行ってpacket sizeを決める（表現は微妙ですが）
わけですが、このPATH-MTU DiscoveryってICMPなんですよね。
というわけで、以下悲しいシナリオ。
1) IPv4では、今時、ICMPを全部たたき落とす設定がしばしば行われる
2) IPv4では、DF bitを立てていない限り、それでも問題なく通信できる。
一応、ICMP type UNREACH code NeedFragmentが帰ってくるので
Path-MTU Discoveryと同等の処理は出来るが、そこまでのFilterはあ
まり書かれていないと思う。
3) IPv6でもIPv4と同じようなPacket Filter Ruleを書いてしまう
4) 従って、Path-MTU Discoveryをたたき落としてしまう
5) そのせいで見られないWeb Pageが発生することがある
で、僕自身はipfwとかiptablesの実装を知らないので、それらの
filter ruleは書けませんが、OpenBSDに(NetBSD/FreeBSDにも)実装されて
いるpfのRuleは判った（つもりな）ので、一応メモ代わりに。
(NetBSD 5.0で試したつもり。転記ミスがあったらごめん)
pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type toobig
# これが問題になるって事は、下手をしたらNeighbor Discoveryも問題に
# なるってことかしらん？ってことで、Neighbor DiscoveryとRouter Solicitation
# さらに、Who-Are-Youに関する部分も一応。
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {routersol, routeradv}
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {neighbrsol, neighbradv}
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {wrureq, wrurep}
# 但し、これは、Externalには返さない方がいいと思います。
# Who-Are-Youは、返してくれると凄く嬉しいけど。
というわけで、tcpとかudpはIPv4と同じ考え方でいいと思うんだけど、ICMP
は気をつけた方がいいかもしれません。
# 常識だったらごめんなさい。
追伸： 一応。proto ipv6-icmpの部分は、/etc/protocolsを見て下さ
い。もしかして、表現が違う可能性があるので。
二伸： Path-MTU Discoveryの正確な挙動は、ここには書いていません。
そう言うICMPがあるわけではなくpacket too bigを利用して、
途中経路のMTUを知る術がある（と言っていいのかしらん？）と
言うことに過ぎないはず。
（自信がないので、識者のコメントが欲しいです。呑んでいる
のでRFC当たる気合いは今は無い…）
JANOGで話題のIPv6ICMPフィルタ話。
こういう情報ってほかの国であまり大々的に議論されているのを見たことがない・・・
subject [janog:08906] IPv6 Firewall
許です。
この間、IPv6のFirewallを書いててちょっと気がついたので、ここにも
書いておきます。
# きっかけは、某所のWebサービスが見られない場所があると言う話を
# 某所で聞いたことですが。
IPv6は、IPv4と違ってパケットをFragmentしません。その代わり、
Path-MTU Discoveryを行ってpacket sizeを決める（表現は微妙ですが）
わけですが、このPATH-MTU DiscoveryってICMPなんですよね。
というわけで、以下悲しいシナリオ。
1) IPv4では、今時、ICMPを全部たたき落とす設定がしばしば行われる
2) IPv4では、DF bitを立てていない限り、それでも問題なく通信できる。
一応、ICMP type UNREACH code NeedFragmentが帰ってくるので
Path-MTU Discoveryと同等の処理は出来るが、そこまでのFilterはあ
まり書かれていないと思う。
3) IPv6でもIPv4と同じようなPacket Filter Ruleを書いてしまう
4) 従って、Path-MTU Discoveryをたたき落としてしまう
5) そのせいで見られないWeb Pageが発生することがある
で、僕自身はipfwとかiptablesの実装を知らないので、それらの
filter ruleは書けませんが、OpenBSDに(NetBSD/FreeBSDにも)実装されて
いるpfのRuleは判った（つもりな）ので、一応メモ代わりに。
(NetBSD 5.0で試したつもり。転記ミスがあったらごめん)
pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type toobig
# これが問題になるって事は、下手をしたらNeighbor Discoveryも問題に
# なるってことかしらん？ってことで、Neighbor DiscoveryとRouter Solicitation
# さらに、Who-Are-Youに関する部分も一応。
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {routersol, routeradv}
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {neighbrsol, neighbradv}
# pass in quick inet6 proto ipv6-icmp from $from to $to icmp6-type {wrureq, wrurep}
# 但し、これは、Externalには返さない方がいいと思います。
# Who-Are-Youは、返してくれると凄く嬉しいけど。
というわけで、tcpとかudpはIPv4と同じ考え方でいいと思うんだけど、ICMP
は気をつけた方がいいかもしれません。
# 常識だったらごめんなさい。
追伸： 一応。proto ipv6-icmpの部分は、/etc/protocolsを見て下さ
い。もしかして、表現が違う可能性があるので。
二伸： Path-MTU Discoveryの正確な挙動は、ここには書いていません。
そう言うICMPがあるわけではなくpacket too bigを利用して、
途中経路のMTUを知る術がある（と言っていいのかしらん？）と
言うことに過ぎないはず。
（自信がないので、識者のコメントが欲しいです。呑んでいる
のでRFC当たる気合いは今は無い…）
JANOGで話題のIPv6ICMPフィルタ話。
こういう情報ってほかの国であまり大々的に議論されているのを見たことがない・・・
5/16/2009
JANOG@May 15, 2009
date Fri, May 15, 2009 at 11:00 AM
subject [janog:08881] [Fwd: (JPNIC-IP-USERS 1696) JPOPM16 ご提案募集！]
JPNIC 奥谷です。
転送します。重複ご了承ください。
みなさま、
第16回JPNICオープンポリシーミーティングでのプレゼンテーションを募集いた
します。
JPNICオープンポリシーミーティングでは、みなさんからご応募いただいた発
表をもとにIPアドレス・AS番号の管理に関わる議論を進めています。
これまでは例えばIPv6 PIアドレスの新設やIPv4アドレスの枯渇に向けた最後の
ブロックの分配方法等について、ご応募いただいた提案に基づき議論を行ってき
ました。
また、提案に限らず、情報提供を目的としたプレゼンテーションもお受けしてい
ます。
「発表に興味はあるけれど内容がかたまっていない」
「問題意識はあるけれどどう発表すればよいのかわからない」
等のご相談も受け付けていますので、その他ご応募にあたってのご不明な点もあ
わあせて、お気軽にポリシーWG(jpopf@venus.gr.jp)までご連絡ください。
なお，今回，開催日は，ご提案がございました場合，APNICミーティングへのエ
スカレーションを想定して7月1日(水)を予定しておりますが，この時期ですと
APNIC ミーティングにおけます提案が出そろっていないため，ご提案の有無，
APNICへのエスカレーションの必要性を鑑み，皆様からのご応募に基づき，ご提
案者と相談の上最終決定することにいたしました．開催情報のご案内は5月下旬
に予定しています．
■プレゼンテーション募集要項
募集内容：日本におけるIPアドレス・AS番号のポリシーに関するプレゼンテー
ション
応募締切：2009年5月29日(金)
応募先 ：jpopm-apply@venus.gr.jp
応募方法：下記に添付する応募フォームに記入の上，ご応募ください．
通知 ： 当日プレゼンテーションをお願いする方には，2009年6月5日(金)
までにご本人にご連絡いたします．
開催情報：決定次第後日改めてご案内いたします。
※下記応募フォームにて頂いた個人情報は，ポリシーワーキンググループに
おけます，第16回オープンポリシーミーティングの議題検討，及び，応募者
との連絡目的以外には使用致しません．
※ご提案内容に関します理解を深め，議論を進めるために，内容，及びプ
レゼンテーション資料をミーティング開催前から公開させて頂きますこと
をご了承下さい．公開方法はWeb掲載、当MLへの周知を予定しております．
掲載URL等は後日お知らせ致します．
※プレゼンテーションをご応募は内容に沿うものであれば基本的にお受けし
ておりますが，時間枠の都合上，残念ながらお断りさせていただくことも
ありますことをご了承ください．
■応募フォーム
------------------------------------------------------------------------
第16回オープンポリシーミーティングプレゼンテーション応募フォーム
ご氏名 ：
ご所属 ：
タイトル ：
カテゴリー：□情報提供(I) □提案(P)
※上記のどちらかをご選択ください
必要時間(分)：
内容 ：
ポリシー提案(P)の場合、以下の項目を明記下さい。
・ご提案内容の概略
・ご提案理由
- 現状の問題点
- 改善したいポイント
- 想定されるメリット、デメリット
・ご提案が採択された場合の影響範囲
（指定事業者、JPNIC、ユーザなど）
・コミュニティに対し，合意を得たいポイント
------------------------------------------------------------------------
■応募に関するお問い合わせ
応募内容、記述方法など、応募にあたってご不明な点、ご相談がありました
らお気軽にご連絡ください。
ポリシーワーキンググループ
jpopf@venus.gr.jp
■参考
「JPNICオープンポリシーミーティングについて」
http://www.nic.ad.jp/ja/basics/terms/jpopm.html
「第15回JPNICオープンポリシーミーティング」
http://www.venus.gr.jp/opf-jp/opm15/opm15-program.html
「JPNICにおけるIPアドレスポリシー策定プロセス」
http://www.nic.ad.jp/doc/policy-process.html
さてと。ARIN,RIPE,LACNIC,AfriNICが春にポリシー策定シーズンを終えたこの時期に、
日本のポリシー活動が熱くなる。
#APNICが夏と冬っていう季節はずれなのが原因で、日本がとくにどうというわけでもないのですが。
提案したいことがあればガンガン提案を出してみるといいですよ。
ポリシーWGの面々が優しくフォローしてくれるはずです。(突拍子のないポリシー以外は)
subject [janog:08881] [Fwd: (JPNIC-IP-USERS 1696) JPOPM16 ご提案募集！]
JPNIC 奥谷です。
転送します。重複ご了承ください。
みなさま、
第16回JPNICオープンポリシーミーティングでのプレゼンテーションを募集いた
します。
JPNICオープンポリシーミーティングでは、みなさんからご応募いただいた発
表をもとにIPアドレス・AS番号の管理に関わる議論を進めています。
これまでは例えばIPv6 PIアドレスの新設やIPv4アドレスの枯渇に向けた最後の
ブロックの分配方法等について、ご応募いただいた提案に基づき議論を行ってき
ました。
また、提案に限らず、情報提供を目的としたプレゼンテーションもお受けしてい
ます。
「発表に興味はあるけれど内容がかたまっていない」
「問題意識はあるけれどどう発表すればよいのかわからない」
等のご相談も受け付けていますので、その他ご応募にあたってのご不明な点もあ
わあせて、お気軽にポリシーWG(jpopf@venus.gr.jp)までご連絡ください。
なお，今回，開催日は，ご提案がございました場合，APNICミーティングへのエ
スカレーションを想定して7月1日(水)を予定しておりますが，この時期ですと
APNIC ミーティングにおけます提案が出そろっていないため，ご提案の有無，
APNICへのエスカレーションの必要性を鑑み，皆様からのご応募に基づき，ご提
案者と相談の上最終決定することにいたしました．開催情報のご案内は5月下旬
に予定しています．
■プレゼンテーション募集要項
募集内容：日本におけるIPアドレス・AS番号のポリシーに関するプレゼンテー
ション
応募締切：2009年5月29日(金)
応募先 ：jpopm-apply@venus.gr.jp
応募方法：下記に添付する応募フォームに記入の上，ご応募ください．
通知 ： 当日プレゼンテーションをお願いする方には，2009年6月5日(金)
までにご本人にご連絡いたします．
開催情報：決定次第後日改めてご案内いたします。
※下記応募フォームにて頂いた個人情報は，ポリシーワーキンググループに
おけます，第16回オープンポリシーミーティングの議題検討，及び，応募者
との連絡目的以外には使用致しません．
※ご提案内容に関します理解を深め，議論を進めるために，内容，及びプ
レゼンテーション資料をミーティング開催前から公開させて頂きますこと
をご了承下さい．公開方法はWeb掲載、当MLへの周知を予定しております．
掲載URL等は後日お知らせ致します．
※プレゼンテーションをご応募は内容に沿うものであれば基本的にお受けし
ておりますが，時間枠の都合上，残念ながらお断りさせていただくことも
ありますことをご了承ください．
■応募フォーム
------------------------------------------------------------------------
第16回オープンポリシーミーティングプレゼンテーション応募フォーム
ご氏名 ：
ご所属 ：
タイトル ：
カテゴリー：□情報提供(I) □提案(P)
※上記のどちらかをご選択ください
必要時間(分)：
内容 ：
ポリシー提案(P)の場合、以下の項目を明記下さい。
・ご提案内容の概略
・ご提案理由
- 現状の問題点
- 改善したいポイント
- 想定されるメリット、デメリット
・ご提案が採択された場合の影響範囲
（指定事業者、JPNIC、ユーザなど）
・コミュニティに対し，合意を得たいポイント
------------------------------------------------------------------------
■応募に関するお問い合わせ
応募内容、記述方法など、応募にあたってご不明な点、ご相談がありました
らお気軽にご連絡ください。
ポリシーワーキンググループ
jpopf@venus.gr.jp
■参考
「JPNICオープンポリシーミーティングについて」
http://www.nic.ad.jp/ja/basics/terms/jpopm.html
「第15回JPNICオープンポリシーミーティング」
http://www.venus.gr.jp/opf-jp/opm15/opm15-program.html
「JPNICにおけるIPアドレスポリシー策定プロセス」
http://www.nic.ad.jp/doc/policy-process.html
さてと。ARIN,RIPE,LACNIC,AfriNICが春にポリシー策定シーズンを終えたこの時期に、
日本のポリシー活動が熱くなる。
#APNICが夏と冬っていう季節はずれなのが原因で、日本がとくにどうというわけでもないのですが。
提案したいことがあればガンガン提案を出してみるといいですよ。
ポリシーWGの面々が優しくフォローしてくれるはずです。(突拍子のないポリシー以外は)
GTER@May 15,2009
Date: Fri, 15 May 2009 09:00:18 -0400
Subject: [GTER] Google ontem
http://www.wired.com/epicenter/2009/05/when-google-goes-down-it-goes-down-hard/
http://www.networkworld.com/community/node/41880
Pequena diferenca no grafico :-)
OutageやNANOGで話題になったGoogleIssueがここにも報告されています。
世界はつながっているんだねぇ。
自分が著名サイトを運営していて、チョンボや障害を引き起こすと世界中にバレるということ。
Subject: [GTER] Google ontem
http://www.wired.com/epicenter/2009/05/when-google-goes-down-it-goes-down-hard/
http://www.networkworld.com/community/node/41880
Pequena diferenca no grafico :-)
OutageやNANOGで話題になったGoogleIssueがここにも報告されています。
世界はつながっているんだねぇ。
自分が著名サイトを運営していて、チョンボや障害を引き起こすと世界中にバレるということ。
Outages@May 15, 2009
date Fri, May 15, 2009 at 12:56 AM
subject [outages] Google Issue
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
Googleは既に主要インフラと化していますね。
NANOGでも同様に熱い話題になっているようです。
subject [outages] Google Issue
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
Googleは既に主要インフラと化していますね。
NANOGでも同様に熱い話題になっているようです。
5/13/2009
Gore/ESNOG@May 12, 2009
Date: Tue, 12 May 2009 18:48:52 +0200
Subject: [Gore] Ficheros video y streaming de GORE 3
Gracias a la gente del DIT UPM que nos acompañó ayer (Abel y Monica)
estan en linea los videos del las ponencias del GORE3, como ficheros
para bajar o via streaming.
Ver los URLs en la pagina del GORE 3: http://www.esnog.net/gore3.html
Saludos
Joao
先日行われたGore3のビデオアーカイブも公開された。
全篇スペイン語だが。勉強にいかが？
Subject: [Gore] Ficheros video y streaming de GORE 3
Gracias a la gente del DIT UPM que nos acompañó ayer (Abel y Monica)
estan en linea los videos del las ponencias del GORE3, como ficheros
para bajar o via streaming.
Ver los URLs en la pagina del GORE 3: http://www.esnog.net/gore3.html
Saludos
Joao
先日行われたGore3のビデオアーカイブも公開された。
全篇スペイン語だが。勉強にいかが？
5/12/2009
Gore/ESNOG@May 11, 2009
Date: Mon, 11 May 2009 11:44:12 +0200
From: joao damas
Subject: [Gore] Cambio en servidor jabber para GORE3
Utilizad la sala xmpp://gore3@conference.jabber.org para comunicaros
si quereis hacer preguntas a los ponentes de GORE3 y no estais en la
sala pero si siguiendo el streaming.
El de esnog esta caido por gremlins que no consigo eliminar por ahora
Joao
もうすぐ開催されるGore3のJabberも準備された。
JANOGにも欲しいよね。
From: joao damas
Subject: [Gore] Cambio en servidor jabber para GORE3
Utilizad la sala xmpp://gore3@conference.jabber.org para comunicaros
si quereis hacer preguntas a los ponentes de GORE3 y no estais en la
sala pero si siguiendo el streaming.
El de esnog esta caido por gremlins que no consigo eliminar por ahora
Joao
もうすぐ開催されるGore3のJabberも準備された。
JANOGにも欲しいよね。
NANOG@May 11, 2009
Date: Mon, 11 May 2009 22:29:27 +0200
Subject: two interfaces one subnet
Hi,
This is a pretty moronic question, but I've been searching RFC's on-
and-off for a couple of weeks and can't find an answer. So I'm hoping
someone here will know it offhand.
I've been looking through RFC's trying to find a clear statement that
having two interfaces in the same subnet does not work, but can't find
it that statement anywhere.
The OS in this case is Linux. I know it can be done with clever
routing and prioritization and such, but this has to do with vanilla
config, just setting up two interfaces in one network.
I would be grateful for a pointer to such an RFC statement, assuming
it exists.
Thanks!
Chris
とりあえずやってみればいいことなのにRFCを調べるなんて素晴らしい。
色々やった結果、挙動が異なるので調べてるならそれも納得。
コメントがたくさん出てきています。
Subject: two interfaces one subnet
Hi,
This is a pretty moronic question, but I've been searching RFC's on-
and-off for a couple of weeks and can't find an answer. So I'm hoping
someone here will know it offhand.
I've been looking through RFC's trying to find a clear statement that
having two interfaces in the same subnet does not work, but can't find
it that statement anywhere.
The OS in this case is Linux. I know it can be done with clever
routing and prioritization and such, but this has to do with vanilla
config, just setting up two interfaces in one network.
I would be grateful for a pointer to such an RFC statement, assuming
it exists.
Thanks!
Chris
とりあえずやってみればいいことなのにRFCを調べるなんて素晴らしい。
色々やった結果、挙動が異なるので調べてるならそれも納得。
コメントがたくさん出てきています。
5/09/2009
AfNOG@May 8, 2009
Date: Fri, 8 May 2009 07:12:21 -0700 (PDT)
Subject: [afnog] Breaking News: Kenyan Internet Community comes face
to face with new Legislation
Apologies for cross-posting:
It took a KENIC (KEnya Network Information Center, www.kenic.or.ke) Annual General Meeting for the Kenyan Internet community to digest the implication of the a Kenyan ICT Legislation passed more than five months ago. The law which included sections that touched on the Media, IT, Telecommunication and Postal Services has faced stiff resistance from the Media fraternity while the Internet Community kept a low if not a dead profile.
It was at the KENIC general meeting held today in Nairobi that the Internet Community grappled with the implication of the IT section on the operation of the .KE namespace. The law specifies that all second level .KE internet domain names must be licensed by the country's converged Regulator, Communication Commission of Kenya. The law requires that all Registries - those who manage the internet domains - must apply for a license by the 2nd of June 2009.
KENIC, a public-private-partnership has under the ICANN Policies been managing the .KE namespace including the 2nd level sub-domains such as xyz.CO.KE, xyz.OR.KE, etc. From 2nd June 2009, KENIC must seek permission from the Regulator to continue managing these sub-domains. In an effort to comply with the law, the KENIC Board requested the community to support a resolution that a new legal entity (Special Purpose Vehicle, SPV) be created in order to apply for the license from the Regulator as well as compete with other potential entities that are set to fight in that space.
The proposals opened up heated discussions with some members wondering if KENIC was ceding its hard-won rights & control over the .KE namespace to an exclusive and single entity. The current governance structure for KENIC provides for a Multistakeholder Partnership over the whole .KE namespace and has the Govt, Academia, Private Sector/Telcos and Civil Society Board Representation that is wholly accountable to Internet Users during Annual General Meetings. Effectively, the new law takes part of this mandate and places it under one or two of these Stakeholders that is the Regulator/Govt.
Members wondered about the criteria that would be used by the Regulator to award the management licenses to various competitors. Others wondered about the potential conflict between the local legislation and the ICANN policies given that KENIC has currently been operating under ICANN policies but now has to take cognizance of the local law. For example, if the Regulator granted a license to someone else to manage the "co.ke" subdomain BUT the local internet community for one reason or the other instructed the KENIC Board NOT to accept and transfer the delegation from KENIC how would that be resolved? And yet other members wondered to what extend the proposed SPV would cannibalize their existing markets and services.
It has taken five months of silence but clearly, the Kenyan Internet community is just beginning to understand and feel the heat of some sections in the ICT law that had previously been hijacked and labeled "Media law" at the expense of IT practitioners. It will be interesting to see how this plays out before and after the 2nd of June 2009 - the date when all subdomain managers must be licensed by the Regulator.
walu
ケニアにてメディアに関するIT関連の法律の適用に関して。
今後こういう動きが増えてくるのかな。
Subject: [afnog] Breaking News: Kenyan Internet Community comes face
to face with new Legislation
Apologies for cross-posting:
It took a KENIC (KEnya Network Information Center, www.kenic.or.ke) Annual General Meeting for the Kenyan Internet community to digest the implication of the a Kenyan ICT Legislation passed more than five months ago. The law which included sections that touched on the Media, IT, Telecommunication and Postal Services has faced stiff resistance from the Media fraternity while the Internet Community kept a low if not a dead profile.
It was at the KENIC general meeting held today in Nairobi that the Internet Community grappled with the implication of the IT section on the operation of the .KE namespace. The law specifies that all second level .KE internet domain names must be licensed by the country's converged Regulator, Communication Commission of Kenya. The law requires that all Registries - those who manage the internet domains - must apply for a license by the 2nd of June 2009.
KENIC, a public-private-partnership has under the ICANN Policies been managing the .KE namespace including the 2nd level sub-domains such as xyz.CO.KE, xyz.OR.KE, etc. From 2nd June 2009, KENIC must seek permission from the Regulator to continue managing these sub-domains. In an effort to comply with the law, the KENIC Board requested the community to support a resolution that a new legal entity (Special Purpose Vehicle, SPV) be created in order to apply for the license from the Regulator as well as compete with other potential entities that are set to fight in that space.
The proposals opened up heated discussions with some members wondering if KENIC was ceding its hard-won rights & control over the .KE namespace to an exclusive and single entity. The current governance structure for KENIC provides for a Multistakeholder Partnership over the whole .KE namespace and has the Govt, Academia, Private Sector/Telcos and Civil Society Board Representation that is wholly accountable to Internet Users during Annual General Meetings. Effectively, the new law takes part of this mandate and places it under one or two of these Stakeholders that is the Regulator/Govt.
Members wondered about the criteria that would be used by the Regulator to award the management licenses to various competitors. Others wondered about the potential conflict between the local legislation and the ICANN policies given that KENIC has currently been operating under ICANN policies but now has to take cognizance of the local law. For example, if the Regulator granted a license to someone else to manage the "co.ke" subdomain BUT the local internet community for one reason or the other instructed the KENIC Board NOT to accept and transfer the delegation from KENIC how would that be resolved? And yet other members wondered to what extend the proposed SPV would cannibalize their existing markets and services.
It has taken five months of silence but clearly, the Kenyan Internet community is just beginning to understand and feel the heat of some sections in the ICT law that had previously been hijacked and labeled "Media law" at the expense of IT practitioners. It will be interesting to see how this plays out before and after the 2nd of June 2009 - the date when all subdomain managers must be licensed by the Regulator.
walu
ケニアにてメディアに関するIT関連の法律の適用に関して。
今後こういう動きが増えてくるのかな。
GTER@May 8, 2009
Date: Fri, 8 May 2009 00:59:35 -0300
Subject: [GTER] Internautas ficam temporariamente sem acesso ao Google
no Brasil
http://ultimosegundo.ig.com.br/economia/2009/05/07/internautas+ficam+temporariamente+sem+acesso+ao+google+no+brasil+6002915.html
O Google Brasil informou h? pouco que um problema t?cnico, surgido durante
manuten??o de rotina dos roteadores, tirou do ar o site de buscas hoje ?
tarde.
Segundo a empresa, a falha interferiu no tr?fego de informa??es de parte dos
usu?rios brasileiros.
De acordo com nota ? imprensa, a pane durou "instantes" e rapidamente foi
solucionada. Boa parte dos internautas, no entanto, passou pelo menos duas
horas sem acesso ao site de buscas. E a impossibilidade de conex?o perdurava
no in?cio da noite.
Googleブラジルの接続障害でここのところGTERが活発でしたが、レポートが出てきました。
ようやく収束かな。
Subject: [GTER] Internautas ficam temporariamente sem acesso ao Google
no Brasil
http://ultimosegundo.ig.com.br/economia/2009/05/07/internautas+ficam+temporariamente+sem+acesso+ao+google+no+brasil+6002915.html
O Google Brasil informou h? pouco que um problema t?cnico, surgido durante
manuten??o de rotina dos roteadores, tirou do ar o site de buscas hoje ?
tarde.
Segundo a empresa, a falha interferiu no tr?fego de informa??es de parte dos
usu?rios brasileiros.
De acordo com nota ? imprensa, a pane durou "instantes" e rapidamente foi
solucionada. Boa parte dos internautas, no entanto, passou pelo menos duas
horas sem acesso ao site de buscas. E a impossibilidade de conex?o perdurava
no in?cio da noite.
Googleブラジルの接続障害でここのところGTERが活発でしたが、レポートが出てきました。
ようやく収束かな。
5/08/2009
RIPE-address-policy-wg@May 7, 2009
Date: Thu, 7 May 2009 14:15:03 +0200
Subject: [address-policy-wg] IPv4 PI assignment statistics
Dear Colleagues,
During the Address Policy Working Group session at RIPE58, statistics
were requested about the number and size of IPv4 PI prefixes that the
RIPE NCC has assigned over the last few years.
NOTE: The numbers for 2009 contain data up to May 2009.
2005 2006 2007 2008 2009
/16 0 1 0 0 1
/17 0 1 1 0 0
/18 1 2 3 10 1
/19 3 7 4 12 7
/20 25 28 23 44 14
/21 51 56 89 100 26
/22 260 261 261 402 111
/23 385 464 778 571 159
/24 726 897 973 1046 292
/25 10 22 8 8 5
/26 7 6 8 5 0
/27 5 8 7 7 2
/28 0 8 0 1 0
/29 2 1 0 8 0
Total 1475 1762 2155 2214 618
Please let us know if you require any further information.
Best regards,
Alex Le Heux
RIPE NCC
欧州地域でのプロバイダ非依存IPv4アドレス割当ての状況についての報告。
/25以下も結構あるけど、何に使っているんだろうか。使えているんだろうか。
Subject: [address-policy-wg] IPv4 PI assignment statistics
Dear Colleagues,
During the Address Policy Working Group session at RIPE58, statistics
were requested about the number and size of IPv4 PI prefixes that the
RIPE NCC has assigned over the last few years.
NOTE: The numbers for 2009 contain data up to May 2009.
2005 2006 2007 2008 2009
/16 0 1 0 0 1
/17 0 1 1 0 0
/18 1 2 3 10 1
/19 3 7 4 12 7
/20 25 28 23 44 14
/21 51 56 89 100 26
/22 260 261 261 402 111
/23 385 464 778 571 159
/24 726 897 973 1046 292
/25 10 22 8 8 5
/26 7 6 8 5 0
/27 5 8 7 7 2
/28 0 8 0 1 0
/29 2 1 0 8 0
Total 1475 1762 2155 2214 618
Please let us know if you require any further information.
Best regards,
Alex Le Heux
RIPE NCC
欧州地域でのプロバイダ非依存IPv4アドレス割当ての状況についての報告。
/25以下も結構あるけど、何に使っているんだろうか。使えているんだろうか。
LACNIC-Anuncios@May 7, 2009
Date: Thu, 07 May 2009 18:34:06 -0300
Subject: [LACNIC/Anuncios] Nueva Informacion LACNCI XII/Update LACNIC
XII
～スペイン語版はばっさりと略～
Dear colleagues of the Latin American and Caribbean community:
More than 250 people have already registered to attend the LACNI XII
meeting in Panama. The event will be held on 24 - 29 May 2009, at the
Hotel El Panama. The registration fee discount is valid until tomorrow,
8 May. Register now at:
http://www.lacnic.net/en/eventos/lacnicxii/registro.html
Accommodation
-----------------
The Hotel Riande Continental, located just a few blocks away from the
hotel where the event will be held, has announced new promotional rates
valid as of today! If you have not yet made your reservations you can
check out this and other accommodation options at the following address:
http://www.lacnic.net/en/eventos/lacnicxii/hospedaje.html
Program
----------
The meeting?s program is available at:
http://www.lacnic.net/en/eventos/lacnicxii/programa.html
Social Events
--------------
New information about the social events has been published. Find out
about the welcome cocktail that will be held on Monday the 25th
sponsored by Tiscali International Network and the social event that
will take place on Wednesday the 27th at a spectacular location.
http://www.lacnic.net/en/eventos/lacnicxii/eventossociales.html
Safety - H1N1 Flu
--------------------
In view of the inquiries we have received from numerous members of the
community and potential attendants to the event regarding the H1N1 FLU,
the event?s organizers would like to inform that the possibility of
suspending or postponing the meeting has not been considered.
We advise those travelling to Panama to take all relevant precautions
that have been made public. We would also like to present the
information provided by the Panamanian Health Ministry regarding the
measures Panama has adopted in relation to this problem, which is
available on the Health Ministry?s website: http://www.minsa.gob.pa/
For updated information, visit the event?s website regularly:
http://www.lacnic.net/en/eventos/lacnicxii/
See you in Panama!
LACNIC XII Organization Committee
LACNICミーティングが再来週に迫っていますが。
新型インフルエンザ(旧名：豚インフルエンザ)の情報が出ています。
参加される方はご注意を。新型インフルエンザのメッカ、メキシコシティからも多数参加のはずです。
Subject: [LACNIC/Anuncios] Nueva Informacion LACNCI XII/Update LACNIC
XII
～スペイン語版はばっさりと略～
Dear colleagues of the Latin American and Caribbean community:
More than 250 people have already registered to attend the LACNI XII
meeting in Panama. The event will be held on 24 - 29 May 2009, at the
Hotel El Panama. The registration fee discount is valid until tomorrow,
8 May. Register now at:
http://www.lacnic.net/en/eventos/lacnicxii/registro.html
Accommodation
-----------------
The Hotel Riande Continental, located just a few blocks away from the
hotel where the event will be held, has announced new promotional rates
valid as of today! If you have not yet made your reservations you can
check out this and other accommodation options at the following address:
http://www.lacnic.net/en/eventos/lacnicxii/hospedaje.html
Program
----------
The meeting?s program is available at:
http://www.lacnic.net/en/eventos/lacnicxii/programa.html
Social Events
--------------
New information about the social events has been published. Find out
about the welcome cocktail that will be held on Monday the 25th
sponsored by Tiscali International Network and the social event that
will take place on Wednesday the 27th at a spectacular location.
http://www.lacnic.net/en/eventos/lacnicxii/eventossociales.html
Safety - H1N1 Flu
--------------------
In view of the inquiries we have received from numerous members of the
community and potential attendants to the event regarding the H1N1 FLU,
the event?s organizers would like to inform that the possibility of
suspending or postponing the meeting has not been considered.
We advise those travelling to Panama to take all relevant precautions
that have been made public. We would also like to present the
information provided by the Panamanian Health Ministry regarding the
measures Panama has adopted in relation to this problem, which is
available on the Health Ministry?s website: http://www.minsa.gob.pa/
For updated information, visit the event?s website regularly:
http://www.lacnic.net/en/eventos/lacnicxii/
See you in Panama!
LACNIC XII Organization Committee
LACNICミーティングが再来週に迫っていますが。
新型インフルエンザ(旧名：豚インフルエンザ)の情報が出ています。
参加される方はご注意を。新型インフルエンザのメッカ、メキシコシティからも多数参加のはずです。
ARIN-ppml@May 7, 2009
Date: Thu, 7 May 2009 12:58:50 -0500
Subject: [arin-ppml] general vendor comment
First I apologize to the list in advance if this is not an appropriate place
for this comment.
I am making a point of ending any conversation with a vendor with the
question "What is your roadmap for IPv6. Future purchase and renewal
decisions will be affected.". Almost invariably the answer is "Gee, you are
the first person that has asked. We don't have a roadmap. I will forward
this on to our development team and when there is a need I am sure we will
pursue it."
I would suggest to everyone that we all start requesting IPv6 information
from our vendors, and submit feature requests when appropriate. Hardware
and software vendors are not going to spend money to address this issue
until they see a widespread business case to do so.
Kevin
使用している機器のIPv6機能導入予定を問い合わせよう！という呼びかけ。
返事として既にRFPには長らく記載されていて、機能はある。だれも使わないだけ、という
ちょっと悲しいものも。
ま、IPv6だけで生活してみると色々わかることもあるけどね。
Subject: [arin-ppml] general vendor comment
First I apologize to the list in advance if this is not an appropriate place
for this comment.
I am making a point of ending any conversation with a vendor with the
question "What is your roadmap for IPv6. Future purchase and renewal
decisions will be affected.". Almost invariably the answer is "Gee, you are
the first person that has asked. We don't have a roadmap. I will forward
this on to our development team and when there is a need I am sure we will
pursue it."
I would suggest to everyone that we all start requesting IPv6 information
from our vendors, and submit feature requests when appropriate. Hardware
and software vendors are not going to spend money to address this issue
until they see a widespread business case to do so.
Kevin
使用している機器のIPv6機能導入予定を問い合わせよう！という呼びかけ。
返事として既にRFPには長らく記載されていて、機能はある。だれも使わないだけ、という
ちょっと悲しいものも。
ま、IPv6だけで生活してみると色々わかることもあるけどね。
5/07/2009
NZNOG@May 6, 2009
Date: Wed, 6 May 2009 10:34:50 +1000
Subject: [nznog] Wholesale DSL Opportunity
All,
We are looking at expanding our national Australian network into New Zealand, and as such we are looking for a partner to assist us with this.
In the short term, we are looking for Transit and also access to Telecom NZ DSL tails(to be handed off as L2TP sessions over Ethernet preferably).
Handoff location would be Sky Tower.
Is there anyone interested in this opportunity - please contact me off list
Thanks
Ben Cornish
National Network Manager
OZがNZに進出しようとしている？！
国を跨いでのネットワーク敷設って、法令とか監督官庁との兼ね合いとか、大変じゃないのかな？
Subject: [nznog] Wholesale DSL Opportunity
All,
We are looking at expanding our national Australian network into New Zealand, and as such we are looking for a partner to assist us with this.
In the short term, we are looking for Transit and also access to Telecom NZ DSL tails(to be handed off as L2TP sessions over Ethernet preferably).
Handoff location would be Sky Tower.
Is there anyone interested in this opportunity - please contact me off list
Thanks
Ben Cornish
National Network Manager
OZがNZに進出しようとしている？！
国を跨いでのネットワーク敷設って、法令とか監督官庁との兼ね合いとか、大変じゃないのかな？
RIPE-address-policy-wg@May 6, 2009
Date: Wed, 06 May 2009 11:22:53 +0200
Subject: [address-policy-wg] RIPE NCC Now Accepting Requests for IPv6 PI Assignments
[Apologies for duplicate emails.]
Dear Colleagues,
We are pleased to announce that the RIPE NCC now accept requests for
IPv6 Provider Independent (PI) assignments.
This follows the accepted policy proposal 2006-01 "Provider Independent
(PI) IPv6 Assignments for End User Organisations".
The request form and supporting notes are available from the RIPE
Document Store at:
http://www.ripe.net/ripe/docs/ipv6.html
Requests can also be made via the LIR Portal, which is available at:
https://lirportal.ripe.net/
IPv6 PI assignments will come from reserved block 2001:678::/29. You may
want to update your filters.
Regards,
Scott Donald
Registration Services
RIPE NCC
RIPE地域ではIPv6のPI(Provider非依存)アドレスの要望を受け入れ始めました。
IPv6で未来永劫リナンバしたくないよ、という方はRIPE NCCメンバーになってリクエストするといいですよ。
Subject: [address-policy-wg] RIPE NCC Now Accepting Requests for IPv6 PI Assignments
[Apologies for duplicate emails.]
Dear Colleagues,
We are pleased to announce that the RIPE NCC now accept requests for
IPv6 Provider Independent (PI) assignments.
This follows the accepted policy proposal 2006-01 "Provider Independent
(PI) IPv6 Assignments for End User Organisations".
The request form and supporting notes are available from the RIPE
Document Store at:
http://www.ripe.net/ripe/docs/ipv6.html
Requests can also be made via the LIR Portal, which is available at:
https://lirportal.ripe.net/
IPv6 PI assignments will come from reserved block 2001:678::/29. You may
want to update your filters.
Regards,
Scott Donald
Registration Services
RIPE NCC
RIPE地域ではIPv6のPI(Provider非依存)アドレスの要望を受け入れ始めました。
IPv6で未来永劫リナンバしたくないよ、という方はRIPE NCCメンバーになってリクエストするといいですよ。
NANOG@May 6, 2009
Date: Wed, 6 May 2009 11:41:55 -0400
Subject: Minnesota Sends List of Blacklisted Gambling Sites to ISPs,
Telcos
With regard to the recent discussion...
"Late last month the Minnesota Department of Public Safety announced
it would require ISPs and telcos to block computers located in the
state from accessing gambling sites, and said non-compliant companies
would be referred to the FCC. Now, the state has sent each ISP and
telco the enclosed blacklist of sites and URLs."
http://www.govtech.com/gt/articles/656645
--
Jeremy L. Gaddis
ミネソタ州の公安局がギャンブルサイトのURLをブラックリストとして各ISPに送付した、と。
実行しないとFCCに報告。
ようやく無秩序な事態から変化が起こるか。
Subject: Minnesota Sends List of Blacklisted Gambling Sites to ISPs,
Telcos
With regard to the recent discussion...
"Late last month the Minnesota Department of Public Safety announced
it would require ISPs and telcos to block computers located in the
state from accessing gambling sites, and said non-compliant companies
would be referred to the FCC. Now, the state has sent each ISP and
telco the enclosed blacklist of sites and URLs."
http://www.govtech.com/gt/articles/656645
--
Jeremy L. Gaddis
ミネソタ州の公安局がギャンブルサイトのURLをブラックリストとして各ISPに送付した、と。
実行しないとFCCに報告。
ようやく無秩序な事態から変化が起こるか。
5/06/2009
Gore/ESNOG@May 5, 2009
Date: Tue, 5 May 2009 09:49:00 +0200
Subject: [Gore] GORE-3: participación remota y difusión.
Estimados colegas,
Podemos confirmar que habrá webcasting del GORE-3, a través de la
herramienta ISABEL del DIT-UPM. Se podrá acceder desde la página del
evento (http://www.esnog.net/gore3.html), aunque también la incluyo en
este mensaje:
> mms://stream1.dit.upm.es/isabel
También habilitaremos una sala de chat Jabber para facilitar la
participación remota. Los detalles de acceso estarán disponibles desde
la página del evento, así como las normas de "netiquette" para poder
participar.
Intentaremos que las presentaciones estén disponibles antes de las
charlas, para facilitar el seguimiento.
Estamos a vuestra disposición para cualquier duda o problema que
podais tener.
Saludos,
Voluntarios de ESNOG
Gore-3のリモート参加のお知らせ。
ストリーミングも行うようですね。JANOGもこういう取り組みがあってもいいのになぁ。
Subject: [Gore] GORE-3: participación remota y difusión.
Estimados colegas,
Podemos confirmar que habrá webcasting del GORE-3, a través de la
herramienta ISABEL del DIT-UPM. Se podrá acceder desde la página del
evento (http://www.esnog.net/gore3.html), aunque también la incluyo en
este mensaje:
> mms://stream1.dit.upm.es/isabel
También habilitaremos una sala de chat Jabber para facilitar la
participación remota. Los detalles de acceso estarán disponibles desde
la página del evento, así como las normas de "netiquette" para poder
participar.
Intentaremos que las presentaciones estén disponibles antes de las
charlas, para facilitar el seguimiento.
Estamos a vuestra disposición para cualquier duda o problema que
podais tener.
Saludos,
Voluntarios de ESNOG
Gore-3のリモート参加のお知らせ。
ストリーミングも行うようですね。JANOGもこういう取り組みがあってもいいのになぁ。
NANOG@May 5, 2009
Date: Tue, 5 May 2009 13:38:17 -0700
Subject: DHCPv6 PD chains vs bridging
On Tue, May 05, 2009 at 04:22:04PM -0400, Paul Timmins wrote:
> Sorry for the top post, but as a crazy thought here, why not throw out an
> RA, and if answered, go into transparent bridge mode? Let the sophisticated
> users who want routed behavior override it manually.
Customer premise gear has a 'front side' and a 'back side', and it is
already well ingrained behaviour for 'back-to-back port chaining' to
create a single large bridged network in the home. What is the
customer's anticipated result from front-to-back chaining?
That seems much more reliable a hint to me than conditional behaviour.
DHCPv6 PD is applicable to the ISP customer premise. DHCPv6 PD
'chaining' however is probably only applicable in some promised future
where there are alternative home network medias to Ethernet, or to the
Enterprise where the boundaries drawn in broadcast domains are
administrative in nature and not technical (but still, all automated).
--
David W. Hankins
DHCPv6PD(PrefixDelegation)にするかブリッジ(RA(RouterAdvertise))にするかはやはり悩むポイント。
法人向けサービスならDHCPv6PDかな。個人向けならRAでもいいじゃん？って個人的に思います。
Subject: DHCPv6 PD chains vs bridging
On Tue, May 05, 2009 at 04:22:04PM -0400, Paul Timmins wrote:
> Sorry for the top post, but as a crazy thought here, why not throw out an
> RA, and if answered, go into transparent bridge mode? Let the sophisticated
> users who want routed behavior override it manually.
Customer premise gear has a 'front side' and a 'back side', and it is
already well ingrained behaviour for 'back-to-back port chaining' to
create a single large bridged network in the home. What is the
customer's anticipated result from front-to-back chaining?
That seems much more reliable a hint to me than conditional behaviour.
DHCPv6 PD is applicable to the ISP customer premise. DHCPv6 PD
'chaining' however is probably only applicable in some promised future
where there are alternative home network medias to Ethernet, or to the
Enterprise where the boundaries drawn in broadcast domains are
administrative in nature and not technical (but still, all automated).
--
David W. Hankins
DHCPv6PD(PrefixDelegation)にするかブリッジ(RA(RouterAdvertise))にするかはやはり悩むポイント。
法人向けサービスならDHCPv6PDかな。個人向けならRAでもいいじゃん？って個人的に思います。
AusNOG@May 5, 2009
date Tue, May 5, 2009 at 11:10 PM
subject Re: [AusNOG] Issues with Cisco IOS 12.4(25) ?
Hi Greg
At my employer we upgraded one of our Internet facing 7200s to 12.4(25) and had it crash twice in around 45mins. Also had major issues with it bringing up BGP sessions running password protection to 3 out of 5 peers that ran it.
Ended up doing a stack of dumps for TAC but gave in and rolled back to 12.4(23). We also bailed on the idea of doing our 2801/21/51 fleet until we had an opportunity to gain lab time to test it before deployment anywhere.
Regards,
Rossco
Ross Delaforce
Sent: Tue, 05 May 2009 23:58:27 +1000
Subject: [AusNOG] Issues with Cisco IOS 12.4(25) ?
Hi All,
Is anyone on AUSNOG running this on any of their Cisco 2800/7200's?
We upgraded one of our borders to this last week, and since then have been
having constant issues.
eg:
bdr1.per uptime is 24 minutes
System returned to ROM by error - a Software forced crash, PC 0x4007C19C at
13:36:51 UTC Tue May 5 2009
We have submitted a TAC case, but have yet to hear a resolution. We were
about to push this out to about 10 2811's and a bunch more 720(4/6)vxr's but
at this stage are holding off....
Cheers,
Greg
Cisco7200/2800シリーズでIOS 12.4(25)を使ってクラッシュが多発したらしい。
ちょっと前にGTERやcisco-nspで話題になった件かな？
subject Re: [AusNOG] Issues with Cisco IOS 12.4(25) ?
Hi Greg
At my employer we upgraded one of our Internet facing 7200s to 12.4(25) and had it crash twice in around 45mins. Also had major issues with it bringing up BGP sessions running password protection to 3 out of 5 peers that ran it.
Ended up doing a stack of dumps for TAC but gave in and rolled back to 12.4(23). We also bailed on the idea of doing our 2801/21/51 fleet until we had an opportunity to gain lab time to test it before deployment anywhere.
Regards,
Rossco
Ross Delaforce
Sent: Tue, 05 May 2009 23:58:27 +1000
Subject: [AusNOG] Issues with Cisco IOS 12.4(25) ?
Hi All,
Is anyone on AUSNOG running this on any of their Cisco 2800/7200's?
We upgraded one of our borders to this last week, and since then have been
having constant issues.
eg:
bdr1.per uptime is 24 minutes
System returned to ROM by error - a Software forced crash, PC 0x4007C19C at
13:36:51 UTC Tue May 5 2009
We have submitted a TAC case, but have yet to hear a resolution. We were
about to push this out to about 10 2811's and a bunch more 720(4/6)vxr's but
at this stage are holding off....
Cheers,
Greg
Cisco7200/2800シリーズでIOS 12.4(25)を使ってクラッシュが多発したらしい。
ちょっと前にGTERやcisco-nspで話題になった件かな？
5/05/2009
RIPE-list@May 4, 2009
Date: Mon, 04 May 2009 14:09:14 +0200
Subject: RIPE 58: Take Part Remotely
[Apologies for duplicates]
Dear Colleagues,
The RIPE 58 Meeting is now underway in Amsterdam, the Netherlands. The
meeting takes place from 4-8 May 2009.
If you're unable to attend, you can still take part in the meeting
proceedings remotely. Find out how to access the RIPE 58 IRC/Jabber
chatrooms, live webcasts and streamed session transcripts at:
http://www.ripe.net/ripe/meetings/ripe-58/live/
If you have any questions about remote participation at the RIPE 58
Meeting, please contact meeting@ripe.net.
Regards,
Camilla Meidell
Conference Coordinator
RIPE NCC
昨日から開催されているRIPEミーティングのリモート参加についてのお知らせ。
色々な議論が交わされるので必見かも。
自社/自分に不利な提案に対してはすぐに懸念表明をした方がいいですよ。
Subject: RIPE 58: Take Part Remotely
[Apologies for duplicates]
Dear Colleagues,
The RIPE 58 Meeting is now underway in Amsterdam, the Netherlands. The
meeting takes place from 4-8 May 2009.
If you're unable to attend, you can still take part in the meeting
proceedings remotely. Find out how to access the RIPE 58 IRC/Jabber
chatrooms, live webcasts and streamed session transcripts at:
http://www.ripe.net/ripe/meetings/ripe-58/live/
If you have any questions about remote participation at the RIPE 58
Meeting, please contact meeting@ripe.net.
Regards,
Camilla Meidell
Conference Coordinator
RIPE NCC
昨日から開催されているRIPEミーティングのリモート参加についてのお知らせ。
色々な議論が交わされるので必見かも。
自社/自分に不利な提案に対してはすぐに懸念表明をした方がいいですよ。
NANOG@May 4, 2009
Date: Mon, 4 May 2009 04:48:49 +0000 (UTC)
Subject: Re: [quagga-users 10587] bgpd crash - apologies (fwd)
On Mon, 4 May 2009, Ingo Flaschberger wrote:
> ---------- Forwarded message ----------
> Date: Mon, 04 May 2009 00:38:54 +0300
> Subject: [quagga-users 10587] bgpd crash - apologies
>
> Hello,
>
> I learned today that a BGP announcement for which I am the tech-c,
> is causing difficulties with Quagga. First of all, I apologise;
> it's only today that I heard about these difficulties.
[...]
A fix is here:
https://www.caputo.com/foss/quagga-0.99.10-BGP-4-byte-ASN-bug-fixes.patch
https://www.caputo.com/foss/quagga-0.99.11-BGP-4-byte-ASN-bug-fixes.patch
(the patches are identical. naming is just for clarity.)
Chris
各地で話題の4バイトAS下でのQuagga/BGPdクラッシュ話。
NANOGにもパッチ情報が。
Subject: Re: [quagga-users 10587] bgpd crash - apologies (fwd)
On Mon, 4 May 2009, Ingo Flaschberger wrote:
> ---------- Forwarded message ----------
> Date: Mon, 04 May 2009 00:38:54 +0300
> Subject: [quagga-users 10587] bgpd crash - apologies
>
> Hello,
>
> I learned today that a BGP announcement for which I am the tech-c,
> is causing difficulties with Quagga. First of all, I apologise;
> it's only today that I heard about these difficulties.
[...]
A fix is here:
https://www.caputo.com/foss/quagga-0.99.10-BGP-4-byte-ASN-bug-fixes.patch
https://www.caputo.com/foss/quagga-0.99.11-BGP-4-byte-ASN-bug-fixes.patch
(the patches are identical. naming is just for clarity.)
Chris
各地で話題の4バイトAS下でのQuagga/BGPdクラッシュ話。
NANOGにもパッチ情報が。
IETF-Digest@May 4, 2009
Date: Mon, 4 May 2009 16:02:47 -0400
From: "Richard Shockey"
Subject: How should ICANN spend its money ..
To: "'IETF Discussion'"
Message-ID: <01cb01c9ccf3$4c51d380$e4f57a80$@us>
Content-Type: text/plain; charset="US-ASCII"
Give it to the IETF obviously ...
http://blog.icann.org/2009/04/have-an-opinion-on-where-icann-should-spend-its-money/
Richard Shockey
ICANNの予算についてご意見ある方は当該ブログにコメントを。
From: "Richard Shockey"
Subject: How should ICANN spend its money ..
To: "'IETF Discussion'"
Message-ID: <01cb01c9ccf3$4c51d380$e4f57a80$@us>
Content-Type: text/plain; charset="US-ASCII"
Give it to the IETF obviously ...
http://blog.icann.org/2009/04/have-an-opinion-on-where-icann-should-spend-its-money/
Richard Shockey
ICANNの予算についてご意見ある方は当該ブログにコメントを。
AusNOG@May 4, 2009
date Mon, May 4, 2009 at 12:19 AM
subject [AusNOG] Quagga bgpd Crashes
Morning All,
Quagga users need to take a look at mailing list post
http://lists.quagga.net/pipermail/quagga-users/2009-April/010581.html in
regards to bgpd crashes as a result of 4 Byte ASN issues.
Despite the post advising the issue becoming apparent on April 30, this
has not only affected ourselves, but we know a number of other parties
over the last 6 hours, causing significant hell. A patch is available
from the above post.
Nick.
GTERでも話題になっていた4バイトAS下でのQuagga/Bgpdのクラッシュの件。
やはり各地で使われているのだな、と実感。
パッチもリリースされたのでまだまだQuaggaで戦える。
subject [AusNOG] Quagga bgpd Crashes
Morning All,
Quagga users need to take a look at mailing list post
http://lists.quagga.net/pipermail/quagga-users/2009-April/010581.html in
regards to bgpd crashes as a result of 4 Byte ASN issues.
Despite the post advising the issue becoming apparent on April 30, this
has not only affected ourselves, but we know a number of other parties
over the last 6 hours, causing significant hell. A patch is available
from the above post.
Nick.
GTERでも話題になっていた4バイトAS下でのQuagga/Bgpdのクラッシュの件。
やはり各地で使われているのだな、と実感。
パッチもリリースされたのでまだまだQuaggaで戦える。
5/04/2009
NNSquad@May 3, 2009
Date: Sun, 3 May 2009 18:59:08 -0700
Subject: [ NNSquad ] Sprint may outsource network to Ericsson
Sprint may outsource network to Ericsson
http://www.nytimes.com/reuters/2009/05/03/business/business-us-sprint.html
--Lauren--
Sprintはどうなってしまうのか。
Subject: [ NNSquad ] Sprint may outsource network to Ericsson
Sprint may outsource network to Ericsson
http://www.nytimes.com/reuters/2009/05/03/business/business-us-sprint.html
--Lauren--
Sprintはどうなってしまうのか。
5/02/2009
dns-operations@May 1, 2009
Date: Fri, 01 May 2009 07:03:48 -0500
Subject: [dns-operations] .gov has been re-inserted into dlv.isc.org
.gov has just been re-inserted into dlv.isc.org. Please report any
problems to dlv-registry@isc.org.
- --Michael
.govにDLVがインプリされた模様。
なにか問題を発見した方はご連絡を。
Subject: [dns-operations] .gov has been re-inserted into dlv.isc.org
.gov has just been re-inserted into dlv.isc.org. Please report any
problems to dlv-registry@isc.org.
- --Michael
.govにDLVがインプリされた模様。
なにか問題を発見した方はご連絡を。
NANOG@May 1, 2009
Date: Fri, 01 May 2009 11:35:00 -0700
Subject: Re: Where to buy Internet IP addresses
LEdouard Louis wrote:
> Optimum Online business only offer 5 static IP address.
>
>
>
> Where can I buy a block of Internet IP address for Business? How much
> does it cost?
>
>
>
> Most of our devices only require an internal IP address to reach the
> internet, but we have a Juniper DX for load balancing.
>
>
>
> We must provide Juniper DX with an internet IP address and point it to
> internal IP address for customers to be able to reach it from the
> internet. this is for testing and development purposes and will expect
> several servers on Load-balancer. The 5 static IP addresses just won't
> be enough.
>
Get a different ISP. You can't "buy addresses." You can apply to your
RIR for addresses, but it sounds like you wouldn't qualify if your price
range is 5 statics from your ISP. Also see huge debate on arin-ppml
about buying and selling addresses.
~Seth
ネタにマジレス？
しかしこういうメールが増えてくるのかもしれないなぁと妄想。
Subject: Re: Where to buy Internet IP addresses
LEdouard Louis wrote:
> Optimum Online business only offer 5 static IP address.
>
>
>
> Where can I buy a block of Internet IP address for Business? How much
> does it cost?
>
>
>
> Most of our devices only require an internal IP address to reach the
> internet, but we have a Juniper DX for load balancing.
>
>
>
> We must provide Juniper DX with an internet IP address and point it to
> internal IP address for customers to be able to reach it from the
> internet. this is for testing and development purposes and will expect
> several servers on Load-balancer. The 5 static IP addresses just won't
> be enough.
>
Get a different ISP. You can't "buy addresses." You can apply to your
RIR for addresses, but it sounds like you wouldn't qualify if your price
range is 5 statics from your ISP. Also see huge debate on arin-ppml
about buying and selling addresses.
~Seth
ネタにマジレス？
しかしこういうメールが増えてくるのかもしれないなぁと妄想。
5/01/2009
GTER@Apr 30, 2009
Date: Thu, 30 Apr 2009 10:18:41 -0300
Subject: Re: [GTER] Quagga - Assertion `len < str_size' failed in
filebgp_aspath.c, line 619
> Caros amigos, CASO algum de voces tenha o problema abaixo com o Quagga
> (Bgpd crash on long asn32 in aspath):
> Assertion `len < str_size' failed in file bgp_aspath.c, line 619
>
> Aconselho o link abaixo:
> http://www.gossamer-threads.com/lists/quagga/users/17769
>
> Para mim funcionou 100%
Ola
Este ? o bug do quagga de umas 3 semanas atr?s, voc? s? foi atingido
agora? Ou s? precisou agora?
Um upgrade pro quagga 0.99-11 ou downgrade pro 0.98-6 resolve a
parada, se preferir n?o patchear manualmente
[]s, !3runo Cabral
4バイトASのうち、非常に大きいAS番号を使うとQuaggaのBGPdがクラッシュしてしまう、という相談に、0.99-11にアップグレードするか、0.98-6にダウングレードすればいい。パッチは自分で当ててね、という返答。
Quaggaは非常に活発に開発が進んでいるOSS。開発状況を追うのは大変だ。
Subject: Re: [GTER] Quagga - Assertion `len < str_size' failed in
filebgp_aspath.c, line 619
> Caros amigos, CASO algum de voces tenha o problema abaixo com o Quagga
> (Bgpd crash on long asn32 in aspath):
> Assertion `len < str_size' failed in file bgp_aspath.c, line 619
>
> Aconselho o link abaixo:
> http://www.gossamer-threads.com/lists/quagga/users/17769
>
> Para mim funcionou 100%
Ola
Este ? o bug do quagga de umas 3 semanas atr?s, voc? s? foi atingido
agora? Ou s? precisou agora?
Um upgrade pro quagga 0.99-11 ou downgrade pro 0.98-6 resolve a
parada, se preferir n?o patchear manualmente
[]s, !3runo Cabral
4バイトASのうち、非常に大きいAS番号を使うとQuaggaのBGPdがクラッシュしてしまう、という相談に、0.99-11にアップグレードするか、0.98-6にダウングレードすればいい。パッチは自分で当ててね、という返答。
Quaggaは非常に活発に開発が進んでいるOSS。開発状況を追うのは大変だ。
ARIN-ppml@Apr 30, 2009
Date: Thu, 30 Apr 2009 18:10:50 -0400
Subject: [arin-ppml] Effect of ARIN's Letters
ARIN's letters are getting some attention:
http://tech.slashdot.org/article.pl?sid=09/04/30/2051235
--
Leo Bicknell
ARINから出たレターが本家Slashdotで話題になっています。
以前から議論されていたことですが、ようやくGeeks～一般人の話題に落ちてきたという感じ。
ま、本当の一般人はどうでもいいことなんでしょうけど。
地デジも各国延期みたいだし、期限を切った告知は難しいですね。
Subject: [arin-ppml] Effect of ARIN's Letters
ARIN's letters are getting some attention:
http://tech.slashdot.org/article.pl?sid=09/04/30/2051235
--
Leo Bicknell
ARINから出たレターが本家Slashdotで話題になっています。
以前から議論されていたことですが、ようやくGeeks～一般人の話題に落ちてきたという感じ。
ま、本当の一般人はどうでもいいことなんでしょうけど。
地デジも各国延期みたいだし、期限を切った告知は難しいですね。
4/30/2009
GTER@Apr 29, 2009
Date: Wed, 29 Apr 2009 13:16:40 -0300
Subject: Re: [GTER] MPLS para Linux
Ol?,
Comece por aqui:
http://apps.sourceforge.net/mediawiki/mpls-linux/index.php?title=Main_Page
Abs,
> Boa Tarde a Todos,
>
> Algu?m poderia indicar algum material sobre MPLS para Linux ?
>
> Grato desde j? pela aten??o.
>
>
> Att,
LinuxでMPLS使えないかな？という質問に返事あり。
MPLS-Linuxというものがあるそうです。
日本人ならNetBSD+Ayameだよね？と思うのだけれど。
Subject: Re: [GTER] MPLS para Linux
Ol?,
Comece por aqui:
http://apps.sourceforge.net/mediawiki/mpls-linux/index.php?title=Main_Page
Abs,
> Boa Tarde a Todos,
>
> Algu?m poderia indicar algum material sobre MPLS para Linux ?
>
> Grato desde j? pela aten??o.
>
>
> Att,
LinuxでMPLS使えないかな？という質問に返事あり。
MPLS-Linuxというものがあるそうです。
日本人ならNetBSD+Ayameだよね？と思うのだけれど。
4/29/2009
RIPE-list@Apr 28, 2009
Date: Tue, 28 Apr 2009 18:27:09 +0200
Subject: ASO AC selects Ray Plzak to serve on Seat 9 of ICANN Board of Directors
Dear Colleagues
The ASO is pleased to announce that the ASO Address Council has selected
Ray Plzak to serve for a three-year term on Seat 9 of the ICANN Board of
Directors. Mr Plzak's term will begin on 7 May 2009.
The ASO congratulates Mr Plzak and would also like to thank the other
four candidates who took part in the selection process:
- Rajesh Chharia
- Jordi Palet Martinez
- Barry Shein
- Suzanne Woolf
Mr Plzak's appointment follows a lengthy selection process, including a
public call for nominations, interviews with eligible candidates, a
public comment period and a vote by all ASO Address Council members. The
Address Council confirmed the result at their meeting on 22 April 2009.
Full details of the process, including information on all eligible
candidates, are available on the ASO web site at:
http://www.aso.icann.org/elections
Best regards,
ASO Secretariat
前ARINのPresident Mr.Ray PlzakがICANN Board of Directorsに選出された、という報告。
Rayは隠居ではなかったんだな。
Subject: ASO AC selects Ray Plzak to serve on Seat 9 of ICANN Board of Directors
Dear Colleagues
The ASO is pleased to announce that the ASO Address Council has selected
Ray Plzak to serve for a three-year term on Seat 9 of the ICANN Board of
Directors. Mr Plzak's term will begin on 7 May 2009.
The ASO congratulates Mr Plzak and would also like to thank the other
four candidates who took part in the selection process:
- Rajesh Chharia
- Jordi Palet Martinez
- Barry Shein
- Suzanne Woolf
Mr Plzak's appointment follows a lengthy selection process, including a
public call for nominations, interviews with eligible candidates, a
public comment period and a vote by all ASO Address Council members. The
Address Council confirmed the result at their meeting on 22 April 2009.
Full details of the process, including information on all eligible
candidates, are available on the ASO web site at:
http://www.aso.icann.org/elections
Best regards,
ASO Secretariat
前ARINのPresident Mr.Ray PlzakがICANN Board of Directorsに選出された、という報告。
Rayは隠居ではなかったんだな。
ARIN-PPML@Apr 28, 2009
Date: Tue, 28 Apr 2009 15:45:40 -0400
Subject: [arin-ppml] RIPE Policy 2008-03 (May be useful about ARIN
2009-02)
Several speakers at the meeting spoke about reducing the timeperiod for
allocations from 12 months to some lower number. RIPE policy 2009-03
attempts to do this, in the RIPE region.
The RIPE policy is at
http://ripe.net/ripe/policies/proposals/2009-03.html if anyone wants to
read it.
--
Leo Bicknell
当たり前だが全世界で波及するようなポリシーを議論する際、
隣の地域でも大体同じような提案が既に出ていることがあり、議論も集約しつつある場合もある。今回もそういう例。
ARINではなぜか車輪の再発明的な議論が多く巻き起こる気がするが、多くの人が隣の地域の議論を
注視していないからかも。
Subject: [arin-ppml] RIPE Policy 2008-03 (May be useful about ARIN
2009-02)
Several speakers at the meeting spoke about reducing the timeperiod for
allocations from 12 months to some lower number. RIPE policy 2009-03
attempts to do this, in the RIPE region.
The RIPE policy is at
http://ripe.net/ripe/policies/proposals/2009-03.html if anyone wants to
read it.
--
Leo Bicknell
当たり前だが全世界で波及するようなポリシーを議論する際、
隣の地域でも大体同じような提案が既に出ていることがあり、議論も集約しつつある場合もある。今回もそういう例。
ARINではなぜか車輪の再発明的な議論が多く巻き起こる気がするが、多くの人が隣の地域の議論を
注視していないからかも。
Outages@Apr 28, 2009
date Tue, Apr 28, 2009 at 6:45 AM
subject Re: [outages] Phoenix Area Network Issues?
There's a ton of chatter about it on the NANOG list now.
Apparently there were some issues with a major AT&T route.
SBC Issues were also reported, this was all about an hour ago.
> In Phoenix here and our XO T1s, Sprint mpls and Internet connection,
> and XO microwave connection are working fine. Cox cable Internet here
> and in Tempe seems fine as well. Where are you experiencing outages?
>
> _____
>
> C. Lauretano
>
>
> > Are there any fiber cuts or other routing issues anyone in the Phoenix
> > area is aware of?
> >
> >
> > Thanks.
フェニックス地域で経路障害発生。
NANOGでも話題に。AT&Tがんばれ。
今はどんな障害でもファイバーカット？と聞くのが定番に？
subject Re: [outages] Phoenix Area Network Issues?
There's a ton of chatter about it on the NANOG list now.
Apparently there were some issues with a major AT&T route.
SBC Issues were also reported, this was all about an hour ago.
> In Phoenix here and our XO T1s, Sprint mpls and Internet connection,
> and XO microwave connection are working fine. Cox cable Internet here
> and in Tempe seems fine as well. Where are you experiencing outages?
>
> _____
>
> C. Lauretano
>
>
> > Are there any fiber cuts or other routing issues anyone in the Phoenix
> > area is aware of?
> >
> >
> > Thanks.
フェニックス地域で経路障害発生。
NANOGでも話題に。AT&Tがんばれ。
今はどんな障害でもファイバーカット？と聞くのが定番に？
4/28/2009
LACNIC-politicas@Apr 27, 2009
Date: Mon, 27 Apr 2009 16:49:04 -0300
Subject: [LACNIC/Politicas] Summary week of 20th to 26th April 2009 -
Sum?rio das discuss?es semana de 20 a 26 de abril - Resumen
discusiones seman del 20 al 26 de abril
- - ---------------
Portugu?s a continua??o
Espa?ol a continuaci?n.
- - ---------------
(English)
Abstract discussions happened on the Public Policy mailing list on the
week from the 20th to the 26th April.
[LAC-2009-04] Transfer of IPv4 blocks in the LACNIC region.
The debate referring to this policy continued. You can find the
complete policy text at:
http://www.lacnic.net/documentos/politicas/LAC-2009-04-propuesta-en.pdf
Here is an abstract of the comments on the mailing list:
[Christian O'Flaherty - 18 Abril 2009 - recap] ?Would this mean that
the entity that originated the transfer does not need to perform any
previous process? Will everything be the responsibility of the entity
that received the transfer?"
[Francisco Arias - 20 Abril 2009] "In general yes. However the
following is referred in a previous bullet:
2.3.18.4.- Upon receiving an IPv4 address block transfer request,
LACNIC shall verify that the entity transferring the block is in fact
the holder of said block and that no disputes exist in relation to
said block."
～ポルトガル語・スペイン語版は略～
ここのところLACNICのサマリ送出間隔が狭くなってきている気がする。
年に一度の会議を前に気合が見えます。
しかし新型インフルエンザがARIN/RIPE/AfriNIC/LACNICの会議シーズン直撃ですね。
参加者はくれぐれも気をつけてください。
Subject: [LACNIC/Politicas] Summary week of 20th to 26th April 2009 -
Sum?rio das discuss?es semana de 20 a 26 de abril - Resumen
discusiones seman del 20 al 26 de abril
- - ---------------
Portugu?s a continua??o
Espa?ol a continuaci?n.
- - ---------------
(English)
Abstract discussions happened on the Public Policy mailing list on the
week from the 20th to the 26th April.
[LAC-2009-04] Transfer of IPv4 blocks in the LACNIC region.
The debate referring to this policy continued. You can find the
complete policy text at:
http://www.lacnic.net/documentos/politicas/LAC-2009-04-propuesta-en.pdf
Here is an abstract of the comments on the mailing list:
[Christian O'Flaherty - 18 Abril 2009 - recap] ?Would this mean that
the entity that originated the transfer does not need to perform any
previous process? Will everything be the responsibility of the entity
that received the transfer?"
[Francisco Arias - 20 Abril 2009] "In general yes. However the
following is referred in a previous bullet:
2.3.18.4.- Upon receiving an IPv4 address block transfer request,
LACNIC shall verify that the entity transferring the block is in fact
the holder of said block and that no disputes exist in relation to
said block."
～ポルトガル語・スペイン語版は略～
ここのところLACNICのサマリ送出間隔が狭くなってきている気がする。
年に一度の会議を前に気合が見えます。
しかし新型インフルエンザがARIN/RIPE/AfriNIC/LACNICの会議シーズン直撃ですね。
参加者はくれぐれも気をつけてください。
AusNOG@Apr 27, 2009
date Mon, Apr 27, 2009 at 2:31 PM
subject [AusNOG] Traffic Levels
One conclusion, the Sweeds are very law abiding ...
http://www.circleid.com/posts/sweden_internet_traffic_drop_anti_piracy_law/
Netnod's stats page ....
http://stats.autonomica.se/mrtg/sums/All.html
スウェーデン政府が著作権違反に関する法律を整備したところ、トラフィックが下がったというニュース。
世界は制限の方向へと向かっている。
#今までが無法地帯だったとも言える。
subject [AusNOG] Traffic Levels
One conclusion, the Sweeds are very law abiding ...
http://www.circleid.com/posts/sweden_internet_traffic_drop_anti_piracy_law/
Netnod's stats page ....
http://stats.autonomica.se/mrtg/sums/All.html
スウェーデン政府が著作権違反に関する法律を整備したところ、トラフィックが下がったというニュース。
世界は制限の方向へと向かっている。
#今までが無法地帯だったとも言える。
4/27/2009
NNSquad@Apr 26, 2009
Date: Sun, 26 Apr 2009 11:25:04 +0200 (CEST)
Subject: [ NNSquad ] nnsquad - filtering not only in asia
Hi,
more and more filtering is getting a topic in EU or other more
"democratic" regions than china & Co....
Now Germany signed a law
http://www.theregister.co.uk/2009/04/23/germany_image_law/
how will be the EU Region influenced? What do you think?
Will the big Filtering Areas work together or will there a competion
politic and the seems of code, products and methods be established?
sharing vs. competion market?
Hopefully getting some minds and new points to other lists about this...
ch
ドイツでもインターネット検閲法案が通った？
BigBrotherの支配するSFな世界に向かうのか？！
Subject: [ NNSquad ] nnsquad - filtering not only in asia
Hi,
more and more filtering is getting a topic in EU or other more
"democratic" regions than china & Co....
Now Germany signed a law
http://www.theregister.co.uk/2009/04/23/germany_image_law/
how will be the EU Region influenced? What do you think?
Will the big Filtering Areas work together or will there a competion
politic and the seems of code, products and methods be established?
sharing vs. competion market?
Hopefully getting some minds and new points to other lists about this...
ch
ドイツでもインターネット検閲法案が通った？
BigBrotherの支配するSFな世界に向かうのか？！
cisco-nsp@Apr 26, 2009
Date: Sun, 26 Apr 2009 23:23:44 +0200
Subject: Re: [c-nsp] 6500 sup720-3bxl crash
Hmmm ... same today morning !?
Cache error detected!
CPO_ECC (reg 26/0): 0x0000009F
CPO_CACHERI (reg 27/0): 0xA0000000
CP0_CAUSE (reg 13/0): 0x00000800
Real cache error detected. System will be halted.
Error: Primary data cache, fields: data,
Actual physical addr 0x00000000,
virtual address is imprecise.
Imprecise Data Parity Error
Imprecise Data Parity Error
Interrupt exception, CPU signal 20, PC = 0x40E7BE6C
========= Start of Crashinfo Collection (07:05:17 GMT Sun Apr 26 2009) =========
IOS (tm) s72033_sp Software (s72033_sp-IPSERVICESK9-M), Version 12.2(18)SXF14, RELEASE SOFTWARE (fc1)
On Sun, Apr 26, 2009 at 01:13:05PM -0700, John van Oppen wrote:
> Has anyone seen this reload cause before? Sounds like bad memory but
> the memory addresses are pretty non machine sounding some I am wondering
> if it is a software bug.
>
>
> Cache error detected!
> CPO_ECC (reg 26/0): 0x000000F3
> CPO_CACHERI (reg 27/0): 0x84000000
> CP0_CAUSE (reg 13/0): 0x00004400
>
> Real cache error detected. System will be halted.
>
> Error: Primary data cache, fields: , 1st dword
> Actual physical addr 0x00000000,
> virtual address is imprecise.
>
> Imprecise Data Parity Error
>
>
> Software version is: s72033_sp-ADVIPSERVICESK9_WAN-M), Version
> 12.2(33)SXI, RELEASE SOFTWARE (fc2)
>
>
> Thanks,
> John
同時多発でCatalyst6500+Sup720-3BXLに問題発生か。
日本にもいっぱい入ってるんじゃないかな？大丈夫なのかな？
Subject: Re: [c-nsp] 6500 sup720-3bxl crash
Hmmm ... same today morning !?
Cache error detected!
CPO_ECC (reg 26/0): 0x0000009F
CPO_CACHERI (reg 27/0): 0xA0000000
CP0_CAUSE (reg 13/0): 0x00000800
Real cache error detected. System will be halted.
Error: Primary data cache, fields: data,
Actual physical addr 0x00000000,
virtual address is imprecise.
Imprecise Data Parity Error
Imprecise Data Parity Error
Interrupt exception, CPU signal 20, PC = 0x40E7BE6C
========= Start of Crashinfo Collection (07:05:17 GMT Sun Apr 26 2009) =========
IOS (tm) s72033_sp Software (s72033_sp-IPSERVICESK9-M), Version 12.2(18)SXF14, RELEASE SOFTWARE (fc1)
On Sun, Apr 26, 2009 at 01:13:05PM -0700, John van Oppen wrote:
> Has anyone seen this reload cause before? Sounds like bad memory but
> the memory addresses are pretty non machine sounding some I am wondering
> if it is a software bug.
>
>
> Cache error detected!
> CPO_ECC (reg 26/0): 0x000000F3
> CPO_CACHERI (reg 27/0): 0x84000000
> CP0_CAUSE (reg 13/0): 0x00004400
>
> Real cache error detected. System will be halted.
>
> Error: Primary data cache, fields: , 1st dword
> Actual physical addr 0x00000000,
> virtual address is imprecise.
>
> Imprecise Data Parity Error
>
>
> Software version is: s72033_sp-ADVIPSERVICESK9_WAN-M), Version
> 12.2(33)SXI, RELEASE SOFTWARE (fc2)
>
>
> Thanks,
> John
同時多発でCatalyst6500+Sup720-3BXLに問題発生か。
日本にもいっぱい入ってるんじゃないかな？大丈夫なのかな？
4/25/2009
NNSquad@Apr 24, 2009
Date: Fri, 24 Apr 2009 07:20:37 -0400 (EDT)
Subject: [ NNSquad ] Big boost for Aussie firewall
http://www.theregister.co.uk/2009/04/23/aussie_firewall_boost/
Big boost for Aussie firewall
The controversial Great Aussie Firewall got a big boost yesterday when
Australia's second largest ISP Optus agreed to join the pilot.
snip
近年、オーストラリアって中国と仲いいよね。
金盾をも真似るのかな？
2番目に大きいISPがそのプロジェクトに加わったとすると、確かに加速が付きそう。
やばい。
Subject: [ NNSquad ] Big boost for Aussie firewall
http://www.theregister.co.uk/2009/04/23/aussie_firewall_boost/
Big boost for Aussie firewall
The controversial Great Aussie Firewall got a big boost yesterday when
Australia's second largest ISP Optus agreed to join the pilot.
snip
近年、オーストラリアって中国と仲いいよね。
金盾をも真似るのかな？
2番目に大きいISPがそのプロジェクトに加わったとすると、確かに加速が付きそう。
やばい。
4/24/2009
LACNIC-politicas@Apr 23, 2009
Date: Thu, 23 Apr 2009 13:25:53 -0300
Subject: [LACNIC/Politicas] Summary week of 13th to 19th April 2009 -
Sum?rio das discuss?es semana de 13 a 19 de abril - Resumen
discusiones seman del 13 al 19 de abril
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Portugu?s a continua??o
Espa?ol a continuaci?n.
- ---------------
(English)
Abstract LACNIC Public Policy Mailing list discussion - week of 13th
to 19th April 2009.
[LAC-2009-04] Transfer of IPv4 blocks in the LACNIC region.
The debate referring to this policy continued.
You can find the complete policy text at: http://www.lacnic.net/documentos/politicas/LAC-2009-04-propuesta-en.pdf
Here is an abstract of the comments on the mailing list:
[Christian O'Flaherty - 16th April 2009] - ?What about the legacy
space? These blocks were allocated previously to the creation of the
RIRs, are they included in this policy??
[Francisco Arias - 17th April 2009] - "We did not considered
explicitly the legacy resources, but I believe that the idea would be
for them to be subject to transfers. However, when transferred they
should stop being legacy resources?
[Francisco Arias - 18th April 2009] - ?The last point in policy
proposal states: 2.3.2.18.9 - The receiving entity must comply with
all LACNIC policies in force , this point will have the effect that I
was mentioning. ?
[Christian O'Flaherty - 18th April 2009] - ?Would this mean that the
entity that originated the transfer do not need to perform any
previous process? Will everything be the responsibility of the entity
that received the transfer?
～スペイン語版とポルトガル語版は略～
LACNICMeeting前なので積極的にまとめが出されています。
LACNICは年一回のMeetingなのでここで決めたいでしょうからね。
Subject: [LACNIC/Politicas] Summary week of 13th to 19th April 2009 -
Sum?rio das discuss?es semana de 13 a 19 de abril - Resumen
discusiones seman del 13 al 19 de abril
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Portugu?s a continua??o
Espa?ol a continuaci?n.
- ---------------
(English)
Abstract LACNIC Public Policy Mailing list discussion - week of 13th
to 19th April 2009.
[LAC-2009-04] Transfer of IPv4 blocks in the LACNIC region.
The debate referring to this policy continued.
You can find the complete policy text at: http://www.lacnic.net/documentos/politicas/LAC-2009-04-propuesta-en.pdf
Here is an abstract of the comments on the mailing list:
[Christian O'Flaherty - 16th April 2009] - ?What about the legacy
space? These blocks were allocated previously to the creation of the
RIRs, are they included in this policy??
[Francisco Arias - 17th April 2009] - "We did not considered
explicitly the legacy resources, but I believe that the idea would be
for them to be subject to transfers. However, when transferred they
should stop being legacy resources?
[Francisco Arias - 18th April 2009] - ?The last point in policy
proposal states: 2.3.2.18.9 - The receiving entity must comply with
all LACNIC policies in force , this point will have the effect that I
was mentioning. ?
[Christian O'Flaherty - 18th April 2009] - ?Would this mean that the
entity that originated the transfer do not need to perform any
previous process? Will everything be the responsibility of the entity
that received the transfer?
～スペイン語版とポルトガル語版は略～
LACNICMeeting前なので積極的にまとめが出されています。
LACNICは年一回のMeetingなのでここで決めたいでしょうからね。
RIPE-announce@Apr 23, 2009
Date: Thu, 23 Apr 2009 09:53:10 +0200
Subject: [policy-announce] 2009-02 Discussion Period extended until 21 May 2009 (Allocating/Assigning Resources to the RIPE NCC)
PDP Number: 2009-02
Allocating/Assigning Resources to the RIPE NCC
Dear Colleagues,
The text of the policy proposal 2009-02 has been revised based on the community feedback received
on the mailing list.
We have published the new version (version 2) today.
As a result a new Discussion Phase is set for the proposal.
You can find the full proposal at:
http://www.ripe.net/ripe/policies/proposals/2009-02.html
We encourage you to review this policy proposal and send your comments
to address-policy-wg@ripe.net before 21 May 2009.
Regards,
Ingrid Wijte
Policy Development Officer
RIPE NCC
RIPE NCCも2009-2をRevise/Updateして再びコメント募集期間を設定しました。
春のRIPEMeetingでなんとしても纏めたいという意気込みが見えます。
#それはARINも同じだが、あっちはなんだかこじれた感がある。
Subject: [policy-announce] 2009-02 Discussion Period extended until 21 May 2009 (Allocating/Assigning Resources to the RIPE NCC)
PDP Number: 2009-02
Allocating/Assigning Resources to the RIPE NCC
Dear Colleagues,
The text of the policy proposal 2009-02 has been revised based on the community feedback received
on the mailing list.
We have published the new version (version 2) today.
As a result a new Discussion Phase is set for the proposal.
You can find the full proposal at:
http://www.ripe.net/ripe/policies/proposals/2009-02.html
We encourage you to review this policy proposal and send your comments
to address-policy-wg@ripe.net before 21 May 2009.
Regards,
Ingrid Wijte
Policy Development Officer
RIPE NCC
RIPE NCCも2009-2をRevise/Updateして再びコメント募集期間を設定しました。
春のRIPEMeetingでなんとしても纏めたいという意気込みが見えます。
#それはARINも同じだが、あっちはなんだかこじれた感がある。
PacNOG@Apr 23, 2009
Date: Thu, 23 Apr 2009 00:34:05 +1300
Subject: [pacnog] IPTV
Hi,
Anyone with experience in implementing IPTv service in the pacific? I am
looking for information on equipments, etc and the likely cost involved.
Kind Regards,
TCC/ENG/I.T/Siumafua Moala
KaliaNet Services
Tonga Communications Corporation
太平洋地域でのIPTVの導入事例を探しているようです。
Yahoo!JapanはGyaoのシステムを安く譲ってあげればいいのに。もしくはYahoo!動画のシステムでも。
Subject: [pacnog] IPTV
Hi,
Anyone with experience in implementing IPTv service in the pacific? I am
looking for information on equipments, etc and the likely cost involved.
Kind Regards,
TCC/ENG/I.T/Siumafua Moala
KaliaNet Services
Tonga Communications Corporation
太平洋地域でのIPTVの導入事例を探しているようです。
Yahoo!JapanはGyaoのシステムを安く譲ってあげればいいのに。もしくはYahoo!動画のシステムでも。
4/23/2009
dns-operations@Apr 22, 2009
Date: Wed, 22 Apr 2009 21:31:01 +0100
Subject: [dns-operations] Cache Poisoning Attacks
Seems there were a couple of fairly high profile cache poisoning
attacks today. Thought some of you might be interested.
http://www.theregister.co.uk/2009/04/22/bandesco_cache_poisoning_attack/
http://www.theregister.co.uk/2009/04/22/msn_hijacking/
More fuel for the dnssec fire.
Brett
キャッシュポイズンによる攻撃についてのニュース2件。
これがdnssec普及へのガソリンになるか、どうか。
Subject: [dns-operations] Cache Poisoning Attacks
Seems there were a couple of fairly high profile cache poisoning
attacks today. Thought some of you might be interested.
http://www.theregister.co.uk/2009/04/22/bandesco_cache_poisoning_attack/
http://www.theregister.co.uk/2009/04/22/msn_hijacking/
More fuel for the dnssec fire.
Brett
キャッシュポイズンによる攻撃についてのニュース2件。
これがdnssec普及へのガソリンになるか、どうか。
NNSquad@Apr 22, 2009
Date: Wed, 22 Apr 2009 12:02:02 -0700
Subject: [ NNSquad ] Amazon launches HD video service
----- Forwarded message from "Amazon.com" -----
Date: Wed, 22 Apr 2009 11:59:12 -0700 (PDT)
From: "Amazon.com"
Subject: Instant HD Is Here with Amazon Video On Demand
Instant HD with Amazon Video On Demand
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_1/?ie=UTF8&docId=1000364351
Dear Amazon.com Customer,
As a valued Amazon Video On Demand customer, we'd like to let you know that you can now watch over 500 TV shows and movies in crystal-clear, eye-popping HD ( http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_2/?ie=UTF8&docId=1000364351 ). Watch HD TV shows online on Macs or PCs, or on your TV through your TiVo DVR, Roku Digital Video Player, compatible Sony Bravia and Panasonic Viera HDTV's. You can also download to your PC for $2.99 per episode. Rent HD movies directly from your TV through the same compatible devices for $4.99 or less.
See all HD content
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_3/?ie=UTF8&docId=1000364351
--------------------------------
Hit TV Shows: Even Better in HD
--------------------------------
Heroes Season 3 [HD] ( http://www.amazon.com/gp/product/B001T58QWY/ref=pe_11888060_txt_4/ )
The Tudors Season 2 [HD] ( http://www.amazon.com/gp/product/B0025WX2YW/ref=pe_11888060_txt_5/ )
Supernatural Season 4 [HD] ( http://www.amazon.com/gp/product/B001UG13IG/ref=pe_11888060_txt_6/ )
Terminator: The Sarah Connor Chronicles Season 2 [HD] ( http://www.amazon.com/gp/product/B001V6SEY6/ref=pe_11888060_txt_7/ )
Fringe Season 1 [HD] ( http://www.amazon.com/gp/product/B001UTW7QU/ref=pe_11888060_txt_8/ )
Battlestar Galactica Season 4 [HD] ( http://www.amazon.com/gp/product/B001LZZ2DS/ref=pe_11888060_txt_9/ )
See all available HD shows
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_10/?ie=UTF8&docId=1000364351
-----------------------------------------------
Order New Release Movies Right from Your Couch
-----------------------------------------------
Roku Digital Video Player ( http://www.amazon.com/gp/product/B001PIBE8I/ref=pe_11888060_txt_11/ )
TiVo Series3, HD, and HD XL DVRs ( http://www.amazon.com/gp/browse.html/ref=pe_11888060_txt_12/?node=160759011 )
Panasonic Viera HDTVs ( http://www.amazon.com/s/node=172282&hidden-keywords=B001UAEWUS|B001UAB40E|B001UAEWSU/ref=pe_11888060_txt_13/ )
Sony Bravia Internet Video Link ( http://www.amazon.com/gp/product/B000RFURG0/ref=pe_11888060_txt_14/ )
See all ways to watch on your TV
http://www.amazon.com/gp/video/ontv/ref=pe_11888060_txt_15/
----- End forwarded message -----
AmazonがHDクオリティのVideo On Demandサービスを開始らしい。
この動画を見ている人は下記の動画も見ています、とかリコメンドしてくれるのかな(笑)
Subject: [ NNSquad ] Amazon launches HD video service
----- Forwarded message from "Amazon.com"
Date: Wed, 22 Apr 2009 11:59:12 -0700 (PDT)
From: "Amazon.com"
Subject: Instant HD Is Here with Amazon Video On Demand
Instant HD with Amazon Video On Demand
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_1/?ie=UTF8&docId=1000364351
Dear Amazon.com Customer,
As a valued Amazon Video On Demand customer, we'd like to let you know that you can now watch over 500 TV shows and movies in crystal-clear, eye-popping HD ( http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_2/?ie=UTF8&docId=1000364351 ). Watch HD TV shows online on Macs or PCs, or on your TV through your TiVo DVR, Roku Digital Video Player, compatible Sony Bravia and Panasonic Viera HDTV's. You can also download to your PC for $2.99 per episode. Rent HD movies directly from your TV through the same compatible devices for $4.99 or less.
See all HD content
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_3/?ie=UTF8&docId=1000364351
--------------------------------
Hit TV Shows: Even Better in HD
--------------------------------
Heroes Season 3 [HD] ( http://www.amazon.com/gp/product/B001T58QWY/ref=pe_11888060_txt_4/ )
The Tudors Season 2 [HD] ( http://www.amazon.com/gp/product/B0025WX2YW/ref=pe_11888060_txt_5/ )
Supernatural Season 4 [HD] ( http://www.amazon.com/gp/product/B001UG13IG/ref=pe_11888060_txt_6/ )
Terminator: The Sarah Connor Chronicles Season 2 [HD] ( http://www.amazon.com/gp/product/B001V6SEY6/ref=pe_11888060_txt_7/ )
Fringe Season 1 [HD] ( http://www.amazon.com/gp/product/B001UTW7QU/ref=pe_11888060_txt_8/ )
Battlestar Galactica Season 4 [HD] ( http://www.amazon.com/gp/product/B001LZZ2DS/ref=pe_11888060_txt_9/ )
See all available HD shows
http://www.amazon.com/gp/feature.html/ref=pe_11888060_txt_10/?ie=UTF8&docId=1000364351
-----------------------------------------------
Order New Release Movies Right from Your Couch
-----------------------------------------------
Roku Digital Video Player ( http://www.amazon.com/gp/product/B001PIBE8I/ref=pe_11888060_txt_11/ )
TiVo Series3, HD, and HD XL DVRs ( http://www.amazon.com/gp/browse.html/ref=pe_11888060_txt_12/?node=160759011 )
Panasonic Viera HDTVs ( http://www.amazon.com/s/node=172282&hidden-keywords=B001UAEWUS|B001UAB40E|B001UAEWSU/ref=pe_11888060_txt_13/ )
Sony Bravia Internet Video Link ( http://www.amazon.com/gp/product/B000RFURG0/ref=pe_11888060_txt_14/ )
See all ways to watch on your TV
http://www.amazon.com/gp/video/ontv/ref=pe_11888060_txt_15/
----- End forwarded message -----
AmazonがHDクオリティのVideo On Demandサービスを開始らしい。
この動画を見ている人は下記の動画も見ています、とかリコメンドしてくれるのかな(笑)
RIPE-announce@Apr 22, 2009
Date: Wed, 22 Apr 2009 11:31:07 +0200
Subject: [policy-announce] 2006-01 Proposal Accepted (Provider Independent (PI) IPv6 Assignments for End User Organisations)
PDP Number: 2006-01
Provider Independent (PI) IPv6 Assignments for End User Organisations
Dear Colleagues,
Consensus has been reached, and the proposal described in 2006-01,
"Provider Independent (PI) IPv6 Assignments for End User
Organisations" has been accepted by the RIPE community.
The related RIPE policy document is now updated, published and can
be found at:
http://www.ripe.net/ripe/docs/ripe-466.html
or
http://www.ripe.net/ripe/docs/ipv6-policies.html
The proposal is now archived and can be found at:
http://www.ripe.net/ripe/policies/proposals/2006-01.html
The RIPE NCC will implement this new policy within one month.
Thank you for your input.
Regards
Filiz Yilmaz
Policy Development Officer
RIPE NCC
欧州地域でIPv6のプロバイダ非依存アドレスの割当てに関して導入された報告。
欧州地域はIPv6アドレスの取得が進んでいる地域。
しかしIPv6独自のサービスはまだ見えてこない。移行という話も聞こえてこない。
これをきっかけにIPv6の普及が進むか。
Subject: [policy-announce] 2006-01 Proposal Accepted (Provider Independent (PI) IPv6 Assignments for End User Organisations)
PDP Number: 2006-01
Provider Independent (PI) IPv6 Assignments for End User Organisations
Dear Colleagues,
Consensus has been reached, and the proposal described in 2006-01,
"Provider Independent (PI) IPv6 Assignments for End User
Organisations" has been accepted by the RIPE community.
The related RIPE policy document is now updated, published and can
be found at:
http://www.ripe.net/ripe/docs/ripe-466.html
or
http://www.ripe.net/ripe/docs/ipv6-policies.html
The proposal is now archived and can be found at:
http://www.ripe.net/ripe/policies/proposals/2006-01.html
The RIPE NCC will implement this new policy within one month.
Thank you for your input.
Regards
Filiz Yilmaz
Policy Development Officer
RIPE NCC
欧州地域でIPv6のプロバイダ非依存アドレスの割当てに関して導入された報告。
欧州地域はIPv6アドレスの取得が進んでいる地域。
しかしIPv6独自のサービスはまだ見えてこない。移行という話も聞こえてこない。
これをきっかけにIPv6の普及が進むか。
4/22/2009
ARIN-announce@Apr 21, 2009
Date: Tuesday, 21 April 2009 6:28 AM
Subject: [arin-announce] ARIN Outreach on IPv4 Depletion
The Board of Trustees has directed ARIN staff to contact, by certified
letter [1], the CEOs of organizations that currently hold IPv4 resources
in its region. The purpose of this effort is to raise executive
awareness of the depletion of IPv4 resources and to encourage the active
adoption of IPv6.
This letter will also serve as notification that, in response to the
approaching depletion of the IPv4 free address pool, the Board has
directed ARIN staff to take additional steps to ensure the legitimacy of
all IPv4 address space requests.
Beginning 18 May 2009, ARIN will require that all applications for IPv4
address space include an attestation of accuracy from an officer of the
organization. For information on this requirement, please see:
https://www.arin.net/resources/agreements/officer_attest.html
Regards,
Leslie Nobile
Director of Registration Services
American Registry for Internet Numbers (ARIN)
[1] https://www.arin.net/knowledge/about_resources/ceo_letter.pdf
ARINは各IPv4割当て組織の取締役に連絡を取ることになった模様。
これで経営層の方々にIPv4の有効活用とIPv6への移行の意識が進むのでしょうか。
ちょっと疑問ですが、やらないよりはマシかな。
Subject: [arin-announce] ARIN Outreach on IPv4 Depletion
The Board of Trustees has directed ARIN staff to contact, by certified
letter [1], the CEOs of organizations that currently hold IPv4 resources
in its region. The purpose of this effort is to raise executive
awareness of the depletion of IPv4 resources and to encourage the active
adoption of IPv6.
This letter will also serve as notification that, in response to the
approaching depletion of the IPv4 free address pool, the Board has
directed ARIN staff to take additional steps to ensure the legitimacy of
all IPv4 address space requests.
Beginning 18 May 2009, ARIN will require that all applications for IPv4
address space include an attestation of accuracy from an officer of the
organization. For information on this requirement, please see:
https://www.arin.net/resources/agreements/officer_attest.html
Regards,
Leslie Nobile
Director of Registration Services
American Registry for Internet Numbers (ARIN)
[1] https://www.arin.net/knowledge/about_resources/ceo_letter.pdf
ARINは各IPv4割当て組織の取締役に連絡を取ることになった模様。
これで経営層の方々にIPv4の有効活用とIPv6への移行の意識が進むのでしょうか。
ちょっと疑問ですが、やらないよりはマシかな。
NZNOG@Apr 21, 2009
Date: Tue, 21 Apr 2009 12:14:05 +1200
Subject: [nznog] msn.co.nz
So, I wouldn't normally make a post like this, but I figure one or two
people might notice this at some point in the next day or so:
mj@coalface:~$ whois msn.co.nz | egrep ^ns_name
ns_name_01: fatih1.turkguvenligi.info
ns_name_02: fatih2.turkguvenligi.info
mj@coalface:~$ whois msn.co.nz | egrep ^domain_datelastmodified
domain_datelastmodified: 2009-04-21T09:44:21+12:00
From my resolver's cache:
;; ANSWER SECTION:
msn.co.nz. 3282 IN A 202.58.48.29
;; AUTHORITY SECTION:
msn.co.nz. 20363 IN NS ns4.msft.net.
msn.co.nz. 20363 IN NS ns5.msft.net.
msn.co.nz. 20363 IN NS ns1.msft.net.
msn.co.nz. 20363 IN NS ns2.msft.net.
msn.co.nz. 20363 IN NS ns3.msft.net.
;; ADDITIONAL SECTION:
ns1.msft.net. 1571 IN A 207.68.160.190
ns2.msft.net. 1593 IN A 65.54.240.126
ns3.msft.net. 18367 IN A 213.199.161.77
ns4.msft.net. 18367 IN A 207.46.66.126
ns5.msft.net. 1302 IN A 65.55.238.126
From the new NS:
;; ANSWER SECTION:
msn.co.nz. 14400 IN A 95.211.11.163
;; AUTHORITY SECTION:
msn.co.nz. 86400 IN NS fatih1.turkguvenligi.info.
msn.co.nz. 86400 IN NS fatih2.turkguvenligi.info.
;; ADDITIONAL SECTION:
fatih1.turkguvenligi.info. 14400 IN A 95.211.11.163
fatih2.turkguvenligi.info. 14400 IN A 95.211.11.163
It's not still April Fools, is it?
-Mike
MSNニュージーランドがハイジャックされた模様。
SQLインジェクションでネームサーバが書き換えられたらしいとのこと。
Subject: [nznog] msn.co.nz
So, I wouldn't normally make a post like this, but I figure one or two
people might notice this at some point in the next day or so:
mj@coalface:~$ whois msn.co.nz | egrep ^ns_name
ns_name_01: fatih1.turkguvenligi.info
ns_name_02: fatih2.turkguvenligi.info
mj@coalface:~$ whois msn.co.nz | egrep ^domain_datelastmodified
domain_datelastmodified: 2009-04-21T09:44:21+12:00
From my resolver's cache:
;; ANSWER SECTION:
msn.co.nz. 3282 IN A 202.58.48.29
;; AUTHORITY SECTION:
msn.co.nz. 20363 IN NS ns4.msft.net.
msn.co.nz. 20363 IN NS ns5.msft.net.
msn.co.nz. 20363 IN NS ns1.msft.net.
msn.co.nz. 20363 IN NS ns2.msft.net.
msn.co.nz. 20363 IN NS ns3.msft.net.
;; ADDITIONAL SECTION:
ns1.msft.net. 1571 IN A 207.68.160.190
ns2.msft.net. 1593 IN A 65.54.240.126
ns3.msft.net. 18367 IN A 213.199.161.77
ns4.msft.net. 18367 IN A 207.46.66.126
ns5.msft.net. 1302 IN A 65.55.238.126
From the new NS:
;; ANSWER SECTION:
msn.co.nz. 14400 IN A 95.211.11.163
;; AUTHORITY SECTION:
msn.co.nz. 86400 IN NS fatih1.turkguvenligi.info.
msn.co.nz. 86400 IN NS fatih2.turkguvenligi.info.
;; ADDITIONAL SECTION:
fatih1.turkguvenligi.info. 14400 IN A 95.211.11.163
fatih2.turkguvenligi.info. 14400 IN A 95.211.11.163
It's not still April Fools, is it?
-Mike
MSNニュージーランドがハイジャックされた模様。
SQLインジェクションでネームサーバが書き換えられたらしいとのこと。
4/21/2009
RIPE-address-policy-wg@Apr 20, 2009
Date: Mon, 20 Apr 2009 13:18:52 +0200
Subject: [address-policy-wg] New Document available: RIPE-465
Dear Colleagues,
The mention of 0.8 as the HD ratio (in two occurrences) in ripe-450 is an error.
In RIPE, the HD ratio for IPv6 has been set at 0.94 since November 2007 and was documented correctly in the previous IPv6 Address Allocation and Assignment Policy (ripe-421).
We have corrected the error and published an updated document (ripe-465) that you can find at:
http://test-www.ripe.net/ripe/docs/ripe-465.html
We apologise for any confusion this may have caused and will put in place additional checks to prevent similar errors in the future
Kind Regards
Adrian Bedford
Web Services Team Leader
RIPE NCC
RIPEのIPv6アドレス割当て/割振りのドキュメントについて訂正版を発行。
HDレシオが0.8の時代のものから順次Updateしてきているので変化を追いやすいかも。
Subject: [address-policy-wg] New Document available: RIPE-465
Dear Colleagues,
The mention of 0.8 as the HD ratio (in two occurrences) in ripe-450 is an error.
In RIPE, the HD ratio for IPv6 has been set at 0.94 since November 2007 and was documented correctly in the previous IPv6 Address Allocation and Assignment Policy (ripe-421).
We have corrected the error and published an updated document (ripe-465) that you can find at:
http://test-www.ripe.net/ripe/docs/ripe-465.html
We apologise for any confusion this may have caused and will put in place additional checks to prevent similar errors in the future
Kind Regards
Adrian Bedford
Web Services Team Leader
RIPE NCC
RIPEのIPv6アドレス割当て/割振りのドキュメントについて訂正版を発行。
HDレシオが0.8の時代のものから順次Updateしてきているので変化を追いやすいかも。
MENOG@Apr 20, 2009
Date: Mon, 20 Apr 2009 15:54:42 +0300
Subject: [menog] Oracle buys Sun!!!
Dear Colleagues,
How true is the statement; 'Oracle buys Sun' ? Typically, HW vendor buys HW vendor, but cross acquisition something that never occurs, at least in mind, unless I've got a tiny brain :)
Regards
オラクルがサンを買収、というニュース。
他のNOGではあまり話題を見かけないが、メジャーネームがメジャーネームを買収ということで
食いつきがよかったか。
Subject: [menog] Oracle buys Sun!!!
Dear Colleagues,
How true is the statement; 'Oracle buys Sun' ? Typically, HW vendor buys HW vendor, but cross acquisition something that never occurs, at least in mind, unless I've got a tiny brain :)
Regards
オラクルがサンを買収、というニュース。
他のNOGではあまり話題を見かけないが、メジャーネームがメジャーネームを買収ということで
食いつきがよかったか。
NANOG@Apr 20, 2009
Date: Mon, 20 Apr 2009 18:39:47 -0500 (CDT)
Subject: Important New Requirement for IPv4 Requests
Forwarded message:
> Subject: Important New Requirement for IPv4 Requests
> From: ARIN Registration Services
>
> Hello,
>
> With the approaching depletion of the IPv4 address free pool, the
> ARIN Board of Trustees has directed ARIN staff to take additional
> steps to ensure the legitimacy of all IPv4 address space requests.
> Beginning 18 May 2009, ARIN will require that all applications for
> IPv4 address space include an attestation of accuracy from an officer
> of the organization. For more information on this requirement, please
> see:
>
> https://www.arin.net/resources/agreements/officer_attest.html
>
> Whenever a request for IPv4 resources is received, ARIN will ask in
> its initial reply for the name and contact information of an officer
> of the organization who will be able to attest to the validity of the
> information provided to ARIN.
>
> At the point a request is ready to be approved, ARIN will send a summary
> of the request (via e-mail) to the officer with a cc: to the requesting
> POC (Tech or Admin) and ask the officer to attest to the validity of the
> information provided to ARIN. The summary will provide a brief overview
> of the request and an explanation of the required attestation. ARIN will
> include the original request template and any other relevant information
> the requestor provided. Once ARIN receives the attestation from the
> officer, the request can be approved. Attestation may also be provided
> via fax or postal mail.
>
> For further assistance, contact ARIN's Registration Services Help Desk
> via e-mail to hostmaster@arin.net or telephone at +1.703.227.0660.
Let me see if I can understand this.
We're running out of IPv4 space.
Knowing that blatant lying about IP space justifications has been an
ongoing game in the community, ARIN has decided to "do something" about
it.
So now they're going to require an attestation. Which means that they
are going to require an "officer" to "attest" to the validity of the
information.
So the "officer," most likely not being a technical person, is going to
contact ... probably the same people who made the request, ask them if
they need the space. Right?
And why would the answer be any different, now?
... JG
ARINは新しいIP要求に対し、経営者に確認のメールなどを送ることを考えている。
それに対して異論が出てきています。
Subject: Important New Requirement for IPv4 Requests
Forwarded message:
> Subject: Important New Requirement for IPv4 Requests
> From: ARIN Registration Services
>
> Hello,
>
> With the approaching depletion of the IPv4 address free pool, the
> ARIN Board of Trustees has directed ARIN staff to take additional
> steps to ensure the legitimacy of all IPv4 address space requests.
> Beginning 18 May 2009, ARIN will require that all applications for
> IPv4 address space include an attestation of accuracy from an officer
> of the organization. For more information on this requirement, please
> see:
>
> https://www.arin.net/resources/agreements/officer_attest.html
>
> Whenever a request for IPv4 resources is received, ARIN will ask in
> its initial reply for the name and contact information of an officer
> of the organization who will be able to attest to the validity of the
> information provided to ARIN.
>
> At the point a request is ready to be approved, ARIN will send a summary
> of the request (via e-mail) to the officer with a cc: to the requesting
> POC (Tech or Admin) and ask the officer to attest to the validity of the
> information provided to ARIN. The summary will provide a brief overview
> of the request and an explanation of the required attestation. ARIN will
> include the original request template and any other relevant information
> the requestor provided. Once ARIN receives the attestation from the
> officer, the request can be approved. Attestation may also be provided
> via fax or postal mail.
>
> For further assistance, contact ARIN's Registration Services Help Desk
> via e-mail to hostmaster@arin.net or telephone at +1.703.227.0660.
Let me see if I can understand this.
We're running out of IPv4 space.
Knowing that blatant lying about IP space justifications has been an
ongoing game in the community, ARIN has decided to "do something" about
it.
So now they're going to require an attestation. Which means that they
are going to require an "officer" to "attest" to the validity of the
information.
So the "officer," most likely not being a technical person, is going to
contact ... probably the same people who made the request, ask them if
they need the space. Right?
And why would the answer be any different, now?
... JG
ARINは新しいIP要求に対し、経営者に確認のメールなどを送ることを考えている。
それに対して異論が出てきています。
APPLe@Apr 20, 2009
Date: Mon, 20 Apr 2009 00:59:46 -0700 (PDT)
Subject: [APPLe list] general internet news - 20 April
**********************************************************
Sponsored by the Singapore Internet Research Centre
Nanyang Technological University, Singapore
http://www.ntu.edu.sg/sci/sirc/
**********************************************************
Don't forget to check out http://www.auda.org.au/domain-news/ for today's edition of the complete domain news, already online!
And see my website - http://technewsreview.com.au/ - for daily updates in between postings.
～ばっさりと略～
MI5 seeks Q - applications in invisible ink optional
For years Britain's foreign intelligence service, MI6, had a Q - a figure, in fact and fiction, "whose team is responsible for innovative technology and gimmicks and gadgets and things like that," as one of its officers puts it.
http://www.guardian.co.uk/uk/2009/apr/18/mi5-recruit-scientific-adviser
～後略～
MI5が007の"Q"のような人を探している、と。
テクノロジー、ギミック、ガジェットに興味がある人は応募してみると面白いかも。
それ以前に国籍条項に引っ掛る可能性があるのでLink先をよく読みこんでから応募をしてください。
Subject: [APPLe list] general internet news - 20 April
**********************************************************
Sponsored by the Singapore Internet Research Centre
Nanyang Technological University, Singapore
http://www.ntu.edu.sg/sci/sirc/
**********************************************************
Don't forget to check out http://www.auda.org.au/domain-news/ for today's edition of the complete domain news, already online!
And see my website - http://technewsreview.com.au/ - for daily updates in between postings.
～ばっさりと略～
MI5 seeks Q - applications in invisible ink optional
For years Britain's foreign intelligence service, MI6, had a Q - a figure, in fact and fiction, "whose team is responsible for innovative technology and gimmicks and gadgets and things like that," as one of its officers puts it.
http://www.guardian.co.uk/uk/2009/apr/18/mi5-recruit-scientific-adviser
～後略～
MI5が007の"Q"のような人を探している、と。
テクノロジー、ギミック、ガジェットに興味がある人は応募してみると面白いかも。
それ以前に国籍条項に引っ掛る可能性があるのでLink先をよく読みこんでから応募をしてください。
4/20/2009
NANOG@Apr 19, 2009
Date: Sun, 19 Apr 2009 12:55:45 -0700 (PDT)
Subject: SkypeSetup Rogue Download
Has anyone seen anything like this?
http://www.virustotal.com/analisis/f58203f8d5cb98628eaa785e27c9e059
SkypeSetup.exeがVirusTotalを通してみるとウィルスに感染しているように見える。
返信としてDownload.comからダウンロードしたものは大丈夫だったよ、と。
怪しい？
Subject: SkypeSetup Rogue Download
Has anyone seen anything like this?
http://www.virustotal.com/analisis/f58203f8d5cb98628eaa785e27c9e059
SkypeSetup.exeがVirusTotalを通してみるとウィルスに感染しているように見える。
返信としてDownload.comからダウンロードしたものは大丈夫だったよ、と。
怪しい？
4/19/2009
APNIC-sig-policy@Apr 18, 2009
Date: Sat, 18 Apr 2009 03:08:08 +1000
Subject: [sig-policy] New thoughts on 050
I am wondering. 050 is about resource transfers.
But does anyone have an opinion on resource leasing?
Example... I enter into a private agreement with a party to lease them an AS and the rights to route (or attempt to do so) a /21, and charge them a yearly fee.
050 stops transfers, but who cares about 050 if there are easier, simpler ways to accomplish the same thing - but better... I still own it in the end.
You could even have a broker that leased lots of excess address space from members for a certain period, and based on the scarcity, the size of the resource, then sub-leased it to different parties at rates according to demand at the time - kind of like the real estate rental market.
I guess the concept of leasing address space is already a standard one as most ISP's I know, and in ones I have built, we have levied a fee on the end customer for larger than the default allocation as a cost recovery method of our APNIC fees in having them in the first place.
Thoughts?
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve@eintellego.net / www.eintellego.net
APNICのprop-050のポリシーに関して。
実際にはIPアドレス移転だけじゃなくて、IPアドレスリースということもできる。
それについて意見は？という質問。
私自身、もしprop-050が通った場合に何を考えるかというと、IPアドレスリースでした。
大規模なIP空間を持った企業グループがグループ内NICとしてグループ企業にIPを配布し、
アドレスが必要になればAPNIC等から割当を受けるか、IPアドレスを保持する他企業を買収する。
IANA--RIR--LIRの仕組みには則っているが、パワーバランスを変化させてしまう可能性もあり。
私が思いつくのだからかなりの人数が危険性を認識しているはず。
ようやく意見が出てきてよかった。
Subject: [sig-policy] New thoughts on 050
I am wondering. 050 is about resource transfers.
But does anyone have an opinion on resource leasing?
Example... I enter into a private agreement with a party to lease them an AS and the rights to route (or attempt to do so) a /21, and charge them a yearly fee.
050 stops transfers, but who cares about 050 if there are easier, simpler ways to accomplish the same thing - but better... I still own it in the end.
You could even have a broker that leased lots of excess address space from members for a certain period, and based on the scarcity, the size of the resource, then sub-leased it to different parties at rates according to demand at the time - kind of like the real estate rental market.
I guess the concept of leasing address space is already a standard one as most ISP's I know, and in ones I have built, we have levied a fee on the end customer for larger than the default allocation as a cost recovery method of our APNIC fees in having them in the first place.
Thoughts?
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve@eintellego.net / www.eintellego.net
APNICのprop-050のポリシーに関して。
実際にはIPアドレス移転だけじゃなくて、IPアドレスリースということもできる。
それについて意見は？という質問。
私自身、もしprop-050が通った場合に何を考えるかというと、IPアドレスリースでした。
大規模なIP空間を持った企業グループがグループ内NICとしてグループ企業にIPを配布し、
アドレスが必要になればAPNIC等から割当を受けるか、IPアドレスを保持する他企業を買収する。
IANA--RIR--LIRの仕組みには則っているが、パワーバランスを変化させてしまう可能性もあり。
私が思いつくのだからかなりの人数が危険性を認識しているはず。
ようやく意見が出てきてよかった。
4/18/2009
RIPE-anti-abuse-wg@Apr 17, 2009
date: Fri, Apr 17, 2009 at 9:31 PM
subject: [anti-abuse-wg] What to do when both RIR and ISP don't care?
I have first to say sorry to this mailing-list, as this mail
isn't related to RIPE but rather to LACNIC.
I've traced back some hacking from an IP address (200.113.126.76)
in an ISP (Telefonica Empresas). I've sent an abuse complaint to the
only email address available (sescobar@isp.tie.cl) in LACNIC Whois but
visibly the ISP didn't care and nothing was done.
Then I had but to send another abuse complaint to LACNIC
(abuse@lacnic.net). The only answer I got is an automatic message
saying that it's not their responsibility at LACNIC to investigate
abuse issues.
That's really a bureaucratic act! What could we do in such situation?
PS: Really sorry that I have to bring this issue in RIPE because in
LACNIC website, there's really nothing to help users like in RIPE
where you have a mailing-list, or like in APNIC where one could report
invalid WHOIS info.
南米地域でクラックされたPCからのSPAMに関しての相談。
このメーリングリストは欧州地域のものだが、南米地域に同様のものが無いため
どうしたらいい？という相談のメール。
CERT.brなどに相談すべきじゃないかな。
subject: [anti-abuse-wg] What to do when both RIR and ISP don't care?
I have first to say sorry to this mailing-list, as this mail
isn't related to RIPE but rather to LACNIC.
I've traced back some hacking from an IP address (200.113.126.76)
in an ISP (Telefonica Empresas). I've sent an abuse complaint to the
only email address available (sescobar@isp.tie.cl) in LACNIC Whois but
visibly the ISP didn't care and nothing was done.
Then I had but to send another abuse complaint to LACNIC
(abuse@lacnic.net). The only answer I got is an automatic message
saying that it's not their responsibility at LACNIC to investigate
abuse issues.
That's really a bureaucratic act! What could we do in such situation?
PS: Really sorry that I have to bring this issue in RIPE because in
LACNIC website, there's really nothing to help users like in RIPE
where you have a mailing-list, or like in APNIC where one could report
invalid WHOIS info.
南米地域でクラックされたPCからのSPAMに関しての相談。
このメーリングリストは欧州地域のものだが、南米地域に同様のものが無いため
どうしたらいい？という相談のメール。
CERT.brなどに相談すべきじゃないかな。
NANOG@Apr 17, 2009
Date: Fri, 17 Apr 2009 22:56:31 +0000
Subject: Re: US west coast personal colo
On Fri, Apr 17, 2009 at 06:50:42PM -0400, Sean Donelan wrote:A
>
> Is anyone still doing personal colo on the west coast? I'm looking for a
> new home for my personal server on the west coast, and it seems like
> the economy has taken out most of the old personal colo offers.
> Even the old web page on www.vix.com/personalcolo is gone.
> A
there are a few of us still around.
--bill
米国西海岸で個人用コロケーションってない？という質問に、まだいくつかあるよ、という回答。
願わくばURLまで教えて欲しかった。。。
Subject: Re: US west coast personal colo
On Fri, Apr 17, 2009 at 06:50:42PM -0400, Sean Donelan wrote:A
>
> Is anyone still doing personal colo on the west coast? I'm looking for a
> new home for my personal server on the west coast, and it seems like
> the economy has taken out most of the old personal colo offers.
> Even the old web page on www.vix.com/personalcolo is gone.
> A
there are a few of us still around.
--bill
米国西海岸で個人用コロケーションってない？という質問に、まだいくつかあるよ、という回答。
願わくばURLまで教えて欲しかった。。。
NANOG@Apr 17, 2009
Date: Fri, 17 Apr 2009 10:11:30 -0400
Subject: IXP
Hello NANOG,
I like would to know what are best practices for an internet exchange. I
have some concerns about the following;
Can the IXP members use RFC 1918 ip addresses for their peering?
Can the IXP members use private autonomous numbers for their peering?
Maybe the answer is obviuos, but I like to know from any IXP admins what
their setup/experiences have been.
--
--sharlon
IXPのメンバーはプライベートアドレスやプライベートASを使ってもいいの？という質問。
使えるとは思うけど、グローバルでやらない理由はなにかな？
Subject: IXP
Hello NANOG,
I like would to know what are best practices for an internet exchange. I
have some concerns about the following;
Can the IXP members use RFC 1918 ip addresses for their peering?
Can the IXP members use private autonomous numbers for their peering?
Maybe the answer is obviuos, but I like to know from any IXP admins what
their setup/experiences have been.
--
--sharlon
IXPのメンバーはプライベートアドレスやプライベートASを使ってもいいの？という質問。
使えるとは思うけど、グローバルでやらない理由はなにかな？
4/17/2009
ARIN-announce@Apr 16, 2009
Date: Thu, 16 Apr 2009 15:09:14 -0400
Subject: [arin-announce] ARIN President and CEO Update
ARIN previously announced that Thomas Cady would be joining as President
and CEO. Mr. Cady will not become ARIN's CEO due to changes in Mr.
Cady's personal circumstances. The ARIN Board is at this time in
negotiations with a highly qualified CEO candidate. In the interim, John
Curran, who has been serving as interim President and CEO of ARIN has
asked that he be relieved of his duties as the founding Chairman of the
ARIN Board of Trustees, so he can devote more time to his role as acting
President and CEO. Mr. Curran will remain an ARIN Board member. Paul
Vixie, a current Board member, has been elected by the Board to serve as
Chairman of the Board. ARIN looks forward to announcing our permanent
CEO and President shortly.
Regards,
Paul Vixie
Chairman, Board of Trustees
American Registry for Internet Numbers (ARIN)
ARINは新CEOを決めるのに難航中。とはいえ暫定社長兼暫定最高経営責任者を新候補で調整中。
はやく体制が決まるといいですね。
IPアドレスの終末期の大変さを知っている人間は引き受けにくいだろうし、
IPアドレスを知らない人間はこの仕事が解らないので引き受けにくいだろう。
大変だ。
Subject: [arin-announce] ARIN President and CEO Update
ARIN previously announced that Thomas Cady would be joining as President
and CEO. Mr. Cady will not become ARIN's CEO due to changes in Mr.
Cady's personal circumstances. The ARIN Board is at this time in
negotiations with a highly qualified CEO candidate. In the interim, John
Curran, who has been serving as interim President and CEO of ARIN has
asked that he be relieved of his duties as the founding Chairman of the
ARIN Board of Trustees, so he can devote more time to his role as acting
President and CEO. Mr. Curran will remain an ARIN Board member. Paul
Vixie, a current Board member, has been elected by the Board to serve as
Chairman of the Board. ARIN looks forward to announcing our permanent
CEO and President shortly.
Regards,
Paul Vixie
Chairman, Board of Trustees
American Registry for Internet Numbers (ARIN)
ARINは新CEOを決めるのに難航中。とはいえ暫定社長兼暫定最高経営責任者を新候補で調整中。
はやく体制が決まるといいですね。
IPアドレスの終末期の大変さを知っている人間は引き受けにくいだろうし、
IPアドレスを知らない人間はこの仕事が解らないので引き受けにくいだろう。
大変だ。
NNSquad@Apr 16, 2009
Date: Thu, 16 Apr 2009 16:06:56 -0700
Subject: [ NNSquad ] Bulletin: Time Warner Reportedly to "Shelve" Bandwidth Cap Plans
Bulletin: Time Warner Reportedly to "Shelve" Bandwidth Cap Plans
http://lauren.vortex.com/archive/000548.html
Greetings. In an extremely brief item that moved this afternoon, AP
has reported that "following mounting public and political outcry,"
Time Warner Cable is "shelving" plans for capped/metered Internet use.
( http://nytimes.com/aponline/2009/04/16/business/AP-TEC-Metered-Internet.html )
The article also suggests that this "capitulation" bodes ill for
future efforts of this sort.
Obviously, there will be a great deal more to say about this story as
details become available, and the reactions of other ISPs who have
implemented or have been moving toward bandwidth caps (including
Comcast, AT&T, etc.) will be interesting to observe. The related
implications could potentially impact literally every aspect of
Internet use.
Will I need to revise "'Once Upon a Time' (Understanding Bandwidth
Caps)" ( http://www.nnsquad.org/bandwidth-caps.html ) to provide a
happy ending after all? It's still really too early to know. But
today's development is certainly quite fascinating.
There's an old slogan that goes "Power to the people!" Perhaps in the
context of the Internet, "Bandwidth for the people!" should be a new
rallying cry.
Stay tuned.
--Lauren--
Lauren Weinstein
タイムワーナーは帯域制限を棚上げしたというメール。
やはり反対意見が多かったか。
日本ではぷららやIIJへの反対意見も多少はあったようだが、それほど問題にならなかった気がする。
違法P2Pが敵なうちに導入できたからね。
今は動画共有サイトだから・・・ これは大手を振っては制限できない。。。
Subject: [ NNSquad ] Bulletin: Time Warner Reportedly to "Shelve" Bandwidth Cap Plans
Bulletin: Time Warner Reportedly to "Shelve" Bandwidth Cap Plans
http://lauren.vortex.com/archive/000548.html
Greetings. In an extremely brief item that moved this afternoon, AP
has reported that "following mounting public and political outcry,"
Time Warner Cable is "shelving" plans for capped/metered Internet use.
( http://nytimes.com/aponline/2009/04/16/business/AP-TEC-Metered-Internet.html )
The article also suggests that this "capitulation" bodes ill for
future efforts of this sort.
Obviously, there will be a great deal more to say about this story as
details become available, and the reactions of other ISPs who have
implemented or have been moving toward bandwidth caps (including
Comcast, AT&T, etc.) will be interesting to observe. The related
implications could potentially impact literally every aspect of
Internet use.
Will I need to revise "'Once Upon a Time' (Understanding Bandwidth
Caps)" ( http://www.nnsquad.org/bandwidth-caps.html ) to provide a
happy ending after all? It's still really too early to know. But
today's development is certainly quite fascinating.
There's an old slogan that goes "Power to the people!" Perhaps in the
context of the Internet, "Bandwidth for the people!" should be a new
rallying cry.
Stay tuned.
--Lauren--
Lauren Weinstein
タイムワーナーは帯域制限を棚上げしたというメール。
やはり反対意見が多かったか。
日本ではぷららやIIJへの反対意見も多少はあったようだが、それほど問題にならなかった気がする。
違法P2Pが敵なうちに導入できたからね。
今は動画共有サイトだから・・・ これは大手を振っては制限できない。。。
4/16/2009
AfriNIC-rpd@Apr 15, 2009
Date: Wed, 15 Apr 2009 15:50:58 +0300
Subject: [AfriNIC-rpd] AfriNIC Policy Proposal Summary
Dear Members,
Below please find a summary of the policy proposals currently under
discussion in the AfriNIC region. Please note that these policies shall be
discussed at the forthcoming face to face public meeting during the AfriNIC
10 meetings. Members are therefore encouraged to continue discussions on the
policy proposals between now and then.
The AfriNIC Policy Development Process can be found at:
http://www.afrinic.net/docs/policies/afpol-pdp200707.htm
AfriNIC Mailing Lists subscription information can be found at:
http://www.afrinic.net/mailinglist.htm
Kind Regards,
Vincent Ngundi
Chair, AfriNIC PDP-MG
####### Policy Proposal Summary #############
Policy proposal : IPv4 Soft Landing Policy
Proposal Date : 05 Jan 2009
Scope : Regional proposal
afpol-v4200901 < http://www.afrinic.net/docs/policies/afpol-v4200901.htm>
Summary:
This policy proposal outlines a process through which AfriNIC shall manage
the last /8 addresses that will be assigned to it by the IANA under the
"Global Policy for the Allocation of the Remaining IPv4 Address space".
<http://www.afrinic.net/docs/policies/afpol-v4gp200802.html>
There were several comments regarding this policy from AfriNIC community;
such as the comment on the idea of refraining from making v6 allocations
mandatory as shown in the policy, They argue that an RIR is not supposed to
dictate on the technology that the LIR's use.
Another comments favor the return of the /16 into the v4 pool when the v4
pool reached exhaustion, and suggest making allocations for Critical
infrastructure from the /16 that will be in reserve, on contrary, other
comments saying we should leave this reserved even when the pool reaches
exhaustion as the motive for reserving it was for unforeseen circumstances,
and think if we make allocations to Critical infrastructure from the /16 in
reserve we shall be eating our cake and expecting to have it.
Comments seconded the idea of all address allocations being used only within
the AfriNIC region arguing that all resources allocated should be used
within Africa to support local operations. and other comments favored a 90%
threshold of usage before additional allocation can be made to any LIR.
It's a very important policy proposal in case of ratification by community,
it'll re-shape the way of allocating IPv4 address to all LIRs in the region.
It is the time to discuss it more and we'd like to encourage the community
to put their inputs in order to get all proper required modifications for
the proposal (if any) before the coming AfriNIC-10 face to face meeting next
May in Cairo.
##############################
Policy proposal : IPv6 Allocations to Non-Profit Networks
Proposal Date : 13 Jan 2009
Scope : Regional proposal
afpol-v6200901 <http://www.afrinic.net/docs/policies/afpol-v6200901.htm>
Summary:
This policy seeks to make it as easy as possible for non-profit entities to
obtain a /48 PI IPv6 addressing resources from AfriNIC and drive the
deployment of and demand for IPv6 services through this in Africa.
Additionally the policy seeks to limit the way in which these addressing
resources for non-profit entities will be used to avoid abuse by LIRs,
Internet Service Providers and other commercial users of Internet addressing
resources.
we need to hear the comments from community on this proposal "IPv6
Allocations to Non-Profit Networks". This proposal makes a massive
controversial discussion in our mailing-list and in other regions too, we
heard 12 emails from community till now that comment on this policy
proposal, some for positive and other for negative reactions. It is the time
to discuss it more and we'd like to encourage the community to put their
inputs in order to get all proper required modifications for the proposal
(if any) before the coming AfriNIC-10 face to face meeting next May in
Cairo.
##############################
Policy Proposal : Global Policy Proposal for the Allocation of IPv4 Blocks
to Regional Internet Registries
Proposal Date : 09 Mar 2009
Scope : Global proposal
afpol-v4gb200903 <http://www.afrinic.net/docs/policies/afpol-v4gb200903.htm>
Summary:
This global policy is aiming to solve the problem of transferring IPv4
address space between RIRs, that may be exist at the depletion of IANA free
pool. The authors of this policy proposal provide a mechanism for the RIRs
to put the recovered IPv4 address space back to the IANA central pool, and
also provide the IANA with the policy by which it can allocate them back to
the RIR in a well defined criteria.
This proposal is submitted to the five existing RIRs, and has been adopted
in APNIC region.
we need to hear the comments from community on this proposal "Global Policy
Proposal for the Allocation of IPv4 Blocks to Regional Internet Registries".
We heard only one comment! We think it's the time to discuss it more and
we'd like to encourage the community to put their inputs in order to get all
proper required modifications for the proposal (if any) before the coming
AfriNIC-10 face-to-face meeting next May in Cairo.
AfriNICミーティングももうすぐですね。
ミーティングを前に提案もそろってきました。
非営利団体向けIPv6割り当てがちょっと特殊かな。
Subject: [AfriNIC-rpd] AfriNIC Policy Proposal Summary
Dear Members,
Below please find a summary of the policy proposals currently under
discussion in the AfriNIC region. Please note that these policies shall be
discussed at the forthcoming face to face public meeting during the AfriNIC
10 meetings. Members are therefore encouraged to continue discussions on the
policy proposals between now and then.
The AfriNIC Policy Development Process can be found at:
http://www.afrinic.net/docs/policies/afpol-pdp200707.htm
AfriNIC Mailing Lists subscription information can be found at:
http://www.afrinic.net/mailinglist.htm
Kind Regards,
Vincent Ngundi
Chair, AfriNIC PDP-MG
####### Policy Proposal Summary #############
Policy proposal : IPv4 Soft Landing Policy
Proposal Date : 05 Jan 2009
Scope : Regional proposal
afpol-v4200901 < http://www.afrinic.net/docs/policies/afpol-v4200901.htm>
Summary:
This policy proposal outlines a process through which AfriNIC shall manage
the last /8 addresses that will be assigned to it by the IANA under the
"Global Policy for the Allocation of the Remaining IPv4 Address space".
<http://www.afrinic.net/docs/policies/afpol-v4gp200802.html>
There were several comments regarding this policy from AfriNIC community;
such as the comment on the idea of refraining from making v6 allocations
mandatory as shown in the policy, They argue that an RIR is not supposed to
dictate on the technology that the LIR's use.
Another comments favor the return of the /16 into the v4 pool when the v4
pool reached exhaustion, and suggest making allocations for Critical
infrastructure from the /16 that will be in reserve, on contrary, other
comments saying we should leave this reserved even when the pool reaches
exhaustion as the motive for reserving it was for unforeseen circumstances,
and think if we make allocations to Critical infrastructure from the /16 in
reserve we shall be eating our cake and expecting to have it.
Comments seconded the idea of all address allocations being used only within
the AfriNIC region arguing that all resources allocated should be used
within Africa to support local operations. and other comments favored a 90%
threshold of usage before additional allocation can be made to any LIR.
It's a very important policy proposal in case of ratification by community,
it'll re-shape the way of allocating IPv4 address to all LIRs in the region.
It is the time to discuss it more and we'd like to encourage the community
to put their inputs in order to get all proper required modifications for
the proposal (if any) before the coming AfriNIC-10 face to face meeting next
May in Cairo.
##############################
Policy proposal : IPv6 Allocations to Non-Profit Networks
Proposal Date : 13 Jan 2009
Scope : Regional proposal
afpol-v6200901 <http://www.afrinic.net/docs/policies/afpol-v6200901.htm>
Summary:
This policy seeks to make it as easy as possible for non-profit entities to
obtain a /48 PI IPv6 addressing resources from AfriNIC and drive the
deployment of and demand for IPv6 services through this in Africa.
Additionally the policy seeks to limit the way in which these addressing
resources for non-profit entities will be used to avoid abuse by LIRs,
Internet Service Providers and other commercial users of Internet addressing
resources.
we need to hear the comments from community on this proposal "IPv6
Allocations to Non-Profit Networks". This proposal makes a massive
controversial discussion in our mailing-list and in other regions too, we
heard 12 emails from community till now that comment on this policy
proposal, some for positive and other for negative reactions. It is the time
to discuss it more and we'd like to encourage the community to put their
inputs in order to get all proper required modifications for the proposal
(if any) before the coming AfriNIC-10 face to face meeting next May in
Cairo.
##############################
Policy Proposal : Global Policy Proposal for the Allocation of IPv4 Blocks
to Regional Internet Registries
Proposal Date : 09 Mar 2009
Scope : Global proposal
afpol-v4gb200903 <http://www.afrinic.net/docs/policies/afpol-v4gb200903.htm>
Summary:
This global policy is aiming to solve the problem of transferring IPv4
address space between RIRs, that may be exist at the depletion of IANA free
pool. The authors of this policy proposal provide a mechanism for the RIRs
to put the recovered IPv4 address space back to the IANA central pool, and
also provide the IANA with the policy by which it can allocate them back to
the RIR in a well defined criteria.
This proposal is submitted to the five existing RIRs, and has been adopted
in APNIC region.
we need to hear the comments from community on this proposal "Global Policy
Proposal for the Allocation of IPv4 Blocks to Regional Internet Registries".
We heard only one comment! We think it's the time to discuss it more and
we'd like to encourage the community to put their inputs in order to get all
proper required modifications for the proposal (if any) before the coming
AfriNIC-10 face-to-face meeting next May in Cairo.
AfriNICミーティングももうすぐですね。
ミーティングを前に提案もそろってきました。
非営利団体向けIPv6割り当てがちょっと特殊かな。
LACNIC-Anuncios@Apr 15, 2009
Date: Wed, 15 Apr 2009 15:58:02 -0300
Subject: [LACNIC/Anuncios] Evento FRIDA Event- Webcasting
Podr? seguir el encuentro v?a webcasting en espa?ol:
http://www.programafrida.net/sp/eventos/frida2009/webcasting.html
------
O evento ter? transmiss?o em webcast em espanhol e ingl?s.
Espanhol: http://www.programafrida.net/sp/eventos/frida2009/webcasting.html
Ingl?s: http://www.programafrida.net/en/eventos/frida2009/webcasting.html
------
This event will be transmitted through a webcast in English:
http://www.programafrida.net/en/eventos/frida2009/webcasting.html
アジア・太平洋地域で行われるAPRICOTの南米地域版
FRIDA-Fundo Regional para a Inovação Digital na América Latina e Caribe
のWebcastingのご案内。栄えある第一回会議。
Agendaは「政府とパブリックポリシー」や「南米地域での成功例」など面白そうなものがずらり。
Subject: [LACNIC/Anuncios] Evento FRIDA Event- Webcasting
Podr? seguir el encuentro v?a webcasting en espa?ol:
http://www.programafrida.net/sp/eventos/frida2009/webcasting.html
------
O evento ter? transmiss?o em webcast em espanhol e ingl?s.
Espanhol: http://www.programafrida.net/sp/eventos/frida2009/webcasting.html
Ingl?s: http://www.programafrida.net/en/eventos/frida2009/webcasting.html
------
This event will be transmitted through a webcast in English:
http://www.programafrida.net/en/eventos/frida2009/webcasting.html
アジア・太平洋地域で行われるAPRICOTの南米地域版
FRIDA-Fundo Regional para a Inovação Digital na América Latina e Caribe
のWebcastingのご案内。栄えある第一回会議。
Agendaは「政府とパブリックポリシー」や「南米地域での成功例」など面白そうなものがずらり。
NNSquad@Apr 15, 2009
Date: Wed, 15 Apr 2009 08:26:46 -0400
Subject: [ NNSquad ] Bell Canada proposal to cap wholesale customers
Bell Canada has submitted a proposal to the CRTC to allow it to cap
bandwidth usage of wholesale customers (mostly independent ISPs). The
independent ISPs are concerned that this will essentially eliminate the
possibility of 'unlimited bandwidth' type offerings to their customers.
The submission from Bell Canada also comes at an interesting time when
the CRTC has recently allowed it to throttle wholesale customers for
'network management' purposes. In addition there are CRTC public
hearings scheduled in the next few months to investigate the general
issues relating to network management and throttling.
http://www.cbc.ca/technology/story/2009/04/14/bell-unlimited-download.ht
ml?ref=rss
Bell Canada has been struggling to be profitable over the last decade or
so - my guess is that this translates into a lack of investment in
infrastructure upgrades. Now it seems that they are trying to find any
means of avoiding spending the larger sums of money now required to
bring their networks to a standard that will support current Internet
usage patterns. There is also a clear anti-competitive aspect to the
impacts on wholesale customers where throttling and capping force
independent ISPs to limit their offerings to be similar to what Bell
Canada Internet Service already offers to it's residential customers.
ベル・カナダも帯域制限の提案を出してきました。
世界的な流れになるか。
Subject: [ NNSquad ] Bell Canada proposal to cap wholesale customers
Bell Canada has submitted a proposal to the CRTC to allow it to cap
bandwidth usage of wholesale customers (mostly independent ISPs). The
independent ISPs are concerned that this will essentially eliminate the
possibility of 'unlimited bandwidth' type offerings to their customers.
The submission from Bell Canada also comes at an interesting time when
the CRTC has recently allowed it to throttle wholesale customers for
'network management' purposes. In addition there are CRTC public
hearings scheduled in the next few months to investigate the general
issues relating to network management and throttling.
http://www.cbc.ca/technology/story/2009/04/14/bell-unlimited-download.ht
ml?ref=rss
Bell Canada has been struggling to be profitable over the last decade or
so - my guess is that this translates into a lack of investment in
infrastructure upgrades. Now it seems that they are trying to find any
means of avoiding spending the larger sums of money now required to
bring their networks to a standard that will support current Internet
usage patterns. There is also a clear anti-competitive aspect to the
impacts on wholesale customers where throttling and capping force
independent ISPs to limit their offerings to be similar to what Bell
Canada Internet Service already offers to it's residential customers.
ベル・カナダも帯域制限の提案を出してきました。
世界的な流れになるか。
NANOG@Apr 15, 2009
Date: Wed, 15 Apr 2009 00:51:36 -0700
Subject: Anyone from Intelligence Network Online?
Hi -
I wanted to see if anyone is here from Intelligence Network Online - I
suspect an old AS number and a /16 of yours is being hijacked by a spam gang
operating in downtown LA and wanted to get some confirmation.
-Justin
誰か諜報ネットワークの人いない？LAのダウンタウンにいるSPAMGANGに古いAS番号と/16のIPアドレスをハイジャックされた疑いがあるのだが、確証を得たい、というメール。
日本には経路奉行/テレコムISAC/JPIRRがあるが米国にはそういう枠組みがない。
BGPlayがあるのみ。欧州にはRISがあるがやはり起こった事象の記録が残るのみ。
経路奉行はリアルタイムにハイジャック情報を流せる世界に誇れるシステム。すばらしい。
Subject: Anyone from Intelligence Network Online?
Hi -
I wanted to see if anyone is here from Intelligence Network Online - I
suspect an old AS number and a /16 of yours is being hijacked by a spam gang
operating in downtown LA and wanted to get some confirmation.
-Justin
誰か諜報ネットワークの人いない？LAのダウンタウンにいるSPAMGANGに古いAS番号と/16のIPアドレスをハイジャックされた疑いがあるのだが、確証を得たい、というメール。
日本には経路奉行/テレコムISAC/JPIRRがあるが米国にはそういう枠組みがない。
BGPlayがあるのみ。欧州にはRISがあるがやはり起こった事象の記録が残るのみ。
経路奉行はリアルタイムにハイジャック情報を流せる世界に誇れるシステム。すばらしい。
NANOG@Apr 15, 2009
Date: Wed, 15 Apr 2009 14:35:37 -0500
Subject: Level3 funkiness
Anyone else experience sporadic funkiness via
Level3? I can't even reach the main website from who
knows how many networks I've tried. Also friends
and former colleagues have tried to reach the site
to no avail.
One of my machines on AT&T:
# traceroute level3.net
traceroute to level3.net (63.211.236.36), 30 hops max, 40 byte packets
4 cr1.n54ny.ip.att.net (12.122.105.58) 11.285 ms 21.702 ms 21.477 ms
5 ggr2.n54ny.ip.att.net (12.122.131.141) 12.712 ms 10.194 ms 16.393 ms
6 so-8-0-0.car3.NewYork1.Level3.net (4.68.127.149) 9.975 ms 10.019 ms 10.833 ms
7 vlan79.csw2.NewYork1.Level3.net (4.68.16.126) 10.162 ms 10.189 ms 14.474 ms
8 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 15.763 ms 11.166 ms 9.725 ms
9 ae-3-3.ebr4.Washington1.Level3.net (4.69.132.93) 16.139 ms 30.616 ms 16.275 ms
10 ae-64-64.csw1.Washington1.Level3.net (4.69.134.178) 15.684 ms ae-74-74.csw2.Washington1.Level3.net (4.69.134.182) 21.870 ms ae-84-84.csw3.Washington1.Level3.net (4.69.134.186) 28.729 ms
11 ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 17.035 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 17.041 ms ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 21.940 ms
12 ae-2-2.ebr2.Chicago2.Level3.net (4.69.132.69) 31.671 ms 42.407 ms 45.774 ms
13 ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) 31.922 ms 32.115 ms 38.135 ms
14 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 75.265 ms 67.528 ms 67.937 ms
15 ge-9-0.hsa1.Denver1.Level3.net (4.68.107.35) 62.587 ms !H ge-9-1.hsa1.Denver1.Level3.net (4.68.107.99) 62.543 ms !H ge-9-2.hsa1.Denver1.Level3.net (4.68.107.163) 75.797 ms !H
(From Texas through Above.net)
$ traceroute level3.net|tail -n 1
traceroute to level3.net (63.211.236.36), 64 hops max, 40 byte packets
11 ge-6-2.hsa1.Denver1.Level3.net (4.68.107.131) 21.473 ms !H * ge-6-0.hsa1.Denver1.Level3.net (4.68.107.3) 21.547 ms !H
Confirmed it can't be reached from Travelers Ins, The
Hartford, none of my connections. Anyone else seeing
issues? I'm seeing drop off from clients going through
their Atlanta interconnects with Charter and two other
providers, which I can't make sense of. I DO KNOW they
experienced some sort of issue with a TDM switch or so
they said... Very broad statements: "We know teh
interwebs are down please stand by"
I know websites are one thing, but the chances of the
website going down, a TDM switch being wacky and now
clients traversing their networks complaining all at
once seems a little out of the ordinary.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
J. Oquendo
SGFA, SGFE, C|EH, CNDA, CHFI, OSCP
Level3.netに繋がらないんだけど・・・というメール。
Level3.comなら見えるぜという返事や、うちも同じ状況だというメール、アトランタでLevel3とピアしてるうちのISPは見えてるよ、という報告が続々と入ってきています。
とりあえず、Level3.comとLevel3.netは同一ホストなんだけどね・・・
Subject: Level3 funkiness
Anyone else experience sporadic funkiness via
Level3? I can't even reach the main website from who
knows how many networks I've tried. Also friends
and former colleagues have tried to reach the site
to no avail.
One of my machines on AT&T:
# traceroute level3.net
traceroute to level3.net (63.211.236.36), 30 hops max, 40 byte packets
4 cr1.n54ny.ip.att.net (12.122.105.58) 11.285 ms 21.702 ms 21.477 ms
5 ggr2.n54ny.ip.att.net (12.122.131.141) 12.712 ms 10.194 ms 16.393 ms
6 so-8-0-0.car3.NewYork1.Level3.net (4.68.127.149) 9.975 ms 10.019 ms 10.833 ms
7 vlan79.csw2.NewYork1.Level3.net (4.68.16.126) 10.162 ms 10.189 ms 14.474 ms
8 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 15.763 ms 11.166 ms 9.725 ms
9 ae-3-3.ebr4.Washington1.Level3.net (4.69.132.93) 16.139 ms 30.616 ms 16.275 ms
10 ae-64-64.csw1.Washington1.Level3.net (4.69.134.178) 15.684 ms ae-74-74.csw2.Washington1.Level3.net (4.69.134.182) 21.870 ms ae-84-84.csw3.Washington1.Level3.net (4.69.134.186) 28.729 ms
11 ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 17.035 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 17.041 ms ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 21.940 ms
12 ae-2-2.ebr2.Chicago2.Level3.net (4.69.132.69) 31.671 ms 42.407 ms 45.774 ms
13 ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) 31.922 ms 32.115 ms 38.135 ms
14 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 75.265 ms 67.528 ms 67.937 ms
15 ge-9-0.hsa1.Denver1.Level3.net (4.68.107.35) 62.587 ms !H ge-9-1.hsa1.Denver1.Level3.net (4.68.107.99) 62.543 ms !H ge-9-2.hsa1.Denver1.Level3.net (4.68.107.163) 75.797 ms !H
(From Texas through Above.net)
$ traceroute level3.net|tail -n 1
traceroute to level3.net (63.211.236.36), 64 hops max, 40 byte packets
11 ge-6-2.hsa1.Denver1.Level3.net (4.68.107.131) 21.473 ms !H * ge-6-0.hsa1.Denver1.Level3.net (4.68.107.3) 21.547 ms !H
Confirmed it can't be reached from Travelers Ins, The
Hartford, none of my connections. Anyone else seeing
issues? I'm seeing drop off from clients going through
their Atlanta interconnects with Charter and two other
providers, which I can't make sense of. I DO KNOW they
experienced some sort of issue with a TDM switch or so
they said... Very broad statements: "We know teh
interwebs are down please stand by"
I know websites are one thing, but the chances of the
website going down, a TDM switch being wacky and now
clients traversing their networks complaining all at
once seems a little out of the ordinary.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
J. Oquendo
SGFA, SGFE, C|EH, CNDA, CHFI, OSCP
Level3.netに繋がらないんだけど・・・というメール。
Level3.comなら見えるぜという返事や、うちも同じ状況だというメール、アトランタでLevel3とピアしてるうちのISPは見えてるよ、という報告が続々と入ってきています。
とりあえず、Level3.comとLevel3.netは同一ホストなんだけどね・・・
IETF-Digest@Apr 15, 2009
Date: Wed, 15 Apr 2009 09:24:41 -0700
Subject: pickpockets
Ingemar Johansson S wrote:
> Pickpockets:
> Summer in Stockholm is high season for pickpockets who often like to operate in teams, so keep your wallet close.
For those who did not see the spiffy exchange on this topic, at the time of the
Paris IETF, here are some specifics, based on my post hoc learning after being
expertly double-teamed, a few weeks before the Paris IETF, when getting off the
Paris Metro:
Background:
Protection:
There are quite a few online pages that list the same (verbatim) information and
misinformation, including some official police pages.
Personal comments:
1. While it does tend to slow the pickpocket down a bit, putting your
wallet/etc. into your front pocket is not serious protection. That's one of the
things I learned by experience.
2. Carry two sets of ID, money and credit card, in two different places, on
your person. Unless your are thoroughly mugged, you'll only lose one of them.
3. A money belt really does help.
4. Have a /third/ set of ID, money and credit card back in your room, along
with a copy of your passport.
5. Almost anywhere in the world has some risk of your stuff being taken. I
think Japan is probably the only place I'd assume there is almost no risk. If
you are in an unfamiliar place -- /any place/ and not just in a different
country -- stay actively and overtly alert to your surroundings. It's your best
defense. (A bottle of wine tends to defeat this advice.)
5. Perfect protection is impossible. Make the assumption that at least some of
your stuff will get stolen. If you embrace the likelihood beforehand, the
trauma will be a lot smaller when -- not if -- it happens.
6. Don't get freaked out by all this. It does not need to get in the way of
having a great time. Really.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
IETFミーティングがストックホルムであるが、スリに気をつけて！というメールに
スリ対策を丁寧に説明してくれている。
これはIETFに限らず、重要なお知らせ。
日本ではなかなかスリ被害に遭わないが、海外では日常茶飯事。
Subject: pickpockets
Ingemar Johansson S wrote:
> Pickpockets:
> Summer in Stockholm is high season for pickpockets who often like to operate in teams, so keep your wallet close.
For those who did not see the spiffy exchange on this topic, at the time of the
Paris IETF, here are some specifics, based on my post hoc learning after being
expertly double-teamed, a few weeks before the Paris IETF, when getting off the
Paris Metro:
Background:
Protection:
There are quite a few online pages that list the same (verbatim) information and
misinformation, including some official police pages.
Personal comments:
1. While it does tend to slow the pickpocket down a bit, putting your
wallet/etc. into your front pocket is not serious protection. That's one of the
things I learned by experience.
2. Carry two sets of ID, money and credit card, in two different places, on
your person. Unless your are thoroughly mugged, you'll only lose one of them.
3. A money belt really does help.
4. Have a /third/ set of ID, money and credit card back in your room, along
with a copy of your passport.
5. Almost anywhere in the world has some risk of your stuff being taken. I
think Japan is probably the only place I'd assume there is almost no risk. If
you are in an unfamiliar place -- /any place/ and not just in a different
country -- stay actively and overtly alert to your surroundings. It's your best
defense. (A bottle of wine tends to defeat this advice.)
5. Perfect protection is impossible. Make the assumption that at least some of
your stuff will get stolen. If you embrace the likelihood beforehand, the
trauma will be a lot smaller when -- not if -- it happens.
6. Don't get freaked out by all this. It does not need to get in the way of
having a great time. Really.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
IETFミーティングがストックホルムであるが、スリに気をつけて！というメールに
スリ対策を丁寧に説明してくれている。
これはIETFに限らず、重要なお知らせ。
日本ではなかなかスリ被害に遭わないが、海外では日常茶飯事。
RIPE-address-policy-wg@Apr 15, 2009
Date: Wed, 15 Apr 2009 18:57:33 +0200
Subject: [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Dear WG,
this is a rough draft policy proposal. I'd appreciate some feedback before
I decide whether to invoke the formal process.
Summary:
The RIPE NCC is asked to assign an IPv4 /24 for documentation purposes.
Background:
In example configurations, RFCs, training material and other documentation
it is necessary from time to time to include IP addresses, domain names
or even phone numbers as examples. These resources should meet all
syntactical requirements (e.g., be "real" IP addresses), but should not
interfere with assignments or registrations by innocent third parties.
See RFC 4085 (BCP 105) for what could happen in the worst case.
For the DNS, RFC 2606 (BCP 32) has set aside several top level and
second level domain names and the network 192.0.2/24 has been dedicated
for documentation and test purposes by the IANA in the past (see RFC 3330).
RFC 3849 ("IPv6 Address Prefix Reserved for Documentation") documents
APNIC's assignment of 2001:DB8::/32 for the sole use in example texts.
Motivation:
During recent discussion within the IETF, but also on other occasions
in the past, it appeared that a single /24 is often not enough to
support instructive examples. This may include more complex network
designs, or the use of addresses for DNS name servers, where good
practice (see RFC 2182, BCP 16) suggests topological diversity.
Sometimes, address space from RFC 1918 (BCP 5) is used in addition to
or as a replacement for 192.0.2/24, but this is also a source of
confusion due to the special nature of the "private address space".
It also conflicts with the goal to avoid any collision with addresses
used in real life, even if the burden would be spread across many
users of RFC 1918 address space.
Request:
The RIPE NCC is asked to assign and dedicate a /24 that is reasonable
visually distinct from 192.0.2/24 for documentation only purposes.
The network is not to be used and the prefix is never expected to be
announced in any BGP session (cf. 3849).
The new assignment is not intended to serve as a supplement to RFC 1918
address space. It is intentionally left open here whether similar
considerations would suggest an additional assignment in v6 space, as well.
The pros should be obvious to anyone who ever had to write documentation
or example configurations, but there are also some cons:
o another /24 is a waste of space
o just a /24 won't be enough
o this creates yet another bogon
o any invest in IPv4 is a waste of resources, anyway
o nobody knew 192.0.2/24 in the first place, so why add to the confusion?
o this doesn't need a policy proposal, but could be dealt with through
a specially "sponsored" PI assignment
A special action seems cleaner to me than some random PI assignment, but
this is why I'd like to ask the WG for feedback. Also, if anyone is
aware of other address space similar to 192.0.2/24, I'd appreciate a pointer.
Best regards,
Peter
ドキュメント用に192.0.2.0/24というネットワークが用意されているが、
複雑なネットワークのためにもうひとつ別の/24を割り当てようという提案。
なんでプライベートアドレスじゃだめなの？という反論あり。
Subject: [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Dear WG,
this is a rough draft policy proposal. I'd appreciate some feedback before
I decide whether to invoke the formal process.
Summary:
The RIPE NCC is asked to assign an IPv4 /24 for documentation purposes.
Background:
In example configurations, RFCs, training material and other documentation
it is necessary from time to time to include IP addresses, domain names
or even phone numbers as examples. These resources should meet all
syntactical requirements (e.g., be "real" IP addresses), but should not
interfere with assignments or registrations by innocent third parties.
See RFC 4085 (BCP 105) for what could happen in the worst case.
For the DNS, RFC 2606 (BCP 32) has set aside several top level and
second level domain names and the network 192.0.2/24 has been dedicated
for documentation and test purposes by the IANA in the past (see RFC 3330).
RFC 3849 ("IPv6 Address Prefix Reserved for Documentation") documents
APNIC's assignment of 2001:DB8::/32 for the sole use in example texts.
Motivation:
During recent discussion within the IETF, but also on other occasions
in the past, it appeared that a single /24 is often not enough to
support instructive examples. This may include more complex network
designs, or the use of addresses for DNS name servers, where good
practice (see RFC 2182, BCP 16) suggests topological diversity.
Sometimes, address space from RFC 1918 (BCP 5) is used in addition to
or as a replacement for 192.0.2/24, but this is also a source of
confusion due to the special nature of the "private address space".
It also conflicts with the goal to avoid any collision with addresses
used in real life, even if the burden would be spread across many
users of RFC 1918 address space.
Request:
The RIPE NCC is asked to assign and dedicate a /24 that is reasonable
visually distinct from 192.0.2/24 for documentation only purposes.
The network is not to be used and the prefix is never expected to be
announced in any BGP session (cf. 3849).
The new assignment is not intended to serve as a supplement to RFC 1918
address space. It is intentionally left open here whether similar
considerations would suggest an additional assignment in v6 space, as well.
The pros should be obvious to anyone who ever had to write documentation
or example configurations, but there are also some cons:
o another /24 is a waste of space
o just a /24 won't be enough
o this creates yet another bogon
o any invest in IPv4 is a waste of resources, anyway
o nobody knew 192.0.2/24 in the first place, so why add to the confusion?
o this doesn't need a policy proposal, but could be dealt with through
a specially "sponsored" PI assignment
A special action seems cleaner to me than some random PI assignment, but
this is why I'd like to ask the WG for feedback. Also, if anyone is
aware of other address space similar to 192.0.2/24, I'd appreciate a pointer.
Best regards,
Peter
ドキュメント用に192.0.2.0/24というネットワークが用意されているが、
複雑なネットワークのためにもうひとつ別の/24を割り当てようという提案。
なんでプライベートアドレスじゃだめなの？という反論あり。
4/15/2009
GTER@Mar 14, 2009
Date: Tue, 14 Apr 2009 21:37:41 -0300
From: Rodrigo Ristow Branco
Subject: [GTER] Curiosidade - Contador de endere?os IP ainda
dispon?veis
To: Grupo de Trabalho de Engenharia e Operacao de Redes
Message-ID: <49E52C55.6010805@pobox.com>
Content-Type: text/plain; charset=UTF-8
IPv4 Exhaustion Counter (English)
http://inetcore.com/project/ipv4ec/index_en.html
インテック・ネットコア社のIPv4枯渇カウントダウンのお知らせ。
なんで英語ページを案内するんだろう？ブラジル・ポルトガル語版もあるのに。
From: Rodrigo Ristow Branco
Subject: [GTER] Curiosidade - Contador de endere?os IP ainda
dispon?veis
To: Grupo de Trabalho de Engenharia e Operacao de Redes
Message-ID: <49E52C55.6010805@pobox.com>
Content-Type: text/plain; charset=UTF-8
IPv4 Exhaustion Counter (English)
http://inetcore.com/project/ipv4ec/index_en.html
インテック・ネットコア社のIPv4枯渇カウントダウンのお知らせ。
なんで英語ページを案内するんだろう？ブラジル・ポルトガル語版もあるのに。
登録:
投稿 (Atom)
