Re: [CCAMP] I-D Action: draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-09.txt

[Pontus Sköldström <[e-mail]>]

See inline, 

Cheers, 
Pontus 
--- snip --- 
> Just noticed, the draft says:
>    3.4.2.  MPLS OAM PM Delay sub-TLV
> 
>    The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub-
>    TLV of the "OAM Functions TLV".
> 
> Shouldn't it read:
>    TLV of the "Performance Monitoring sub-TLV"
> 
> and (in same section)
>    define, suggested value 1).
> should be
>    define, suggested value 2).

[Pontus] 
You're absolutely correct, fixed. 

--- snip --- 
> > We'd rather not specify exactly what happens when the threshold is
> > exceeded but leave that open (could be that nothing happens). And
> > since we're not talking about any particular thing in RFC6374 there's
> > no reference to it.
> 
> Perhaps the way to address is to make a general statement on this
> earlier in the section and removed both statements of:
> 
>    Configuration of triggered action(s) is out of scope for this
>    document but may include signaling an NMS, triggering protection
>    switching, etc.
> 
> Perhaps something at the start of 3.4 that says something like:
> 
> The Performance Monitoring sub-TLV provides the configuration
> information mentioned in Section 7 of [RFC6374]. It includes support
> for
> the configuration of quality thresholds and, as described in [RFC6374],
> "the crossing of which will trigger warnings or alarms, and result
> reporting and exception notification will be integrated into the
> system-wide network management and reporting framework."

[Pontus] 
Sure, that makes sense, fixed.