On 08.12.19 11:40, 정치영 wrote:

what is the most standard subnet length that always can be guaranteed through Internet. less than /24 bit ?

nothing can always be guaranteed in life or the internet. but /24s do seem to be fairly widely used. so they probably work for the folk announcing them. randy

On Dec 18, 2008, at 9:40 PM, 정치영 wrote:

Hi everyone,

I'm going to rebuild IP allocation policy of my company and I am looking for some standard reference for my policy. I have already studied some standard like RFC1518, RIPE181, RFC2050 and I got it is very important to maintain hierachy structure. However, what I am really wondering is what is the most standard subnet length that always can be guaranteed through Internet. less than /24 bit ?

Depends on how you count it - /24 is definitely the most numerous from where I sit. You might find this interesting : http://www.multicasttech.com/status/cidr.html Regards Marshall

I could not find any documents about that, which subnet length is most proper value and pursue internet standard policy ?

Could anyone give me some information guides ?

Best wishes, Chiyoung ============================================= Chi-Young Joung SAMSUNG NETWORKS Inc. Email: lionair@samsung.com Tel +82 70 7015 0623, Mobile +82 17 520 9193 Fax +82 70 7016 0031 =============================================

On Fri, Dec 19, 2008 at 02:40:47AM +0000, l l9l
wrote:

However, what I am really wondering is what is the most standard subnet length that always can be guaranteed through Internet. less than /24 bit ?

while one can get away w/ /24s (if that is all one has) for many places, I suspect that there will be increasing pressure to drop more specific /24s as folks routing tables grow. your question, "...length that can be guaranteed through the Internet." argues for fairly short netmasks, e.g. a /16 is likley to be accepted by most folks while very short masks, e.g. /8 or smaller are likly to be seen with some level of consideration since so very few prefixes of that size are likely to be origin-sourced (often proxy aggregates from transit parties)... as others have pointed out - this "acceptable" value is fluid, changing over time and variable between ISPs. Creating a static policy is likely to be flawed. --bill (crawling out from under his rock, blinking in the bright lights)