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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ 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.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE_IF-RFC5201.zip TTAE_IF-RFC5201.zip            

ÀÌÀü
DTN ±¸Á¶
´ÙÀ½
MSRP¸¦ À§ÇÑ ¸±·¹ÀÌ È®Àå