Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAE.IF-RFC3654 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2007-12-26 ÃÑÆäÀÌÁö 32
ÇѱÛÇ¥Áظí IP Á¦¾î¿Í Æ÷¿öµùÀÇ ºÐ¸®¸¦ À§ÇÑ ¿ä±¸»çÇ×
¿µ¹®Ç¥Áظí Requirements for Separation of IP Control and Forwarding
Çѱ۳»¿ë¿ä¾à IP ³×Æ®¿öÅ© ¿ä¼Ò´Â ´Ù¾çÇÏ°í ¸¹Àº ³í¸®ÀûÀ¸·Î ºÐ¸®µÈ °³Ã¼µé·Î ±¸¼ºµÇ¾îÀÖ´Ù. ÀÌ·¯ÇÑ
¿ä¼Ò Áß ÁÖ¿äÇÑ µÎ °¡Áö°¡ Á¸ÀçÇϴµ¥, Çϳª´Â Á¦¾î ´Ü°è ÄÄÆ÷³ÍÆ®¿Í Æ÷¿öµù ´Ü°èÀÇ ÄÄ
Æ÷³ÍÆ® ÀÌ´Ù.
ÀϹÝÀûÀ¸·Î, Æ÷¿öµù ´Ü°è ÄÄÆ÷³ÍÆ®µé·Î´Â ASIC, ³×Æ®¿öÅ© ÇÁ·Î¼¼¼­, ¶Ç´Â ¸ðµç µ¥ÀÌÅÍ
°æ·ÎÀÇ °áÁ¤ ¿¬»êÀ» ´Ù·ç´Â ÀϹÝÀû ¸ñÀûÀÇ ÇÁ·Î¼¼¼­ ±â¹ÝÀÇ ´Ü¸»µéÀÌ´Ù. ÀÌ¿Í ¹Ý´ë·Î,
Á¦¾î ´Ü°è ÄÄÆ÷³ÍÆ®µéÀº ÀüÇüÀûÀ¸·Î ¶ó¿ìÆà ó¸® ¹× ½Ã±×³Î¸µ ÇÁ·ÎÅäÄݵéó·³ Á¦¾î ±â
´ÉµéÀ» Á¦°øÇØÁÖ´Â ÀϹÝÀû ¸ñÀûÀÇ ÇÁ·Î¼¼¼­µéÀ» ±â¹ÝÀ¸·Î ÇÏ°í ÀÖ´Ù.
ÀÌ·¯ÇÑ ºÐ¸®ÀÇ ¸ñÀûÀ» À§ÇØ, ¿ì¸®´Â ¶ó¿ìÅÍ°¡ Á¦¾î¿Í Æ÷¿öµù ´Ü°è ºÐ¸®ÀÇ ÄÁ¼ÁÀ» Áö¿ø
Çϵµ·Ï ±¸Á¶ÀûÀÎ °í·Á¸¦ ÇØ¾ß ÇÑ´Ù. ÀüÇüÀûÀ¸·Î ÀÌ·¯ÇÑ µð¹ÙÀ̽ºµéÀÇ ±¸Á¶´Â ÀÌ·¯ÇÑ ¸ð
µç ±â´ÉµéÀÌ ÇϳªÀÇ ÅëÇÕü·Î ¿¬°áµÇ¾î ÀÖ´Ù.
¿µ¹®³»¿ë¿ä¾à An IP network element is composed of numerous logically separate entities. Two
primary types of network element components exist: control-plane components and
forwarding-plane components.
In general, forwarding-plane components are ASIC, network-processor, or generalpurpose
processor-based devices that handle all data path operations. Conversely,
control-plane components are typically based on general-purpose processors that
provide control functionality such as the processing of routing or signaling protocols.
For the purpose of illustration, let us consider the architecture of a router to illustrate
the concept of separate control and forwarding planes. Typically, the architecture of
these devices combines all of this functionality into a single functional whole with
respect to external entities.
±¹Á¦Ç¥ÁØ IETF RFC 3654
°ü·ÃÆÄÀÏ TTAE_IF-RFC3654_[2].zip TTAE_IF-RFC3654_[2].zip            

ÀÌÀü
ºí·Ï ¾ÏÈ£ ¿î¿µ ¸ðµå: Counter with CBC-MAC(CCM)
´ÙÀ½
À§Ä¡Á¤º¸ ÇÁ¶óÀ̹ö½Ã(Geopriv) ¿ä±¸»çÇ×