Ȩ > ÀڷḶ´ç > ÀÚ·á°Ë»ö > Ç¥ÁØ
ÀÚ·á °Ë»ö°á°ú
Ç¥ÁØÁ¾·ù | Á¤º¸Åë½Å´ÜüǥÁØ(TTAS) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Ç¥ÁعøÈ£ | TTAE.IF-RFC5338 | ±¸ Ç¥ÁعøÈ£ | |||||||||||||||
Á¦°³Á¤ÀÏ | 2009-11-20 | ÃÑ ÆäÀÌÁö | 24 | ||||||||||||||
ÇÑ±Û Ç¥Áظí | È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝ°ú ±âÁ¸ ÀÀ¿ë°úÀÇ ¿¬µ¿ | ||||||||||||||||
¿µ¹® Ç¥Áظí | Using the Host Identity Protocol with Legacy Applications | ||||||||||||||||
ÇÑ±Û ³»¿ë¿ä¾à | º» Ç¥ÁØÀº ±âÁ¸ÀÇ ÀÀ¿ëµéÀÌ È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝ (HIP: Host Identity Protocol))°ú ¾î¶»°Ô µ¿ÀÛÇÒ ¼ö ÀÖ´Â °¡¸¦ ±â¼úÇϴ ǥÁØÀÌ´Ù. È£½ºÆ® ½Äº° ÇÁ·ÎÅäÄÝÀº ³×Æ®¿öÅ© ¿£ÅÍƼ¸¦ À§ÇÑ ¾ÏÈ£ÈµÈ ÁÖ¼Ò °ø°£À» Á¦°øÇÑ´Ù. ÀÀ¿ëÀÇ °üÁ¡¿¡¼ HIP ÇÁ·ÎÅäÄÝÀÌ Å¾ÀçµÈ ½Ã½ºÅÛÀº »õ·Î¿î ÁÖ¼Òü°è¸¦ Áö¿øÇØ¾ß ÇÏÁö¸¸, HIP ±â¹Ý ÀÀ¿ëÀÌ µµÀ﵃ ¶§±îÁö´Â »ó´çÇÑ ½ÃÀÏÀÌ ¼Ò¿äµÉ °ÍÀ¸·Î ¿¹»óµÈ´Ù. º» Ç¥ÁØÀº HIP ÇÁ·ÎÅäÄÝÀÌ Å¾ÀçµÈ ½Ã½ºÅÛ¿¡¼ HIPÀ» Áö¿øÇÏÁö ¾Ê´Â ÀÀ¿ë°ú ¿¬µ¿Çϱâ À§ÇÑ API ¹× ±¸Çö À̽´¸¦ ±â¼úÇÑ´Ù. | ||||||||||||||||
¿µ¹® ³»¿ë¿ä¾à | This standard defines overview of how legacy applications can be made to work with the Host Identity Protocol (HIP). HIP proposes to add a cryptographic name space for network stack names, but it is expected to take a long time to deploy the HIP protocol to the network. So, it is necessary to define the interaction between HIP-enabled systems and the applications that are not aware. | ||||||||||||||||
°ü·Ã IPR È®¾à¼ | Á¢¼öµÈ IPR È®¾à¼ ¾øÀ½ | ||||||||||||||||
°ü·ÃÆÄÀÏ | TTAE_IF-RFC5338.zip | ||||||||||||||||
Ç¥ÁØÀÌ·Â |
|
||||||||||||||||
Ç¥ÁØÀ¯Áöº¸¼öÀÌ·Â |
|