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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAE.IF-RFC5039 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2010-12-23 ÃÑÆäÀÌÁö 43
ÇѱÛÇ¥ÁØ¸í ¼¼¼Ç °³½Ã ÇÁ·ÎÅäÄÝ(SIP)°ú ½ºÆÔ
¿µ¹®Ç¥Áظí The Session Initiation Protocol (SIP) and Spam
Çѱ۳»¿ë¿ä¾à ½ºÆÔÀº ´ë¿ë·®ÀÇ ¿øÄ¡ ¾Ê´Â ¸Þ½ÃÁö Àü¼ÛÀ¸·Î Á¤ÀÇµÉ ¼ö ÀÖÀ¸¸ç, À̸ÞÀÏ ½ºÆÔÀº ¼­ºñ½º Á¦°ø¾÷ÀÚ ¹× ÀÌ¿ëÀÚ¿¡°Ô ÇÇÇظ¦ ¾ß±âÇØ ¿Ô´Ù. ±×·¯³ª ½ºÆÔÀº À̸ÞÀÏ¿¡¼­¸¸ ¹ß»ýÇÏ´Â °ÍÀÌ ¾Æ´Ï¸ç, ¸ðµç Á¾·ùÀÇ Åë½Å ½Ã½ºÅÛ»ó¿¡¼­ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. SIPÀº Åë½Å ÀÌ¿ëÀÚ °£¿¡ ¸ÖƼ¹Ìµð¾î Åë½ÅÀ» À§ÇÑ ½Ã½ºÅÛÀ» Á¤ÀÇÇÏ´Â ÇÁ·ÎÅäÄÝ·Î, À̸ÞÀÏ¿¡¼­¿Í °°ÀÌ SIP ȯ°æ¿¡¼­µµ ½ºÆÔÀÌ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. º» Ç¥ÁØ¿¡¼­´Â SIP ȯ°æ¿¡¼­ ¹ß»ýÇÏ´Â ½ºÆÔÀÇ ¹®Á¦Á¡À» ºÐ¼®ÇÑ´Ù. À̸¦ À§ÇÏ¿© ¸ÕÀú SIP ½ºÆÔÀÇ ¹®Á¦Á¡À» ÆľÇÇÏ°í, À̸ÞÀÏ ½ºÆÔ Â÷´ÜÀ» À§ÇÑ ´Ù¾çÇÑ ¼Ö·ç¼ÇÀÇ SIP ½ºÆÔ¿¡ÀÇ Àû¿ë¼º¿¡ ´ëÇÏ¿© °ËÅäÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à Spam, defined as the transmission of bulk unsolicited messages, has plagued Internet email. Unfortunately, spam is not limited to email. It can affect any system that enables user-to-user communications. The Session Initiation Protocol (SIP) defines a system for user-to-user multimedia communications. Therefore, it is susceptible to spam, just as email is. In this document, we analyze the problem of spam in SIP. We first identify the ways in which the problem is the same and the ways in which it is different from email. We then examine the various possible solutions that have been discussed for email and consider their applicability to SIP.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.IF-RFC5039_ed15.pdf TTAE.IF-RFC5039_ed15.pdf            

ÀÌÀü
½º¸¶Æ® ¸ð¹ÙÀÏ OK ¿ä±¸ »çÇ×
´ÙÀ½
±¹°¡ÃÖ»óÀ§µµ¸ÞÀÎ º¸¾È°­È­¸¦ À§ÇÑ DNS º¸¾È À§ÀÓ·¹ÄÚµå µî·Ï EPP(Extensible Provisioning Protocol)