@techreport{li-opsawg-oam-interval-mod-00,
    number =    {draft-li-opsawg-oam-interval-mod-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-opsawg-oam-interval-mod/00/},
    author =    {Zhiqiang Li and Zongpeng Du and Junjie Wang and Wei Cheng and Guoying Zhang and Xun Sun and Chunhao Zhao},
    title =     {{Coordinated CCM Interval Modification Procedures}},
    pagetotal = 8,
    year =      2026,
    month =     jul,
    day =       4,
    abstract =  {In IEEE 802.1ag Connectivity Fault Management (CFM), the Continuity Check Message (CCM) interval is a static parameter that must match on both peer Maintenance End Points (MEPs). Changing the interval at runtime on one MEP without simultaneously updating the peer causes a Loss of Continuity (LOC) defect and may trigger protection switching. Because the CFM PDU formats and OpCode space are governed by IEEE 802.1, this document does not modify the protocol; instead, it specifies a coordinated management-plane procedure that transitions both MEPs to a new CCM interval without raising spurious defects or triggering protection switching, together with failure handling and rollback behavior. The procedure can be operated through existing configuration models such as the connection-oriented OAM YANG model.},
}