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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAE.IF-RFC3053 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2005-12-21 ÃÑÆäÀÌÁö 23
ÇѱÛÇ¥Áظí IPv6 ÅͳΠºê·ÎÄ¿
¿µ¹®Ç¥Áظí IPv6 Tunnel Broker
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØÀº ÅͳΠºê·ÎÄ¿¶ó´Â Àü¿ë ¼­¹ö¸¦ ±¸Ãà, »ç¿ëÀÚÀÇ ÅͳΠ¿äûÀ» ÀÚµ¿À¸·Î °ü¸®ÇÏ´ÂIPv6 ÅͳΠºê·ÎÄ¿ ¸ÞÄ¿´ÏÁòÀ» Á¤ÀÇÇÑ °ÍÀÌ´Ù.ÅͳΠºê·ÎÄ¿´Â ÀÌ¹Ì IPv4 ÀÎÅͳݿ¡ ¿¬°áµÈ »ç¿ëÀÚ¿¡°Ô IPv6 ¿¬°áÀ» Á¦°øÇÏ´Â °¡»ó IPv6 ISP °³³äÀ¸·Î¼­, »ç¿ëÀÚ¸¦ À§ÇØ ÅͳÎÀÇ »ý¼º, ¼öÁ¤ ¹× »èÁ¦¸¦ °ü¸®ÇÑ´Ù. ÅͳΠ¼­¹ö´Â ÅͳÎÀÌ »ý¼º, ¼öÁ¤ ¶Ç´Â »èÁ¦µÇ¾î¾ß ÇÒ ¶§¸¶´Ù °ü·Ã ÅͳΠ¼­¹ö¿¡ ¼³Á¤ ¸í·ÉÀ» º¸³½´Ù. ÅͳΠ¼­¹ö´Â ±Û·Î¹ú ÀÎÅͳݿ¡ ¿¬°áµÈ µà¾ó ½ºÅà ¶ó¿ìÅͷμ­, ÅͳΠºê·ÎÄ¿·ÎºÎÅÍ ¼³Á¤ ¸í·ÉÀ» ¹ÞÀ¸¸é ÅͳΠ¼­¹ö´Â °¢ ÅͳÎÀÇ ¼­¹ö ÃøÀ» ¼öÁ¤ ¶Ç´Â »èÁ¦ÇÑ´Ù.
ÅͳΠºê·ÎÄ¿ ¼­ºñ½ºÀÇ Å¬¶óÀ̾ðÆ®´Â IPv4 ÀÎÅͳݿ¡ ¿¬°áµÈ µà¾ó ½ºÅà IPv6 ³ëµå·Î¼­,Ŭ¶óÀ̾ðÆ®°¡ ÅͳΠºê·ÎÄ¿¿¡ Á¢±ÙÇÏ¸é ¿ì¼± ÀûÀýÇÑ »ç¿ëÀÚ ÀÎÁõ, Çã°¡ ¹× °è»êÀ» ¼öÇàÇÒ ¼ö ÀÖµµ·Ï ID¿Í Áõ¸í¼­¸¦ Á¦°øÇϵµ·Ï ¿ä±¸ÇÑ´Ù. ¼­ºñ½º Á¢±ÙÀÌ Çã°¡µÈ Ŭ¶óÀ̾ðÆ®´Â IPv6 Åͳθµ ¹× ±âŸ ÇÊ¿äÇÑ ¼­ºñ½º¸¦ À§ÇÑ Á¤º¸¸¦ ÅͳΠºê·ÎÄ¿¿¡°Ô Á¦°øÇÑ´Ù. ÅͳΠºê·ÎÄ¿´Â Ŭ¶óÀ̾ðÆ®ÀÇ ¿äûÀ» °ü¸®Çϸ鼭 ³×Æ®¿öÅ© Ãø¿¡¼­ ½ÇÁ¦ ÅͳΠÁ¾´ÜÁ¡À¸·Î »ç¿ëµÉ ÅͳΠ¼­¹ö¸¦ ÁöÁ¤ÇÏ°í ÅͳΠ¼³Á¤°ú °ü·ÃµÈ ÀÛ¾÷À» ¼öÇàÇÑ´Ù. ÀÌ»óÀÇ ¼³Á¤ ´Ü°è°¡ ¼öÇàµÇ°í ³ª¸é, Ŭ¶óÀ̾ðÆ® È£½ºÆ®¿Í ¶ó¿ìÅÍ·Î ¼±ÅÃµÈ ÅͳΠ¼­¹ö°£¿¡ IPv6-in-IPv4 ÅͳÎÀÌ ¼³Á¤µÇ¾î ÀÛµ¿µÇ¹Ç·Î ÅͳΠºê·ÎÄ¿ »ç¿ëÀÚ´Â 6Bone ¶Ç´Â ÅͳΠ¼­¹ö°¡ ¿¬°áµÈ ±âŸ ÀÓÀÇÀÇ IPv6 ³×Æ®¿öÅ©¿¡ Á¢±ÙÇÒ ¼ö ÀÖ°Ô µÈ´Ù.
¿µ¹®³»¿ë¿ä¾à This standard describes IPv6 Tunnel Broker mechanism that automatically manages the request of IPv6 tunnel configuration with a specified server. Tunnel Broker can be seen as virtual IPv6 ISPs, providing IPv6 connectivity to users already connected to the IPv4 Internet. To do this, IPv6 Tunnel Broker manages tunnel creation, modification and deletion on behalf of user. It sends configuration orders to the relevant tunnel server whenever a tunnel has to be created, modified and deleted. A Tunnel Server is a dual-stack (IPv4 & IPv6) router connected to the global Internet. Upon receipt of a configuration order coming from the Tunnel Broker, it creates modifies or deletes the server side of each tunnel. The client of the Tunnel Broker service is a dual-stack IPv6 node (host or router) connected to the IPv4 Internet. Approaching the Tunnel Broker, the client should be asked first of all to provide its identity and credentials so that proper user authentication, authorization and accounting can be carried out. Once the client has been authorized to access the services, it should provide necessary information for IPv6 tunneling and other services. The Tunnel Broker designates a Tunnel Server to be used as the actual tunnel end-point at the network side. After the above configuration steps have been carried out, the IPv6 over IPv4 tunnel between the client host/router and the selected Tunnel Server is up and working, thus allowing the tunnel broker user to get access to the 6bone or any other IPv6 network the Tunnel Server is connected to.
3. Applicable fields of industry and its effect This standard can be expected to be useful to stimulate the growth of IPv6 interconnected hosts and to allow early IPv6 network providers to provide easy access
±¹Á¦Ç¥ÁØ IETF RFC 3053
°ü·ÃÆÄÀÏ TTAE_IF-RFC3053.zip TTAE_IF-RFC3053.zip            

ÀÌÀü
±â¾÷ ½º¸¶Æ®¿öÅ©¿¡¼­ REST ±â¹ÝÀÇ Áö½ÄÇù¾÷À» À§ÇÑ ¼­ºñ½º ÀÎÅÍÆäÀ̽º
´ÙÀ½
±â¾÷ ½º¸¶Æ®¿öÅ©¿¡¼­ SOAP ±â¹ÝÀÇ ÅëÇÕ Ä¿¹Â´ÏÄÉÀ̼ÇÀ» À§ÇÑ ¼­ºñ½º ÀÎÅÍÆäÀ̽º