JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for IPV6-USERS Archives


IPV6-USERS Archives

IPV6-USERS Archives


IPV6-USERS@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

IPV6-USERS Home

IPV6-USERS Home

IPV6-USERS  August 2011

IPV6-USERS August 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: IPv6 Address Blocks (fwd)

From:

Bob Franklin <[log in to unmask]>

Reply-To:

Bob Franklin <[log in to unmask]>

Date:

Thu, 11 Aug 2011 19:29:16 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (66 lines)

On Thu, 11 Aug 2011, Robin Stevens wrote:

> Interesting.  We successfully argued that a /48 was insufficient to 
> avoid a fragmented internal allocation strategy, and I believe Cambridge 
> have subsequently done the same - both of us now have /44s, but perhaps 
> we should have pushed for more :-)

Indeed we did, but the policies under which the Cambridge /44 was 
allocated are quite different from the Oxford one.  I believe the rules 
had changed twice between the two applications!

The main beef was around subnets and internal administration - as I stated 
at my Networkshop talk: we (the central Computing Service) do not act as a 
single central authority on how all subnetting is carried out within the 
university, but act more like an ISP and route blocks of addresses down to 
the colleges and many of the larger internal departments.  When you get 
into that situation, you inevitably waste address space because you grant 
a block that you hope is large enough (but not too large) for their needs 
for the next 10-20 years (perhaps).

Coupled with DNS delegation (which we don't generally do, but I can see it 
happening with increased dynamic usage) then it's much nicer to delegate 
on a nibble boundary, so you're stuck with a /56 or /60.  Even if you 
allocate something smaller, you want to feel fairly confident you won't 
have to give them another 16 subnets (/60) in the future, perhaps.

When we started working all that out, giving internal institutions /56s 
would fit in a /48 but got a bit tight before anything new had come along 
(160-200x /56s = ~65%).  The next /48 up from ours was already allocated 
so there wouldn't be any room to expand, if we ever needed it.

We had quite a bit of trouble getting RIPE to understand the internal 
devolved nature of the university and affiliated institutions - yes 65K 
subnets is enough, but it's difficult to decide on what size block you 
allocate any particular department/college.  One of the nice things about 
IPv6 is supposed to that you can use all this address space to organise 
things on nice boundaries and not grow things piecemeal.

[Or, if you like, make all the mistakes we made with IPv4 back in the 
early 90s all over again.]


> Given that some ISPs are giving out /48s to domestic customers, then it 
> doesn't seem so unreasonable to grant a larger allocation to a large 
> university, with many departments and colleges, each of whom may require 
> multiple internal networks for various groups and applications.

I think the updated RFC that was published in late March / early April 
[the one Rob quoted] revises that and, I'm told, that Andrews and Arnold 
no longer offer a /48 by default to new customers.  I can see that a home 
user might need more than one subnet, but 65K seems silly (especially if 
you consider an ISP having 65K customers would then have used up their 
/32).


All that said, we're moving our office network from 2001:630:200:8100::/64 
to 2001:630:212:100::/64 this week and demonstrating just how easy prefix 
migration is on a subnet!

   - Bob


-- 
  Bob Franklin <[log in to unmask]>              +44 1223 748479
  Network Division, University of Cambridge Computing Service

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
February 2024
December 2023
October 2023
September 2023
June 2023
May 2023
March 2023
January 2023
December 2022
November 2022
June 2022
May 2022
December 2021
April 2021
March 2021
February 2021
December 2020
October 2020
October 2019
August 2019
March 2019
November 2018
August 2018
July 2018
March 2018
February 2018
November 2017
August 2017
June 2017
May 2017
April 2017
January 2017
November 2016
October 2016
September 2016
June 2016
May 2016
January 2016
December 2015
November 2015
October 2015
September 2015
July 2015
October 2014
November 2013
October 2013
August 2013
June 2013
March 2013
February 2013
September 2012
August 2012
July 2012
June 2012
April 2012
February 2012
December 2011
November 2011
October 2011
September 2011
August 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
February 2010
January 2010
December 2009
November 2009
February 2009
December 2008
November 2008
July 2008
June 2008
May 2008
January 2008
December 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
March 2007
2006
2005
2004
2003
2002
2000


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager