Ȩ > Ç¥ÁØÈ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ
| Ç¥ÁعøÈ£ | TTAE.IF-RFC9326 | ±¸Ç¥ÁعøÈ£ | |
|---|---|---|---|
| Á¦°³Á¤ÀÏ | 2025-12-05 | ÃÑÆäÀÌÁö | 23 |
| ÇѱÛÇ¥Áظí | ½Ç »óȲ ¿î¿ë, °ü¸® ¹× À¯Áöº¸¼ö(IOAM) Á÷Á¢ º¸°í | ||
| ¿µ¹®Ç¥Áظí | In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting | ||
| Çѱ۳»¿ë¿ä¾à | IOAM [RFC9197]Àº ³×Æ®¿öÅ© Æ®·¡ÇÈÀ» ¸ð´ÏÅ͸µÇϰí, IOAM-µ¥ÀÌÅÍ-Çʵ带 ³×Æ®¿öÅ©¸¦ Åë°úÇÏ´Â µ¥ÀÌÅÍ ÆÐŶ(in-flight data packets)¿¡ »ðÀÔÇϴµ¥ »ç¿ëµÈ´Ù.
IOAM ±â¼úÀº »çÀü-ÇÒ´ç ÃßÀû, ÁõºÐ ÃßÀû, Àü¼Û Áõ¸í, ±×¸®°í ¿§Áö-Åõ-¿§Áö·Î Á¤ÀÇµÈ ³× °¡Áö °¡´ÉÇÑ IOAM-¿É¼Ç-ŸÀÔÀ» »ç¿ëÇÑ´Ù. ÀÌ ¹®¼´Â "IOAM Á÷Á¢ º¸°í(Direct Export, DEX)-¿É¼Ç-ŸÀÔ"À̶ó´Â »õ·Î¿î IOAM-¿É¼Ç-ŸÀÔÀ» Á¤ÀÇÇÑ´Ù. ÀÌ ¿É¼Ç ŸÀÔÀº IOAM ³ëµå°¡ µ¥ÀÌÅ͸¦ ·ÎÄÿ¡¼ Áý°è ¹× ó¸®Çϰųª, ƯÁ¤ ¼ö½Å ¿£ÅÍÆ¼(Receiving Entity)·Î ³»º¸³¾ ¼ö ÀÖµµ·Ï ±¸µ¿ÇÏ´Â ¿ªÇÒÀ» ÇÑ´Ù. ¹®¼¿¡¼´Â ÀÌ·¯ÇÑ ±â´ÉÀ» "¼öÁý(Collection)" ¹×/¶Ç´Â "º¸°í(Exporting)"¶ó ÇÑ´Ù. ÀÌ ¹®¼¿¡¼ ¼ö½Å ¿£ÅÍÆ¼¶õ IOAM-µµ¸ÞÀÎ ³»ÀÇ ¼öÁý±â, ºÐ¼®±â, ÄÁÆ®·Ñ·¯, µðĸ½¶È ³ëµå ¹× ³ëµå ³» ¼ÒÇÁÆ®¿þ¾î ¸ðµâÀÌ µÉ ¼ö ÀÖ´Ù. 1Àý¿¡¼´Â ¼·ÐÀ» ¼³¸íÇϰí, 2Àý¿¡¼ ±ÔÄ¢À» Á¤ÀÇÇÑ´Ù. 3Àý¿¡´Â IOAM Á÷Á¢ º¸°í-¿É¼Ç-ŸÀÔÀ» ¼³¸íÇϰí, 4Àý¿¡¼ IANA °í·Á»çÇ×, 5Àý¿¡¼ ¼º´É °í·Á»çÇ×À» ¼³¸íÇϰí, 6Àý¿¡¼ º¸¾È °í·Á»çÇ×, 7Àý¿¡¼´Â Âü°í¹®ÇåÀ» ±âÀçÇÑ´Ù. ºñ·Ï IOAM-¿É¼Ç-ŸÀÔÀÌ Á÷Á¢ º¸°í¶ó°í ÇÏÁö¸¸, ÀÌ ¿É¼Ç ŸÀÔÀÌ Æ÷ÇÔµÈ ÆÐŶÀ» ¼ö½ÅÇßÀ» ¶§, ½ÇÁ¦·Î ¶Ç ´Ù¸¥ ÆÐŶÀÌ »ý¼ºµÇ´ÂÁö´Â ¹èÆ÷ ȯ°æ¿¡ µû¶ó ´Ù¸£´Ù. ÀϺΠ¹èÆ÷ ȯ°æ¿¡¼´Â Á÷Á¢ º¸°í ¿É¼Ç ŸÀÔÀÌ Æ÷ÇÔµÈ ÆÐŶÀ» ´Ü¼øÈ÷ OAM µ¥ÀÌÅÍÀÇ ·ÎÄà 󸮸¦ ±¸µ¿ÇÏ´Â ¿ëµµ·Î¸¸ »ç¿ëÇÒ ¼öµµ ÀÖ´Ù. ÀÌ·¯ÇÑ ·ÎÄà ó¸® ±â´ÉÀÇ ±¸Ã¼ÀûÀÎ µ¿ÀÛ ¹æ½ÄÀº º» ¹®¼ÀÇ ¹üÀ§¿¡ Æ÷ÇÔÇÏÁö ¾Ê´Â´Ù. |
||
| ¿µ¹®³»¿ë¿ä¾à | In-situ Operations, Administration, and Maintenance (IOAM) [RFC9197] is used to monitor network traffic and to insert IOAM-Data-Fields into in-flight data packets traversing the network.
IOAM employs four possible IOAM-Option-Types: Pre-allocated Trace, Incremental Trace, Proof of Transit, and Edge-to-Edge. This document defines a new IOAM-Option-Type, the "IOAM Direct Export (DEX) Option-Type". This option type triggers IOAM nodes to locally aggregate and process data, or to export it to a specific Receiving Entity. In this document, these functions are referred to as "Collection" and/or "Exporting". A Receiving Entity may refer to a collector, analyzer, controller, decapsulating node, or a software module within an IOAM node, inside the IOAM domain. Section 1 provides an introduction. Section 2 defines conventions used. Section 3 describes the IOAM Direct Export Option-Type. Section 4 specifies IANA considerations. Section 5 discusses performance considerations. Section 6 addresses security considerations. Section 7 provides references. Although the IOAM Direct Export Option-Type is termed ¡°Direct Export¡±, whether a new packet is actually generated upon reception of a packet carrying this option type depends on the specific deployment. In some deployments, the Direct Export Option-Type may simply trigger local processing of the IOAM data, without generating any additional packets. The specific behavior of such local processing is outside the scope of this document. |
||
| ±¹Á¦Ç¥ÁØ | |||
| °ü·ÃÆÄÀÏ |
| ||





