Chinaunix首页 | 论坛 | 博客
  • 博客访问: 83187
  • 博文数量: 18
  • 博客积分: 735
  • 博客等级: 军士长
  • 技术积分: 205
  • 用 户 组: 普通用户
  • 注册时间: 2005-09-04 14:10
文章分类

全部博文(18)

文章存档

2008年(2)

2007年(12)

2005年(4)

我的朋友

分类: 系统运维

2007-09-26 00:15:18

3. LSP Tunnel related Message Formats
   //LSP隧道相关消息格式
  
   Five new objects are defined in this section:

      Object name          Applicable RSVP messages
      ---------------      ------------------------
      LABEL_REQUEST          Path
      LABEL                  Resv
      EXPLICIT_ROUTE         Path
      RECORD_ROUTE           Path, Resv
      SESSION_ATTRIBUTE      Path

   New C-Types are also assigned for the SESSION, SENDER_TEMPLATE, and
   FILTER_SPEC, objects.

   Detailed descriptions of the new objects are given in later sections.
   All new objects are OPTIONAL with respect to RSVP.  An implementation
   can choose to support a subset of objects.  However, the
   LABEL_REQUEST and LABEL objects are mandatory with respect to this
   specification.
   //对以上新对象的描述,将在后续章节中给出。这些新对象对RSVP都是可选的。
   //一个实现可以选择支持这些对象的子集。此外,LABEL_REQUEST和LABEL对象
   //对本文档(或RSVP-TE)而言是必须支持的。

   The LABEL and RECORD_ROUTE objects, are sender specific.  In Resv
   messages they MUST appear after the associated FILTER_SPEC and prior
   to any subsequent FILTER_SPEC.
   //LABEL和RRO对象,与sender有关。它们必须出现在相关的FILTER_SPEC对象后
   //且在其他FILTER_SPEC对象之前,当然,是在RESV消息中。

   The relative placement of EXPLICIT_ROUTE, LABEL_REQUEST, and
   SESSION_ATTRIBUTE objects is simply a recommendation.  The ordering
   of these objects is not important, so an implementation MUST be
   prepared to accept objects in any order.
   //ERO,LABEL_REQUEST和SESSION_ATTRIBUTE的位置只是一个建议。这些对象的
   //顺序不重要,因此一个实现必须准备好以任何顺序接收这些对象。

3.1. Path Message
  
   The format of the Path message is as follows:
   //PATH消息的格式如下:
  
      ::=       [ ]
                              
                              
                               [ ]
                              
                               [ ]

 

Awduche, et al.             Standards Track                    [Page 15]

RFC 3209           Extensions to RSVP for LSP Tunnels      December 2001


                               [ ... ]
                              

      ::= 
                               [ ]
                               [ ]

3.2. Resv Message

   The format of the Resv message is as follows:

      ::=       [ ]
                                
                              
                               [ ]  [ ]
                               [ ... ]