CIDR - Revision history

Onnowpurbo at 09:03, 22 December 2018

2018-12-22T09:03:17Z

← Older revision		Revision as of 09:03, 22 December 2018
Line 1:		Line 1:
			Classless Inter-Domain Routing (CIDR /ˈsaɪdər, ˈsɪ-/) is a method for allocating IP addresses and IP routing. The Internet Engineering Task Force introduced CIDR in 1993 to replace the previous addressing architecture of classful network design in the Internet. Its goal was to slow the growth of routing tables on routers across the Internet, and to help slow the rapid exhaustion of IPv4 addresses.[1][2]

			IP addresses are described as consisting of two groups of bits in the address: the most significant bits are the network prefix, which identifies a whole network or subnet, and the least significant set forms the host identifier, which specifies a particular interface of a host on that network. This division is used as the basis of traffic routing between IP networks and for address allocation policies.

			Whereas classful network design for IPv4 sized the network prefix as one or more 8-bit groups, resulting in the blocks of Class A, B, or C addresses, Classless Inter-Domain Routing allocates address space to Internet service providers and end users on any address bit boundary. In IPv6, however, the interface identifier has a fixed size of 64 bits by convention, and smaller subnets are never allocated to end users.

			CIDR encompasses several concepts. It is based on the variable-length subnet masking (VLSM) technique, which allows the specification of arbitrary-length prefixes. CIDR introduced a new method of representation for IP addresses, now commonly known as CIDR notation, in which an address or routing prefix is written with a suffix indicating the number of bits of the prefix, such as 192.0.2.0/24 for IPv4, and 2001:db8::/32 for IPv6. CIDR introduced an administrative process of allocating address blocks to organizations based on their actual and short-term projected needs. The aggregation of multiple contiguous prefixes resulted in supernets in the larger Internet, which whenever possible are advertised as aggregates, thus reducing the number of entries in the global routing table.




	'''[[Classless Inter-Domain Routing]]''' ('''[[CIDR]]''') adalah metoda untuk mengalokasikan [[IP address]] dan routing paket [[Internet Protocol]]. CIDR di ajukan pada tahun 1993 untuk menggantikan cara pengalamatan yang lama yang menggunakan disain arsitektur [[classful network]] di [[Internet]] dengan tujuan untuk memperlambat pertumbuhan router yang ada di Internet, juga menunda kehabisan / kekurangan dari [[IPv4]] address.		'''[[Classless Inter-Domain Routing]]''' ('''[[CIDR]]''') adalah metoda untuk mengalokasikan [[IP address]] dan routing paket [[Internet Protocol]]. CIDR di ajukan pada tahun 1993 untuk menggantikan cara pengalamatan yang lama yang menggunakan disain arsitektur [[classful network]] di [[Internet]] dengan tujuan untuk memperlambat pertumbuhan router yang ada di Internet, juga menunda kehabisan / kekurangan dari [[IPv4]] address.

Onnowpurbo: /* Pranala Luar */

2013-10-31T02:41:46Z

Pranala Luar

