Can someone add the new IP addresses to the rviews router?
--
Jay Hanke
CTO, CCIE #19093
Mankato Networks LLC
PO Box 54
619 S Front St
Mankato, MN 56001-3838
Google 530-618-2398
jayhanke(a)mankatonetworks.net
http://www.mankatonetworks.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Thanks for all the work and input on this.
I got a chance to play with the orange squares this morning. I
adjusted the Relative value of the 10G to 1G to 2.64, basically to
make the 10G port cost come out to 1k per solar cycle. The total 10G
at $1440 (1k + 440) seemed to be reasonable.
Remote Switches
I'd further propose that remote switch operators pay their port fee
but not an IP fee unless they are peering as well. Anyone who pays any
fee is a member and has voting rights. Which is a change from our
current requirement of having 1 BGP session. Any AS connected to a
remote switch pays the IP Fee and the port costs are between them and
the remote switch "owner".
Remote Switch owners must provide superuser rights to MICE for their
switches to provide common administration. I'd also argue the
equipment switching must be dedicated. Remote switch operators are
responsible for all the costs associated with running their remote
switches. Addition of future switches requires Board of Governors
approval, and likely some written agreement in the future.
Remote Switches applies to attaching a L2 fabric to the network not
transporting single connections.
I think MICE not purchase or provide any transport period. If other
parties want to offer that service I don't see an issue with it
Grace Period
I'd advocate offering a six month grace for new members on either 1G
or 10G ports for new participants.
Small Networks
Under this model, small networks could connect to a "cheaper" remote
switch so they would have a way to connect and participate in MICE
that's feasible for them. ~$500/year isn't a huge hurdle.
Expansion beyond 511
I think MICE should focus on getting our ducks in a row in 511 for
now. I would be open to "seeding" a second exchange somewhere else in
the Midwest.
Promotion
We should budget something for promotion and holding events.
Organizing a UG is a PITA when you need to get everything for free. In
addition, we may need to chip in for some travel at some point.
Remote Hands
Entering in a contract for 24x7 support is also something we should explore.
--
Jay Hanke
CTO, CCIE #19093
Mankato Networks LLC
PO Box 54
619 S Front St
Mankato, MN 56001-3838
Google 530-618-2398
jayhanke(a)mankatonetworks.net
http://www.mankatonetworks.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Is anyone else going to the ARIN meeting on Thursday in Minneapolis?
--
Jay Hanke
CTO, CCIE #19093
Mankato Networks LLC
PO Box 54
619 S Front St
Mankato, MN 56001-3838
Google 530-618-2398
jayhanke(a)mankatonetworks.net
http://www.mankatonetworks.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
All,
Richard Laager from Wikstrom Telephone and I have put together a
spreadsheet (see link below) detailing the cost breakdown and potential fee
structures for MICE. I've highlighted the input fields in orange (you're
welcome Mike H) and would encourage you to review the values and
assumptions annotated within the sheet.
MICE Cost Breakdown, Oct 2012.xlsx <http://db.tt/aJCZNXGz>
This spreadsheet proposes fees based on the current costs of the exchange.
While slightly simplistic (e.g. no effort was made to account for
inflation), this seemed like a reasonable and mostly-objective path to
calculating the first year of fees. These costs assume that labor is still
donated. The space and power costs are included, even though they're
currently donated for 3 years; the effect of this will be to build up
reserves. These reserves would be to allow for unforeseen events as well as
growth (e.g. adding another switch if we run out of ports). The hardware
costs of the existing switches are included as well, even though the
switches are already paid for. This will build up funding to buy the next
generation of switches (40G or 100G).
Yearly, the Board of Governors ("steering committee") needs to update (or
review the work of a committee which has updated) the inputs to cost
projections. After this first year, since the "expected life" will be one
year less, the hardware purchase costs will need to be updated to account
for costs already recovered. For example, pretend we had only one switch
that cost $10,000, support costs $1,000/year, and we expect to install then
next generation switch in 5 years. The methods used in the spreadsheet
would show we need to recover: 10000 / 5 + 1000 = $3000/year. Next year, if
we are still exactly on, the fees don't change. Since we recovered $2,000
in the first year, we now need to recover: 8000 / 4 + 1000 = $3000/year. As
the best estimates (for the cost of the next generation of switch and the
remaining time until such a switch is necessary) are updated, the costs
will go up or down.
Additionally, Richard and I discussed some policy notes and considerations
and wanted to include the following for your review and comment as well.
*POLICY PROPOSALS:*
*General
*
The term "Resources" refers to physical or logical resources such as IP
addresses, ports, etc.
In the 4th quarter, the rates for Resources for the upcoming year shall be
fixed by the Board of Governors. The new rates shall take effect on January
1.
Future policy action may define a Grace Period (e.g. for new members)
during which fees are waived. This Grace Period is separate from, and in
addition to, the "one month" references below.
*Prorating
*
Annual rates shall be prorated by months only. Resources connected on or
before the 15th of a month shall be billed effective the 1st of that month.
Resources connected after the 15th shall be billed effective the 1st of the
next month. No refunds shall be given for disconnections. Credit is only
given during migrations, as provided below.
*Migrations
*
Additional resources utilized during MICE-initiated migrations are not
billable provided the member complies with MICE's timetable for that
migration.
Members upgrading (not downgrading) the type (speed) of their ports (e.g.
one or more 1G ports to one or more 10G ports) shall be prorated the
difference between the port costs. If the difference is negative, the
credit may be carried forward up to one year. During the period of overlap
between the sets of ports, one month's overlap of the cheaper set shall be
credited; if there is less than one month of overlap, no overlapping
charges apply.
*IPs
*
Upon application, a new member shall be assigned one set of one IPv4
address and one IPv6 address. The IPs are billable one month after the
route servers are configured (unless the member opts out of multi-lateral
peering) and the member is notified of the assignment.
Additional IPv4 and IPv6 addresse sets are billable at the same rate as the
first set. Members may not be assigned more than two sets of addresses
without future policy action.
*Ports
*
Ports are billable once configured and the member is notified of the
assignment, except that ports assigned to new members are billable one
month later.
*Transceivers
*
Transceivers (SFP, SFP+, etc.), when required for ports, must be purchased
from MICE or provided by the member. If purchased from MICE, no Grace
Period applies. If provided, the transceiver must meet MICE's requirements,
which may include a manufacturer or manufacturer compatibility
specification for switch support reasons. Transceivers (once paid for)
remain the property of the member.
Feel free to play around with the numbers and understand the cost
breakdowns for yourself. Let us know if you have questions regarding the
sheet or the included calculations/assumptions.
Thanks!
s
*Shaun Carlson
*Senior Network Engineer | Arvig
ph: (218) 346-8673 | contact: protocol.by/scarlson
em: shaun.carlson(a)arvig.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Connecting via the Mankato Networks switch.
Broadband Visions (BBV)
ASN 25615
New/Primary IPs:
206.108.255.107
2001:504:27:0:0:640F::1
Old/Secondary IPs:
69.147.218.107
2607:fe10:ffff::107
Anthony Anderberg
Sr. Systems Analyst
[NUtel_email_logo_1]
320-234-5239
anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net>
www.nutelecom.net
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Please congratulate Shaun Carlson of Arvig as the new MICE Steering
Committee Member. Shaun will be serving a three year term ending in
Fall 2015.
Shaun replaces Mike Horwath of ipHouse.
Thanks!
--
Jay Hanke
CTO, CCIE #19093
Mankato Networks LLC
PO Box 54
619 S Front St
Mankato, MN 56001-3838
Google 530-618-2398
jayhanke(a)mankatonetworks.net
http://www.mankatonetworks.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
New spreadsheet oncoming about costs and revenue needs for MICE.
Thanks guys!
EX4200-24-T $1900
EX4200-48-T $4200
EX4500 $19,500
Max virtual chassis config is 10 EX4200 series or 2 EX4200 + EX4500 series.
Maintenance fees were in another message and I hope we can keep the discount long term.
Cologix will be approximately $1600 per month for a rack and A+B power at 20A (Mr. Hemphill please correct me).
Is figure three years for ROI. Two years may be better depending on growth plans to cover updates.
--
Mike, via phone
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Here is the IP assignment:
Savage Communications
ASN 23260
Secondary IP: 69.147.218.17 (temp)
Primary IP: 206.108.255.17
Secondary IPv6: 2607:fe10:ffff::17 (temp)
Primary IPv6: 2001:504:27:0:0:5ADC::1
SCI will peer with the route servers at:
206.108.255.1
206.108.255.2
2001:504:27:0:0:D1AF::1
2001:504:27:0:0:D1AF::2
Please configure the route servers.
Thanks!
--
Jay Hanke
CTO, CCIE #19093
Mankato Networks LLC
PO Box 54
619 S Front St
Mankato, MN 56001-3838
Google 530-618-2398
jayhanke(a)mankatonetworks.net
http://www.mankatonetworks.com
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
We've reached the first milestone in the MICE renumbering project.
By now, all peering email contacts have recieved notice of the new IP
addresses, and a timeline and request to have the new IP address setup
as a secondary on their MICE facing interface by today, 10/1/2012.
The timeline also stated that members can now start to schedule their
maintenance windows to shift around their BGP announcements so they
can announce their prefixes with a next-hop IP in the new IP range.
Unfortunately, doing spot checks only about 22% of members seem to
have done the secondary IPv4 setup yet based on ping results.
If you have not yet put your new IP addresses on a secondary IP
on your interface, please do this as-soon-as-possible.
If you do not, and another member does shift their prefix announcement,
your network will have reachability issues to the other member, trying
to get to an IP address your router doesn't know how to reach.
Again, here is the cutover schedule that was emailed out:
Addition of Address Secondary: before 10/1/2012
New Prefix Announcements: after 10/1/2012
Final use of old IP address next-hop: before 11/30/2012
Removal of old IP address range: after 12/1/2012
Project End: 12/31/2012
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1