Re: [mpls] A question on draft-vkst-bfd-mpls-mib-01

Bala,

Sorry for the delayed response. Please see in-line.

Thanks,
Venkat.

On Thu, Apr 12, 2012 at 1:16 AM, Bala Subrahmanyam Venkata <
balavenkata@gmail.com> wrote:

> Hello-
>
> This is regarging the BFD MIB for MPLS-TP posted here:
>
> http://www.ietf.org/mail-archive/web/i-d-announce/current/msg42230.html
>
> I have a question about bfdMplsSessMode column proposed. It says
>
> bfdMplsSessMode  OBJECT-TYPE
>           SYNTAX      INTEGER {
>                         cc(1),
>                         cv(2)
>                       }
>           MAX-ACCESS  read-create
>           STATUS      current
>           DESCRIPTION
>             "This object specifies whether the BFD session is running
>              in Continuity Check(CC) or the Connectivity
>              Verification(CV) mode."
>           REFERENCE
>               "1.Proactive Connectivity Verification, Continuity Check
>                  and Remote Defect Indication for MPLS Transport
>                  Profile, draft-ietf-mpls-tp-cc-cv-rdi-06"
>           DEFVAL { cc }
>
>       ::= { bfdMplsSessEntry 2 }
>
>
> What about the cases where   the CC and CV messages are sent over the
> same session ? Is it expected that two entries exist in the
> bfdMplsSessTable - one for CC and another for CV ? I'm referring to
> the first line in section 3.2 of RFC 6428: "The combined CC, CV, and
> RDI functionality for MPLS-TP is achieved by multiplexing CC and CV
> PDUs within a single BFD session."
> [VM] bfdMplsSessMode can have the option cc-cv (3) for multiplexing CC &
> CV PDUs within a single BFD session

and we will add/modify the necessary MIB objects if required
> to accommodate this requirement completely.

> Btw, replace the 'draft' reference with 'RFC 6428' in the MIB.
> [VM] Thanks. We'll correct it in the next version.
>
> Thanks !
>
> /bala
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>