%% You should probably cite draft-ietf-trill-pseudonode-nickname instead of this I-D.
@techreport{hu-trill-pseudonode-nickname-02,
    number =    {draft-hu-trill-pseudonode-nickname-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-hu-trill-pseudonode-nickname/02/},
    author =    {Hongjun Zhai and fangwei hu and Radia Perlman and Donald E. Eastlake 3rd},
    title =     {{RBridge: Pseudo-Nickname}},
    pagetotal = 12,
    year =      2012,
    month =     may,
    day =       15,
    abstract =  {At the edg of TRILL campus, some RBridges provide end-station services to their attached end stations, these RBridges are called edge RBridges. To avoid potential frame duplication or loops in TRILL campus, only one edge RBridge is permitted to provide end- station services in a VLAN x at all times for its attached end stations. However, in some application scenarios, for example in Link Aggregation Group (LAG), more than one edge RBridge is required to provide end-station services to an end stations even in a VLAN, which causes the flip-flopping of the egress RBridge nickname for such an end node in remote RBridges' forwarding tables if nothing to do. In this document, the concept of Virtual RBridge, along with its pseudo-nickname, is introduced to fix the above problem.},
}