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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ [ÆóÁö] TTAE.IF-RFC3338 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2005-12-21 ÃÑÆäÀÌÁö 26
ÇѱÛÇ¥Áظí BIA¸¦ »ç¿ëÇÑ µà¾ó½ºÅà ȣ½ºÆ® º¯È¯ ±â¹ý
¿µ¹®Ç¥Áظí Dual Stack Hosts Using
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØÀº "Bump-in-the-API (API)"¶ó°í ºÒ¸®´Â µà¾ó½ºÅà ȣ½ºÆ®µéÀ» À§ÇÑ »õ·Î¿î ¸ÞÄ¿´ÏÁòÀ» ±â¼úÇÑ´Ù. ÀÌ Ç¥Áرâ¼úÀº µà¾ó½ºÅà ȣ½ºÆ®¿¡ Àû¿ëµÇ¸ç, API º¯È¯±â¸¦ ¼ÒÄÏ API ¸ðµâ°ú TCP/IP ¸ðµâ »çÀÌ¿¡ À§Ä¡½ÃÄÑ IPv4 È£½ºÆ® API ±â´ÉÀ» IPv6 ¼ÒÄÏ API ±â´ÉÀ¸·Î º¯È¯ÇÑ´Ù. ¹°·Ð ¹Ý´ëÀÇ °æ¿ìµµ °¡´ÉÇÏ´Ù. ÀÌ ¸ÞÄ¿´ÏÁòÀÌ °¡Áö´Â °¡Àå Áß¿äÇÑ Á¡Àº IP Çì´õÀÇ º¯È¯ ¾øÀÌ °£·«È­µÇ¾ú´Ù´Â °ÍÀÌ´Ù. µà¾ó½ºÅà ȣ½ºÆ®»óÀÇ IPv4 ÀÀ¿ëµéÀÌ ´Ù¸¥ IPv6 È£½ºÆ®µé°ú Åë½ÅÇÏ´Â ÀýÂ÷¸¦ »ìÆ캸¸é,¸ÕÀú IPv4 ÀÀ¿ëµé·ÎºÎÅÍÀÇ ¼ÒÄÏ API ±â´ÉµéÀ» API º¯È¯±â°¡ °ËÃâÇÑ´Ù. °ËÃâµÇ¸é, IPv6 È£½ºÆ®µé°úÀÇ Åë½ÅÀ» À§ÇØ IPv6 ¼ÒÄÏ API ±â´ÉµéÀÌ ±¸µ¿µÈ´Ù. IPv4 ÀÀ¿ë°ú »ó´ë IPv6 È£½ºÆ®µé°úÀÇ Åë½ÅÀ» Áö¿øÇϱâ À§ÇØ, ÁÖ¼Ò Ç® »óÀÇ IPv4 ÁÖ¼Ò°¡ API º¯È¯±â³»ÀÇ ³×ÀÓ ¸®Á¹¹ö¸¦ ÅëÇØ ÇÒ´çµÈ´Ù.
¿µ¹®³»¿ë¿ä¾à This standard specifies a new mechanism of dual stack hosts called Bump-in-the-API(BIA) technique. The BIA technique inserts an API translator between the socket API module and the TCP/IP module in the dual stack hosts, so that it translates the IPv4 socket API function into IPv6 socket API function and vice versa. With this mechanism, the translation can be simplified without IP header translation. When IPv4 applications on the dual stack communicate with other IPv6 hosts, the API translator detects the socket API functions from IPv4 applications and invokes the IPv6 socket API functions to communicate with the IPv6 hosts, and vice versa. In order to support communication between IPv4 applications and the target IPv6 hosts, pooled IPv4 addresses will be assigned through the name resolver in the API translator.
±¹Á¦Ç¥ÁØ IETF RFC 3338
°ü·ÃÆÄÀÏ TTAE_IF-RFC3338.zip
Ç¥ÁØÀÌ·Â
±¸ºÐ ÀÏÀÚ Ç¥ÁعøÈ£ º¯°æ³»¿ª
°³Á¤ 2012-12-21 TTAE.IF-RFC6535

ÀÌÀü
°øµ¿ÁÖÅÃÀÇ ÃÊ°í¼ÓÁ¤º¸Åë½Å¼³ºñ ¼³Ä¡°ø°£ ±â¼úÇ¥ÁØ
´ÙÀ½
À̵¿ÀüÈ­¿ë ¹«¼±¼³ºñÀÇ RF Ç¥ÁØÃøÁ¤¹ý