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

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

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

°Ë»öÆäÀÌÁö·Î
Ç¥ÁØÁ¾·ù Á¤º¸Åë½Å´ÜüǥÁØ(TTAS)
Ç¥ÁعøÈ£ TTAE.OT-08.0001 ±¸ Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2025-12-05 ÃÑ ÆäÀÌÁö 18
ÇÑ±Û Ç¥Áظí Àß ¾Ë·ÁÁø ºÐ»ê ½Äº°ÀÚ(DID) ¼³Á¤
¿µ¹® Ç¥Áظí Well Known DID Configuration
ÇÑ±Û ³»¿ë¿ä¾à ÀÌ Ç¥ÁØÀº ÀÎÅÍ³Ý µµ¸ÞÀΰú ºÐ»ê ½Äº°ÀÚ(DID) °£ÀÇ ¿¬°è¸¦ Áõ¸íÇϱâ À§ÇÑ ±¸Á¶¿Í ÀýÂ÷¸¦ Á¤ÀÇÇÑ´Ù. Áï, ƯÁ¤ ÀÎÅÍ³Ý µµ¸ÞÀΰú DID°¡ µ¿ÀÏÇÑ ÁÖü(subject)¿¡ ¼ÓÇÔÀ» Áõ¸íÇÏ´Â ¹æ¹ýÀ» ±â¼úÇÑ´Ù.
µµ¸ÞÀÎ ¼ÒÀ¯ÀÚ´Â À¥ »çÀÌÆ®ÀÇ .well-known/did-configuration °æ·Î¿¡ JSON Çü½ÄÀÇ ±¸¼º ÆÄÀÏÀ» ¹èÄ¡Çϰí, ÀÌ ÆÄÀÏ¿¡ µµ¸ÞÀΰú DID ¿¬°á Á¤º¸¸¦ ´ãÀº Çϳª ÀÌ»óÀÇ µµ¸ÞÀÎ ¿¬°è ÁÖÀå(Domain Linkage Assertion)À» Æ÷ÇÔÇÑ´Ù. ÀÌ ÁÖÀå(Assertion)Àº ƯÁ¤ ÀÎÅÍ³Ý µµ¸ÞÀΰú DID°¡ µ¿ÀÏÇÑ ¼ÒÀ¯ÀÚ¿¡ ÀÇÇØ °ü¸®µÇ°í ÀÖÀ½À» ¾ÏÈ£ÇÐÀûÀ¸·Î ¼±¾ðÇÏ´Â Á¤º¸ÀÌ´Ù.

°¢ µµ¸ÞÀÎ ¿¬°è ÁÖÀåÀº DID¿Í ÇØ´ç DIDÀÇ Å°·Î ¼­¸íµÈ JWT(JSON Web Token) ÇüÅ·ΠǥÇöµÇ¸ç, JWT´Â µµ¸ÞÀÎ À̸§, ¹ß±ÞÀÚÀÇ DID, ¸¸·á ½Ã°£ µîÀÇ Á¤º¸°¡ Æ÷ÇԵȴÙ. À̸¦ ÅëÇØ DID ÄÁÆ®·Ñ·¯°¡ µµ¸ÞÀÎÀÇ ¼ÒÀ¯ÀÚÀÓÀ», µµ¸ÞÀÎ ¼ÒÀ¯ÀÚ°¡ DIDÀÇ °ü¸® ÁÖüÀÎ ÄÁÆ®·Ñ·¯ÀÓÀ» »óÈ£ Áõ¸íÇÒ ¼ö ÀÖ´Ù.

°ËÁõ °úÁ¤¿¡¼­ ¼­ºñ½º Á¦°øÀÚ´Â HTTPS¸¦ ÅëÇØ ÇØ´ç ¸®¼Ò½º¸¦ °¡Á®¿Í JSON ÆÄ½Ì, JWT ¼­¸í °ËÁõ, DID ¹®¼­ Á¶È¸ ¹× Ű È®ÀÎ µîÀÇ ÀýÂ÷¸¦ ¼öÇàÇÏ¿© ÁÖÀå(Assertion)ÀÇ ÁøÀ§¸¦ ÆÇº°ÇÑ´Ù. °¢ ÁÖÀåÀº µ¶¸³ÀûÀ¸·Î °ËÁõµÇ¸ç, ÇϳªÀÇ ÁÖÀåÀÌ À¯È¿ÇÏÁö ¾Ê´õ¶óµµ ´Ù¸¥ ÁÖÀå¿¡´Â ¿µÇâÀ» ÁÖÁö ¾Ê´Â´Ù.

ÀÌ Ç¥ÁØÀº IETFÀÇ RFC 8615¿¡¼­ Á¤ÀÇµÈ .well-known °æ·Î ±¸Á¶¸¦ µû¸£¸ç, JWT´Â RFC 7797¿¡ Á¤ÀÇµÈ ¼­¸í ¹æ½ÄÀ» µû¸¥´Ù. À̸¦ ÅëÇØ À¥ ½Ã½ºÅÛÀº DID¸¦ ½Å·Ú ±â¹ÝÀ¸·Î ÅëÇÕÇÒ ¼ö ÀÖ°í, DID ±â¹ÝÀÇ ½Å¿ø ¹× ±ÇÇÑ °ËÁõ ¸ÞÄ¿´ÏÁò°ú ±âÁ¸ À¥ ÀÎÇÁ¶ó °£ÀÇ »óÈ£¿î¿ë¼ºÀ» È®º¸ÇÒ ¼ö ÀÖ´Ù.
¿µ¹® ³»¿ë¿ä¾à The standard defines a method to prove that a web domain and a Decentralized Identifier (DID) belong to the same subject. A domain owner places a JSON configuration file at the .well-known/did-configuration path, containing one or more Domain Linkage Assertions—cryptographically signed statements that a specific domain and DID are controlled by the same entity. Each assertion is a JSON Web Token (JWT) signed with the DID¡¯s key, including details such as the domain name, issuer¡¯s DID, and expiration time.

Verification involves retrieving the file over HTTPS, parsing the JSON, verifying the JWT signature, resolving the DID document, and validating the keys. Each assertion is verified independently, so an invalid assertion does not affect the validity of others.

The standard follows the .well-known path format defined in IETF RFC 8615 and the JWT signature rules in RFC 7797, enabling trust-based integration of DIDs with web systems and ensuring interoperability between DID-based identity and authorization mechanisms and existing web infrastructure.
°ü·Ã IPR È®¾à¼­ Á¢¼öµÈ IPR È®¾à¼­ ¾øÀ½
°ü·ÃÆÄÀÏ    TTAE.OT-08.0001.pdf TTAE.OT-08.0001.pdf
Ç¥ÁØÀÌ·Â
Ç¥Áظí Ç¥ÁعøÈ£ Á¦°³Á¤ÀÏ ±¸ºÐ À¯È¿
¿©ºÎ
IPR
È®¾à¼­
ÆÄÀÏ
Àß ¾Ë·ÁÁø ºÐ»ê ½Äº°ÀÚ(DID) ¼³Á¤ TTAE.OT-08.0001 2025-12-05 Á¦Á¤ À¯È¿ ¾øÀ½ TTAE.OT-08.0001.pdf