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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAE.IF-RFC9256 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2023-12-06 ÃÑÆäÀÌÁö 43
ÇѱÛÇ¥ÁØ¸í ¼¼±×¸ÕÆ® ¶ó¿ìÆà Á¤Ã¥ ±¸Á¶
¿µ¹®Ç¥Áظí Segment Routing Policy Architecture
Çѱ۳»¿ë¿ä¾à ÀÌ Ç¥ÁØÀº ƯÁ¤ ¸ñÀû(¿¹¸¦ µé¾î, ¼­ºñ½º ¼öÁØ Çù¾à(SLA))¿¡ µû¶ó Æ®·¡ÇÈÀ» Á¶Á¤Çϱâ À§ÇÑ SR Á¤Ã¥À» ³ëµå¿¡ ±¸ÇöÇϱâ À§ÇÑ ÇÁ·¹ÀÓ¿öÅ©¸¦ Á¦°øÇÑ´Ù. ÀÌ ÇÁ·¹ÀÓ¿öÅ©´Â Á¤·ÄµÈ ¼¼±×¸ÕÆ® ¸®½ºÆ®(Áï, Áö½Ã»çÇ×)¸¦ ÀνºÅϽºÈ­ÇÏ¿© SR Á¤Ã¥À» ±¸ÇöÇÑ´Ù. ¿©±â¿¡´Â SR Á¤Ã¥ÀÇ ÇÙ½ÉÀûÀÎ Ãø¸é°ú ±¸¼º¿ä¼ÒÀÎ SR Á¤Ã¥ÀÇ ½Äº°, À¯È¿¼º, ¿ì¼±¼øÀ§, Æ÷¿öµù Æò¸éÀÇ ¼¼±×¸ÕÆ® ¶ó¿ìÆà Á¤Ã¥ ÀνºÅϽºÈ­, Èĺ¸ °æ·Î ¹× ¼¼±×¸ÕÆ® ¸®½ºÆ®, Èĺ¸ °æ·ÎÀÇ ÇÁ·ÎÅäÄÝ ±â¿ø, »ý¼ºÀÚ, ÆǺ°ÀÚ, ½Äº°, ¼±È£µµ, À¯È¿¼º, È°¼º Èĺ¸ °æ·Î µîÀÌ Æ÷ÇԵȴÙ. ¼¼±×¸ÕÆ® ¶ó¿ìÆà ±¸Á¶(RFC 8402)´Â ¸ðµç ¸í·ÉÀ» ¼¼±×¸ÕÆ®¿¡ ¹ÙÀεùÇÒ ¼ö ÀÖµµ·Ï ¸í½ÃÇϸç, µû¶ó¼­ ¼¼±×¸ÕÆ® ¶ó¿ìÆà Á¤Ã¥Àº ÅäÆú·ÎÁö ¶Ç´Â ¼­ºñ½º ¸í·É°ú °ü·ÃµÈ ¸ðµç À¯ÇüÀÇ SID¸¦ »ç¿ëÇÒ ¼ö ÀÖ½À´Ï´Ù.
¿µ¹®³»¿ë¿ä¾à The standard provides a framework that enables the instantiation of an ordered list of segments on a node for implementing a source routing policy for the steering of traffic for a specific purpose(e.g., for a specific Service Level Agreement(SLA)) from that node. It includes the key aspects and constituents of an SR Policy: Identification of an SR Policy, Candidate Path and Segment List, Protocol-Origin of a Candidate Path, Originator of a Candidate Path, Discriminator of a Candidate Path, Identification of a Candidate Path, Preference of a Candidate Path, Validity of a Candidate Path, Active Candidate Path, Validity of an SR Policy, Instantiation of an SR Policy in the Forwarding Plane, Priority of an SR Policy. The Segment Routing architecture(RFC 8402) specifies that any instruction can be bound to a segment. Thus, an SR Policy can be built using any type of Segment Identifier(SID) including those associated with topological or service instructions.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.IF-RFC9256.pdf TTAE.IF-RFC9256.pdf            

ÀÌÀü
Áö´ÉÇü Ȩ³×Æ®¿öÅ© ±â±â°£ »óÈ£¿î¿ë¼ºÀ» À§ÇÑ ¿ä±¸»çÇ×
´ÙÀ½
Ȩ³×Æ®¿öÅ© ¼¼´ë°£ ³×Æ®¿öÅ© ºÐ¸® ¼³Ä¡¹æ¹ý