ÀÚ·á°Ë»ö-Ç¥ÁØ

Ȩ > ÀڷḶ´ç > ÀÚ·á°Ë»ö > Ç¥ÁØ

ÀÚ·á °Ë»ö°á°ú

°Ë»öÆäÀÌÁö·Î
Ç¥ÁØÁ¾·ù Á¤º¸Åë½Å´ÜüǥÁØ(TTAS)
Ç¥ÁعøÈ£ TTAE.IF-RFC5201 ±¸ Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2009-11-20 ÃÑ ÆäÀÌÁö 121
ÇÑ±Û Ç¥Áظí È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝ
¿µ¹® Ç¥Áظí Host Identity Protocol
ÇÑ±Û ³»¿ë¿ä¾à È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝ(HIP)Àº °øÀ¯ÇÏ´Â IP °èÃþÀÇ »óŸ¦ ¾ÈÀüÇÏ°Ô ¼ö¸³Çϰí À¯ÁöÇϱâ À§ÇÏ¿©, ½Äº°ÀÚ¿Í À§Ä¡ÀÚ¸¦ ºÐ¸®ÇÑ´Ù. Áï IP ÁÖ¼Ò°¡ º¯µ¿µÇ´Â °æ¿ì¿¡µµ Åë½ÅÀÇ ¿¬¼Ó¼ºÀ» °¡´ÉÇÏ°Ô ÇÑ´Ù. °á°úÀûÀ¸·Î DoS(denial-of-service)¿Í MitM (man-in-the middle) °ø°Ý¿¡ ´ëÀÀÇÏ´Â È¿°ú°¡ ÀÖ´Ù.
¿µ¹® ³»¿ë¿ä¾à This memo specifies the details of the Host Identity Protocol (HIP).
HIP allows consenting hosts to securely establish and maintain shared
IP-layer state, allowing separation of the identifier and locator
roles of IP addresses, thereby enabling continuity of communications
across IP address changes. HIP is based on a Sigma-compliant Diffie-
Hellman key exchange, using public key identifiers from a new Host
Identity namespace for mutual peer authentication. The protocol is
designed to be resistant to denial-of-service (DoS) and man-in-the-
middle (MitM) attacks. When used together with another suitable
security protocol, such as the Encapsulated Security Payload (ESP),
it provides integrity protection and optional encryption for upper-
layer protocols, such as TCP and UDP.
°ü·Ã IPR È®¾à¼­ Á¢¼öµÈ IPR È®¾à¼­ ¾øÀ½
°ü·ÃÆÄÀÏ    TTAE_IF-RFC5201.zip TTAE_IF-RFC5201.zip
Ç¥ÁØÀÌ·Â
Ç¥Áظí Ç¥ÁعøÈ£ Á¦°³Á¤ÀÏ ±¸ºÐ À¯È¿
¿©ºÎ
IPR
È®¾à¼­
ÆÄÀÏ
È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝ TTAE.IF-RFC5201 2009-11-20 Á¦Á¤ À¯È¿ ¾øÀ½ TTAE_IF-RFC5201.zip
Ç¥ÁØÀ¯Áöº¸¼öÀÌ·Â
°ËÅäÀÏÀÚ °ËÅä°á°ú °ËÅä³»¿ë
2018-05-31 À¯Áö ±¹³» ³×Æ®¿öÅ© Àåºñ °ü·Ã »ê¾÷¿¡ ±âȰ¿ë ȤÀº Ȱ¿ë ¿¹Á¤