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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAE.IF-RFC7165 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2017-12-13 ÃÑÆäÀÌÁö 26
ÇѱÛÇ¥Áظí ÀÚ¹Ù ½ºÅ©¸³Æ® °´Ã¼ Ç¥±â¹ý(JSON) °´Ã¼ ¼­¸í ¹× ¾Ïȣȭ¸¦ À§ÇÑ ¿ä±¸»çÇ×
¿µ¹®Ç¥Áظí Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
Çѱ۳»¿ë¿ä¾à ´Ü °£ º¸¾ÈÀ» À§ÇØ, ¸¹Àº ÀÎÅÍ³Ý ÀÀ¿ëµéÀº ³×Æ®¿öÅ© °èÃþ ¶Ç´Â Àü¼Û °èÃþÀÇ º¸¾È ¸ÅÄ¿´ÏÁò ¿Ü¿¡ °´Ã¼±â¹ÝÀÇ º¸¾È ¸ÞÄ¿´ÏÁòÀ» ÇÊ¿ä·Î ÇÑ´Ù. °ú°Å¿¡´Â, ASN. 1¿¡ ±â¹ÝÇÑ ¹ÙÀ̳ʸ®ÀÇ ¾ÈÀüÇÑ °´Ã¼ ¾ç½ÄÀÎ ¾ÏÈ£ ¸Þ½ÃÁö ±Ô°ÝÀÌ Á¦°øµÇ¾ú´Ù. ½Ã°£ÀÌ Èê·¯, ÀÌ·¯ÇÑ Ç¥±â¹ýÀÇ »ç¿ëÀº Á¡ÁøÀûÀ¸·Î ¹®ÀÚ±â¹ÝÀÇ ÀÎÄÚµù ¹æ½ÄÀ¸·Î º¯È¯µÇ¾ú´Ù. ÀÌ·¯ÇÑ ¿¹°¡ ÀÚ¹Ù ½ºÅ©¸³Æ® °´Ã¼ Ç¥±â¹ý(JSON)ÀÌ´Ù. º» Ç¥ÁØÀº ÇöÀç °³¹ß ÁßÀÎ ´Ù¾çÇÑ ÀÀ¿ë º¸¾È ¸ÅÄ¿´ÏÁò¿¡ Àû¿ëµÈ JSON ÀÎÄÚµùÀ» ÀÌ¿ëÇÑ ¾ÈÀüÇÑ °´Ã¼ ¾ç½Ä¿¡ ´ëÇÑ ¿ä±¸»çÇ× ¹× »ç¿ë ½Ã³ª¸®¿À¸¦ Á¤ÀÇÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à For end-to-end security, many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. In the past, the Cryptographic Message Syntax has provided a binary secure object format based on ASN.1. Over time, the use of binary object encodings such as ASN.1 has been overtaken by text-based encodings, for example JavaScript Object Notation. The standard defines a set of use cases and requirements for a secure object format encoded using JavaScript Object Notation, drawn from a variety of application security mechanisms currently in development.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.IF-RFC7165.pdf TTAE.IF-RFC7165.pdf            

ÀÌÀü
Á¦·ÎÅÍÄ¡ ³×Æ®¿öÅ© ¹× ¼­ºñ½º °ü¸®(ZSM): ±³Â÷ µµ¸ÞÀÎ E2E ¼­ºñ½º ¶óÀÌÇÁ»çÀÌŬ °ü¸®
´ÙÀ½
Á¦·ÎÅÍÄ¡ ³×Æ®¿öÅ© ¹× ¼­ºñ½º °ü¸®(ZSM): Æó¼â ȸ·Î ÀÚµ¿È­ - Á¦2ºÎ: E2E ¼­ºñ½º ¹× ³×Æ®¿öÅ© °ü¸® À¯½ºÄÉÀ̽ºÀÇ ÀÚµ¿È­¸¦ À§ÇÑ ¼Ö·ç¼Ç