%% You should probably cite rfc6245 instead of this I-D. @techreport{ietf-mip4-gre-key-extension-05, number = {draft-ietf-mip4-gre-key-extension-05}, 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-mip4-gre-key-extension/05/}, author = {Jay Navali and Kent Leung and Avi Lior and Parviz Yegani and Kuntal Chowdhury}, title = {{Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4}}, pagetotal = 8, year = 2011, month = mar, day = 28, abstract = {The Generic Routing Encapsulation (GRE) specification contains a Key field, which MAY contain a value that is used to identify a particular GRE data stream. This specification defines a new Mobile IP extension that is used to exchange the value to be used in the GRE Key field. This extension further allows the Mobility Agents to set up the necessary protocol interfaces prior to receiving the mobile node traffic. The new extension allows a Foreign Agent to request GRE tunneling without disturbing the Home Agent behavior specified for Mobile IPv4. GRE tunneling with the Key field allows the operators to have home networks that consist of multiple Virtual Private Networks (VPNs), which may have overlapping home addresses. When the tuple \textless{}Care of Address, Home Address, and Home Agent Address\textgreater{} is the same across multiple subscriber sessions, GRE tunneling will provide a means for the Foreign Agent and Home Agent to identify data streams for the individual sessions based on the GRE key. In the absence of this key identifier, the data streams cannot be distinguished from each other -- a significant drawback when using IP-in-IP tunneling. {[}STANDARDS-TRACK{]}}, }