@techreport{patil-mext-mip6issueswithipsec-04,
    number =    {draft-patil-mext-mip6issueswithipsec-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-patil-mext-mip6issueswithipsec/04/},
    author =    {Basavaraj Patil and Charles E. Perkins and Hannes Tschofenig and Domagoj Premec},
    title =     {{Problems with the use of IPsec as the security protocol for Mobile IPv6}},
    pagetotal = 36,
    year =      2011,
    month =     oct,
    day =       10,
    abstract =  {Mobile IPv6 as specified in RFC3775 relies on IPsec for securing the signaling messages and user plane traffic between the mobile node and home agent. An IPsec SA between the mobile node and the home agent provides security for the mobility signaling. Use of IPsec for securing the data traffic between the mobile node and home agent is optional. This document analyses the implications of the design decision to mandate IPsec as the default security protocol for Mobile IPv6 and consequently Dual-stack Mobile IPv6 and recommends revisiting this decision in view of the experience gained from implementation and adoption in other standards bodies.},
}