← Older revision		Revision as of 02:41, 31 October 2013
Line 316:		Line 316:
	* RFC 4291 - IP Version 6 Addressing Architecture		* RFC 4291 - IP Version 6 Addressing Architecture
	* RFC 3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links		* RFC 3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links
	* [http://www.cidr-report.org/ CIDR Report] (~~updated daily~~)		* [http://www.cidr-report.org/ CIDR Report] (update setiap hari)

	==Pranala Menarik==		==Pranala Menarik==

Onnowpurbo: /* External links */

2013-10-31T02:41:26Z

External links

← Older revision		Revision as of 02:41, 31 October 2013
Line 311:		Line 311:
	* RFC 4632, ''Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan'', V. Fuller, T. Li, August 2006		* RFC 4632, ''Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan'', V. Fuller, T. Li, August 2006

	==~~External links~~==		==Pranala Luar==

	* RFC 2317 - Classless IN-ADDR.ARPA delegation		* RFC 2317 - Classless IN-ADDR.ARPA delegation
	* RFC 4291 - IP Version 6 Addressing Architecture		* RFC 4291 - IP Version 6 Addressing Architecture
	* RFC 3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links		* RFC 3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links
	* [http://www.cidr-report.org/ CIDR Report] (updated daily)		* [http://www.cidr-report.org/ CIDR Report] (updated daily)


	==Pranala Menarik==		==Pranala Menarik==

Onnowpurbo: /* References */

2013-10-31T02:41:05Z

References

← Older revision		Revision as of 02:41, 31 October 2013
Line 304:		Line 304:
	(*) Catatan untuk route yang lebih besar dari /31 atau /32, 2 IP perlu di buang dari jumlah address yang tersedi - address terbesar biasanya digunakan sebagai broadcast address, sementara address terkecil biasanya digunakan untuk mengidentifikasi network itu sendiri / network address. Lihat RFC 1812 untu keterangan yang lebih rinci. Biasanya IP gateway akan mengambil satu address, akibatnya kita biasanya membuang tiga (3) address dari total IP dalam sebuah subnet yang dapat digunakan.		(*) Catatan untuk route yang lebih besar dari /31 atau /32, 2 IP perlu di buang dari jumlah address yang tersedi - address terbesar biasanya digunakan sebagai broadcast address, sementara address terkecil biasanya digunakan untuk mengidentifikasi network itu sendiri / network address. Lihat RFC 1812 untu keterangan yang lebih rinci. Biasanya IP gateway akan mengambil satu address, akibatnya kita biasanya membuang tiga (3) address dari total IP dalam sebuah subnet yang dapat digunakan.

	==~~References~~==		==Referensi==

	* RFC 1518, ''An Architecture for IP Address Allocation with CIDR'', Y. Rekhter, T. Li (Eds.), September 1993		* RFC 1518, ''An Architecture for IP Address Allocation with CIDR'', Y. Rekhter, T. Li (Eds.), September 1993

Onnowpurbo: /* Agregasi Prefix */

2013-10-31T02:40:46Z

Agregasi Prefix

← Older revision		Revision as of 02:40, 31 October 2013
Line 58:		Line 58:
	==Agregasi Prefix==		==Agregasi Prefix==

	CIDR memungkinkan kita untuk memperoleh "agregasi prefix routing" yang lebih hasil, juga di kenal sebagai ''[[supernetting]]'' atau ''route summarization''. ~~For example~~, ~~sixteen contiguous~~ /24 ~~networks~~ (~~formerly Class~~ C) ~~can be aggregated and advertised to a larger network as a single~~ /20 ~~route, if the first~~ 20 ~~bits of their~~ network ~~addresses match~~. ~~Two aligned contiguous~~ /~~20s may then be aggregated to a~~ /19, ~~and so forth~~. ~~This allows a significant reduction in the number of routes that have to be advertised~~.		CIDR memungkinkan kita untuk memperoleh "agregasi prefix routing" yang lebih hasil, juga di kenal sebagai ''[[supernetting]]'' atau ''route summarization''. Contoh, enam belas /24 network (dulu Kelas C) yang tersambung satu sama lain dapat di perkenalkan sebagai sebuah route /20 jika 20 bit pertama dari network address mereka sama persis. Dua network /20 yang berurutan dapat di gabung menjadi /19, dan seterusnya. Hal ini memungkinkan pengurangan yang sangat luar biasa dari route yang harus di perkenalkan ke jaringan.


	{\| border="1" cellpadding=2 style="border-collapse: collapse"		{\| border="1" cellpadding=2 style="border-collapse: collapse"
	\|+ IPv4 CIDR		\|+ IPv4 CIDR
	!IP/CIDR		!IP/CIDR
	!Δ ~~to last~~ IP ~~addr~~		!Δ ke IP address terakhir
	!Mask		!Mask
	!~~Hosts~~ (*)		!Host (*)
	!~~Class~~		!Kelas
	!~~Notes~~		!Catatan
	\|-		\|-
	\|a.b.c.d'''/32'''		\|a.b.c.d'''/32'''
Line 301:		Line 302:
	\|}		\|}

	(*) ~~Note that for routed subnets bigger than~~ /31 or /32, 2 ~~needs to be subtracted from the number of available addresses~~ - ~~the largest~~ address ~~is (conventionally) used as the~~ broadcast address, ~~and typically the smallest~~ address ~~is used to identify the~~ network ~~itself~~. ~~See~~ RFC 1812 ~~for more detail~~. ~~It is also common for the~~ gateway ~~IP for that subnet to use an~~ address, ~~meaning that you would subtract~~ 3 ~~from the number of usable hosts that can be used on the~~ subnet.		(*) Catatan untuk route yang lebih besar dari /31 atau /32, 2 IP perlu di buang dari jumlah address yang tersedi - address terbesar biasanya digunakan sebagai broadcast address, sementara address terkecil biasanya digunakan untuk mengidentifikasi network itu sendiri / network address. Lihat RFC 1812 untu keterangan yang lebih rinci. Biasanya IP gateway akan mengambil satu address, akibatnya kita biasanya membuang tiga (3) address dari total IP dalam sebuah subnet yang dapat digunakan.

	==References==		==References==

Onnowpurbo: /* Prefix aggregation */

2013-10-31T02:27:30Z

Prefix aggregation

← Older revision		Revision as of 02:27, 31 October 2013
Line 56:		Line 56:
	A [[Subnetwork\|subnet mask]] is a [[Mask (computing)\|bitmask]] that encodes the prefix length in quad-dotted notation: 32 bits, starting with a number of 1 bits equal to the prefix length, ending with 0 bits, and encoded in four-part dotted-decimal format. A subnet mask encodes the same information as a prefix length, but predates the advent of CIDR. However, in CIDR notation, the prefix bits are always contiguous, whereas subnet masks may specify non-contiguous bits. However, this has no practical advantage for increasing efficiency.		A [[Subnetwork\|subnet mask]] is a [[Mask (computing)\|bitmask]] that encodes the prefix length in quad-dotted notation: 32 bits, starting with a number of 1 bits equal to the prefix length, ending with 0 bits, and encoded in four-part dotted-decimal format. A subnet mask encodes the same information as a prefix length, but predates the advent of CIDR. However, in CIDR notation, the prefix bits are always contiguous, whereas subnet masks may specify non-contiguous bits. However, this has no practical advantage for increasing efficiency.

	==Prefix ~~aggregation~~==		==Agregasi Prefix==
	CIDR ~~provides the possibility of fine-grained ''~~routing ~~prefix aggregation''~~, ~~also known as~~ ''[[supernetting]]'' or ''route summarization''. For example, sixteen contiguous /24 networks (formerly Class C) can be aggregated and advertised to a larger network as a single /20 route, if the first 20 bits of their network addresses match. Two aligned contiguous /20s may then be aggregated to a /19, and so forth. This allows a significant reduction in the number of routes that have to be advertised.
			CIDR memungkinkan kita untuk memperoleh "agregasi prefix routing" yang lebih hasil, juga di kenal sebagai ''[[supernetting]]'' atau ''route summarization''. For example, sixteen contiguous /24 networks (formerly Class C) can be aggregated and advertised to a larger network as a single /20 route, if the first 20 bits of their network addresses match. Two aligned contiguous /20s may then be aggregated to a /19, and so forth. This allows a significant reduction in the number of routes that have to be advertised.

	{\| border="1" cellpadding=2 style="border-collapse: collapse"		{\| border="1" cellpadding=2 style="border-collapse: collapse"
Line 301:		Line 302:

	(*) Note that for routed subnets bigger than /31 or /32, 2 needs to be subtracted from the number of available addresses - the largest address is (conventionally) used as the broadcast address, and typically the smallest address is used to identify the network itself. See RFC 1812 for more detail. It is also common for the gateway IP for that subnet to use an address, meaning that you would subtract 3 from the number of usable hosts that can be used on the subnet.		(*) Note that for routed subnets bigger than /31 or /32, 2 needs to be subtracted from the number of available addresses - the largest address is (conventionally) used as the broadcast address, and typically the smallest address is used to identify the network itself. See RFC 1812 for more detail. It is also common for the gateway IP for that subnet to use an address, meaning that you would subtract 3 from the number of usable hosts that can be used on the subnet.



	==References==		==References==

Onnowpurbo: /* See also */

2013-10-31T02:26:00Z

Onnowpurbo: /* Latar Belakang */

2013-10-31T02:24:32Z

Latar Belakang

← Older revision		Revision as of 02:24, 31 October 2013
Line 16:		Line 16:
	Sebuah [[IP address]] dapat dilihat sebagai dua bagian: sebuah prefix yang mengidentifikasi network yang di ikuti oleh identifikasi mesin / host dalam network tersebut. Dalam bahasa sederhana kita dapat melihat sebagai kode area (prefix) dan nomor pesawat telepon (host).		Sebuah [[IP address]] dapat dilihat sebagai dua bagian: sebuah prefix yang mengidentifikasi network yang di ikuti oleh identifikasi mesin / host dalam network tersebut. Dalam bahasa sederhana kita dapat melihat sebagai kode area (prefix) dan nomor pesawat telepon (host).

	An IP address ~~is interpreted as composed of two parts~~: ~~a network-identifying~~ prefix ~~followed by a host identifier within that network~~. In the prior classful network architecture, IP address allocations were based on octet (8-bit) boundary segments of the 32-bit IP address, forcing either 8, 16, or 24-bit network prefixes. Thus, the smallest allocation and routing block contained only 256 addresses—too small for most enterprises, and the next larger block contained 65,536 addresses—too large to be used efficiently by even large organizations. This led to inefficiencies in address use as well as routing because the large number of allocated small (class-C) networks with individual route announcements, being geographically dispersed with little opportunity for [[Supernet\|route aggregation]], created heavy demand on routing equipment.		Pada arsitektur yang sebelumnya, alokasi IP address berdasarkan batasan 8 bit dalam 32 bit IP address, yang memaksa prefix:
			* prefix 8 bit, kelas A.
			* prefix 16 bit, kelas B.
			* prefix 24 bit, kelas C.

			In the prior classful network architecture, IP address allocations were based on octet (8-bit) boundary segments of the 32-bit IP address, forcing either 8, 16, or 24-bit network prefixes. Thus, the smallest allocation and routing block contained only 256 addresses—too small for most enterprises, and the next larger block contained 65,536 addresses—too large to be used efficiently by even large organizations. This led to inefficiencies in address use as well as routing because the large number of allocated small (class-C) networks with individual route announcements, being geographically dispersed with little opportunity for [[Supernet\|route aggregation]], created heavy demand on routing equipment.

	Classless Inter-Domain Routing is based on ''variable-length subnet masking'' (VLSM) to allow allocation on arbitrary-length prefixes. Variable-length subnet masks are mentioned in RFC 950 (1985).		Classless Inter-Domain Routing is based on ''variable-length subnet masking'' (VLSM) to allow allocation on arbitrary-length prefixes. Variable-length subnet masks are mentioned in RFC 950 (1985).

Onnowpurbo at 02:21, 31 October 2013

2013-10-31T02:21:32Z

← Older revision		Revision as of 02:21, 31 October 2013
Line 13:		Line 13:

	Untuk mengatasi keterbatasan tersebut, tahun 1993 [[Internet Engineering Task Force]] mempublikasikan beberapa standard, RFC 1518 dan RFC 1519, untuk mendefinisikan konsep baru dalam mengalokasikan blok IP address dan metoda baru untuk routing paket IPv4. Versi terbaru dari spesifikasi tersebut dipublikasikan sebagai RFC 4632 tahun 2006.		Untuk mengatasi keterbatasan tersebut, tahun 1993 [[Internet Engineering Task Force]] mempublikasikan beberapa standard, RFC 1518 dan RFC 1519, untuk mendefinisikan konsep baru dalam mengalokasikan blok IP address dan metoda baru untuk routing paket IPv4. Versi terbaru dari spesifikasi tersebut dipublikasikan sebagai RFC 4632 tahun 2006.

			Sebuah [[IP address]] dapat dilihat sebagai dua bagian: sebuah prefix yang mengidentifikasi network yang di ikuti oleh identifikasi mesin / host dalam network tersebut. Dalam bahasa sederhana kita dapat melihat sebagai kode area (prefix) dan nomor pesawat telepon (host).

	An IP address is interpreted as composed of two parts: a network-identifying prefix followed by a host identifier within that network. In the prior classful network architecture, IP address allocations were based on octet (8-bit) boundary segments of the 32-bit IP address, forcing either 8, 16, or 24-bit network prefixes. Thus, the smallest allocation and routing block contained only 256 addresses—too small for most enterprises, and the next larger block contained 65,536 addresses—too large to be used efficiently by even large organizations. This led to inefficiencies in address use as well as routing because the large number of allocated small (class-C) networks with individual route announcements, being geographically dispersed with little opportunity for [[Supernet\|route aggregation]], created heavy demand on routing equipment.		An IP address is interpreted as composed of two parts: a network-identifying prefix followed by a host identifier within that network. In the prior classful network architecture, IP address allocations were based on octet (8-bit) boundary segments of the 32-bit IP address, forcing either 8, 16, or 24-bit network prefixes. Thus, the smallest allocation and routing block contained only 256 addresses—too small for most enterprises, and the next larger block contained 65,536 addresses—too large to be used efficiently by even large organizations. This led to inefficiencies in address use as well as routing because the large number of allocated small (class-C) networks with individual route announcements, being geographically dispersed with little opportunity for [[Supernet\|route aggregation]], created heavy demand on routing equipment.

Onnowpurbo: /* Pranala Menarik */

2013-10-31T02:18:58Z

Pranala Menarik

← Older revision		Revision as of 02:18, 31 October 2013
Line 319:		Line 319:
	** [[Routing Information Protocol]] ([[RIP]])		** [[Routing Information Protocol]] ([[RIP]])
	** [[Open Shortest Path First]] ([[OSPF]])		** [[Open Shortest Path First]] ([[OSPF]])
			** [[Optimized Link State Routing]] ([[OLSR]])
	* [[Alamat IP]] / [[IP Address]]		* [[Alamat IP]] / [[IP Address]]
	* [[Classless Inter-Domain Routing]] ([[CIDR]])		* [[Classless Inter-Domain Routing]] ([[CIDR]])
	* [[Network Address Translation]] ([[NAT]])		* [[Network Address Translation]] ([[NAT]])

← Older revision		Revision as of 02:26, 31 October 2013
Line 302:		Line 302:
	(*) Note that for routed subnets bigger than /31 or /32, 2 needs to be subtracted from the number of available addresses - the largest address is (conventionally) used as the broadcast address, and typically the smallest address is used to identify the network itself. See RFC 1812 for more detail. It is also common for the gateway IP for that subnet to use an address, meaning that you would subtract 3 from the number of usable hosts that can be used on the subnet.		(*) Note that for routed subnets bigger than /31 or /32, 2 needs to be subtracted from the number of available addresses - the largest address is (conventionally) used as the broadcast address, and typically the smallest address is used to identify the network itself. See RFC 1812 for more detail. It is also common for the gateway IP for that subnet to use an address, meaning that you would subtract 3 from the number of usable hosts that can be used on the subnet.

	~~==See also==~~
	*[[Internet Protocol Suite]]

	==References==		==References==