%% You should probably cite draft-ietf-mpls-oam-ipv6-rao instead of this I-D.
@techreport{raza-mpls-oam-ipv6-rao-02,
    number =    {draft-raza-mpls-oam-ipv6-rao-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-raza-mpls-oam-ipv6-rao/02/},
    author =    {Syed Kamran Raza and Nobo Akiya and Carlos Pignataro},
    title =     {{IPv6 Router Alert Option for MPLS OAM}},
    pagetotal = 5,
    year =      2014,
    month =     sep,
    day =       30,
    abstract =  {RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the Router Alert option must be set in the IP header of the MPLS Echo Request messages, and may conditionally be set in the IP header of the MPLS Echo Reply messages. While a generic "Router shall examine packet" Option Value is used for the IPv4 Router Alert Option (RAO), there is no generic Router Alert Option Value defined for IPv6 that can be used. This document allocates a new generic IPv6 Router Alert Option Value that can be used by MPLS OAM tools, including the MPLS Echo Request and MPLS Echo Reply messages for MPLS IPv6. The initial motivation to request an IPv6 Router Alert Option (RAO) code point for MPLS OAM comes from MPLS LSP Ping/Traceroute. However, this codepoint is applicable to all MPLS OAM and not limited to MPLS LSP Ping/Traceroute.},
}