%% You should probably cite draft-ietf-6lo-prefix-registration-18 instead of this revision.
@techreport{ietf-6lo-prefix-registration-13,
    number =    {draft-ietf-6lo-prefix-registration-13},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-6lo-prefix-registration/13/},
    author =    {Pascal Thubert},
    title =     {{IPv6 Neighbor Discovery Prefix Registration}},
    pagetotal = 27,
    year =      2025,
    month =     jun,
    day =       6,
    abstract =  {This document updates Subnet Neighbor Discovery (RFC 8505, RFC 8928) to enable a node that owns or is directly connected to a prefix to register that prefix to neighbor routers. The registration indicates that the registered prefix can be reached via the advertising node without a loop. The unicast prefix registration allows the node to request neighbor router(s) to redistribute the prefix in another routing domain regardless of the routing protocol used in that domain. This document extends Routing Protocol for Low-Power and Lossy Networks (RPL) (RFC 6550, RFC 9010) to enable a 6LoWPAN Router (6LR) to inject the registered prefix in RPL.},
}