Subject: RE: error handling in l2vpn

From: Narasimha Swamy <[email-masked]>
Date: Wed, 21 Nov 2001 16:00:34 +0530

> Narasimha Swamy wrote:
> > 
> > Hi,
> > In case of L2VPN sessions configuration, it is possible for an edge LSR
> to
> > receive unmatched MTU or vc-type from other edge LSR for a particular
> l2vpn
> > session.
> 
> By L2VPN here do you mean draft-martini?
      yes, i mean draft-martini.

> If so then yes - it is possible for the edge LSR to receive unmatched
> MTU or vc-type from the peer edge LSR.
> 
> > What type of message should be sent in this case to indicate this error.
> If
> > notification message is sent, what will be the Status Code.
> 
> A label release should be sent.  I'm not sure what the status code
> should be.  Luca can probably tell us...
> 
       if label release is the one to be sent, i don't think status code
required, as status code is meaningful only in the context of notification
messages. But according to the section 3.5.1.1.1 of rfc3036,  it seems to be
label release is meant for different scenarios than this l2vpn one. May be
it is meaningful to send notification message using Extended Status to
indicate the mismatch problem.

> Giles
> 
> > regards
> > swamy.
> 
> -- 
> =================================================================
> Giles Heron    Principal Network Architect    PacketExchange Ltd.
> ph: +44 7880 506185              "if you build it they will yawn"
> =================================================================
>