[mpls] 答复: draft-dai-mpls-tp-lock-instruct-00

[yang_jian at zte.com.cn]

Hi Sami，

Thanks for your concerns about our draft.

We have read your draft draft-boutros-mpls-tp-loopback-02.
In your draft, the Lock information is included in the Loopback
Message. But we think  Lock
should be an independent OAM tool and not alway accompany loopback. Because
there are some other applications using Lock, for example the out-of-service
performance monitor. It also can be initiated by management plane.
So we submitted a draft which only talks
about lock operation.


Jian

Sami Boutros <sboutros at cisco.com>

2009-11-09 08:33

收件人	dai.xuehui at zte.com.cn, wu.bo at zte.com.cn, yang_jian at zte.com.cn
抄送	"George Swallow" <swallow at cisco.com>, "Siva Sivabalan (msiva)" <msiva at cisco.com>, mpls at ietf.org
主题	draft-dai-mpls-tp-lock-instruct-00

Hi 
Xuehui, Bo, Jian,


The draft seems to cover what we already covered in http://tools.ietf.org/html/draft-boutros-mpls-tp-loopback-02

4.4.2. Lock

   The Lock operation is used to take an LSP out of service for mainte-
   nance.  The Lock operation is carried in an MPLS Loopback
request
   message sent from a MEP to a trail-end MEP of the LSP to request
that
   the LSP be taken out of service.  In response, the Lock operation
is
   carried in an Loopback response message sent from the trail-end
MEP
   back to the originating MEP to report the result.


4.4.3. Unlock

   The Unlock operation is used to restore a previously locked LSP
to
   service.  The Unlock operation is carried in an MPLS Loopback
request
   message sent from a MEP to a trail-end MEP of the LSP to request
that
   the LSP be restored to service.  In response, the Unlock operation
is
   carried in an Loopback Response message sent from the trail-end
MEP
   back to the originating MEP to report the result.

Thanks,

Sami