draft-ietf-ipwave-vehicular-networking-17.txt | draft-ietf-ipwave-vehicular-networking-18.txt | |||
---|---|---|---|---|
IPWAVE Working Group J. Jeong, Ed. | IPWAVE Working Group J. Jeong, Ed. | |||
Internet-Draft Sungkyunkwan University | Internet-Draft Sungkyunkwan University | |||
Intended status: Informational July 28, 2020 | Intended status: Informational July 29, 2020 | |||
Expires: January 29, 2021 | Expires: January 30, 2021 | |||
IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem | IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem | |||
Statement and Use Cases | Statement and Use Cases | |||
draft-ietf-ipwave-vehicular-networking-17 | draft-ietf-ipwave-vehicular-networking-18 | |||
Abstract | Abstract | |||
This document discusses the problem statement and use cases of | This document discusses the problem statement and use cases of | |||
IPv6-based vehicular networking for Intelligent Transportation | IPv6-based vehicular networking for Intelligent Transportation | |||
Systems (ITS). The main scenarios of vehicular communications are | Systems (ITS). The main scenarios of vehicular communications are | |||
vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and | vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and | |||
vehicle-to-everything (V2X) communications. First, this document | vehicle-to-everything (V2X) communications. First, this document | |||
explains use cases using V2V, V2I, and V2X networking. Next, for | explains use cases using V2V, V2I, and V2X networking. Next, for | |||
IPv6-based vehicular networks, it makes a gap analysis of current | IPv6-based vehicular networks, it makes a gap analysis of current | |||
skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on January 29, 2021. | This Internet-Draft will expire on January 30, 2021. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 2, line 31 ¶ | skipping to change at page 2, line 31 ¶ | |||
4.1. Vehicular Network Architecture . . . . . . . . . . . . . 13 | 4.1. Vehicular Network Architecture . . . . . . . . . . . . . 13 | |||
4.2. V2I-based Internetworking . . . . . . . . . . . . . . . . 17 | 4.2. V2I-based Internetworking . . . . . . . . . . . . . . . . 17 | |||
4.3. V2V-based Internetworking . . . . . . . . . . . . . . . . 19 | 4.3. V2V-based Internetworking . . . . . . . . . . . . . . . . 19 | |||
5. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 21 | 5. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 21 | |||
5.1. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 22 | 5.1. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 22 | |||
5.1.1. Link Model . . . . . . . . . . . . . . . . . . . . . 23 | 5.1.1. Link Model . . . . . . . . . . . . . . . . . . . . . 23 | |||
5.1.2. MAC Address Pseudonym . . . . . . . . . . . . . . . . 25 | 5.1.2. MAC Address Pseudonym . . . . . . . . . . . . . . . . 25 | |||
5.1.3. Routing . . . . . . . . . . . . . . . . . . . . . . . 26 | 5.1.3. Routing . . . . . . . . . . . . . . . . . . . . . . . 26 | |||
5.2. Mobility Management . . . . . . . . . . . . . . . . . . . 26 | 5.2. Mobility Management . . . . . . . . . . . . . . . . . . . 26 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 | |||
7. Informative References . . . . . . . . . . . . . . . . . . . 30 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 | |||
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 38 | 8. Informative References . . . . . . . . . . . . . . . . . . . 30 | |||
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 38 | Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 40 | Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 37 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 39 | ||||
1. Introduction | 1. Introduction | |||
Vehicular networking studies have mainly focused on improving safety | Vehicular networking studies have mainly focused on improving safety | |||
and efficiency, and also enabling entertainment in vehicular | and efficiency, and also enabling entertainment in vehicular | |||
networks. The Federal Communications Commission (FCC) in the US | networks. The Federal Communications Commission (FCC) in the US | |||
allocated wireless channels for Dedicated Short-Range Communications | allocated wireless channels for Dedicated Short-Range Communications | |||
(DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with | (DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with | |||
the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band). DSRC- | the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band). DSRC- | |||
based wireless communications can support vehicle-to-vehicle (V2V), | based wireless communications can support vehicle-to-vehicle (V2V), | |||
skipping to change at page 30, line 16 ¶ | skipping to change at page 30, line 16 ¶ | |||
virtual bogus vehicles, and register them with IP-RSUs and MA. This | virtual bogus vehicles, and register them with IP-RSUs and MA. This | |||
registration makes the IP-RSUs and MA waste their resources. The IP- | registration makes the IP-RSUs and MA waste their resources. The IP- | |||
RSUs and MA need to determine whether a vehicle is genuine or bogus | RSUs and MA need to determine whether a vehicle is genuine or bogus | |||
in mobility management. Also, the confidentiality of control packets | in mobility management. Also, the confidentiality of control packets | |||
and data packets among IP-RSUs and MA, the E2E paths (e.g., tunnels) | and data packets among IP-RSUs and MA, the E2E paths (e.g., tunnels) | |||
need to be protected by secure communication channels. In addition, | need to be protected by secure communication channels. In addition, | |||
to prevent bogus IP-RSUs and MA from interfering with the IPv6 | to prevent bogus IP-RSUs and MA from interfering with the IPv6 | |||
mobility of vehicles, mutual authentication among them needs to be | mobility of vehicles, mutual authentication among them needs to be | |||
performed by certificates (e.g., TLS certificate). | performed by certificates (e.g., TLS certificate). | |||
7. Informative References | 7. IANA Considerations | |||
This document does not require any IANA actions. | ||||
8. Informative References | ||||
[Automotive-Sensing] | [Automotive-Sensing] | |||
Choi, J., Va, V., Gonzalez-Prelcic, N., Daniels, R., R. | Choi, J., Va, V., Gonzalez-Prelcic, N., Daniels, R., R. | |||
Bhat, C., and R. W. Heath, "Millimeter-Wave Vehicular | Bhat, C., and R. W. Heath, "Millimeter-Wave Vehicular | |||
Communication to Support Massive Automotive Sensing", | Communication to Support Massive Automotive Sensing", | |||
IEEE Communications Magazine, December 2016. | IEEE Communications Magazine, December 2016. | |||
[Bitcoin] Nakamoto, S., "Bitcoin: A Peer-to-Peer Electronic Cash | [Bitcoin] Nakamoto, S., "Bitcoin: A Peer-to-Peer Electronic Cash | |||
System", URL: https://bitcoin.org/bitcoin.pdf, May 2009. | System", URL: https://bitcoin.org/bitcoin.pdf, May 2009. | |||
[CA-Cruise-Control] | [CA-Cruise-Control] | |||
California Partners for Advanced Transportation Technology | California Partners for Advanced Transportation Technology | |||
(PATH), "Cooperative Adaptive Cruise Control", [Online] | (PATH), "Cooperative Adaptive Cruise Control", Available: | |||
Available: | ||||
http://www.path.berkeley.edu/research/automated-and- | http://www.path.berkeley.edu/research/automated-and- | |||
connected-vehicles/cooperative-adaptive-cruise-control, | connected-vehicles/cooperative-adaptive-cruise-control, | |||
2017. | 2017. | |||
[CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A | [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A | |||
Framework of Context-Awareness Safety Driving in Vehicular | Framework of Context-Awareness Safety Driving in Vehicular | |||
Networks", International Workshop on Device Centric Cloud | Networks", International Workshop on Device Centric Cloud | |||
(DC2), March 2016. | (DC2), March 2016. | |||
[CBDN] Kim, J., Kim, S., Jeong, J., Kim, H., Park, J., and T. | [CBDN] Kim, J., Kim, S., Jeong, J., Kim, H., Park, J., and T. | |||
skipping to change at page 31, line 22 ¶ | skipping to change at page 31, line 22 ¶ | |||
[EU-2008-671-EC] | [EU-2008-671-EC] | |||
European Union, "Commission Decision of 5 August 2008 on | European Union, "Commission Decision of 5 August 2008 on | |||
the Harmonised Use of Radio Spectrum in the 5875 - 5905 | the Harmonised Use of Radio Spectrum in the 5875 - 5905 | |||
MHz Frequency Band for Safety-related Applications of | MHz Frequency Band for Safety-related Applications of | |||
Intelligent Transport Systems (ITS)", EU 2008/671/EC, | Intelligent Transport Systems (ITS)", EU 2008/671/EC, | |||
August 2008. | August 2008. | |||
[FirstNet] | [FirstNet] | |||
U.S. National Telecommunications and Information | U.S. National Telecommunications and Information | |||
Administration (NTIA), "First Responder Network Authority | Administration (NTIA), "First Responder Network Authority | |||
(FirstNet)", [Online] | (FirstNet)", Available: https://www.firstnet.gov/, 2012. | |||
Available: https://www.firstnet.gov/, 2012. | ||||
[FirstNet-Report] | [FirstNet-Report] | |||
First Responder Network Authority, "FY 2017: ANNUAL REPORT | First Responder Network Authority, "FY 2017: ANNUAL REPORT | |||
TO CONGRESS, Advancing Public Safety Broadband | TO CONGRESS, Advancing Public Safety Broadband | |||
Communications", FirstNet FY 2017, December 2017. | Communications", FirstNet FY 2017, December 2017. | |||
[Fuel-Efficient] | [Fuel-Efficient] | |||
van de Hoef, S., H. Johansson, K., and D. V. Dimarogonas, | van de Hoef, S., H. Johansson, K., and D. V. Dimarogonas, | |||
"Fuel-Efficient En Route Formation of Truck Platoons", | "Fuel-Efficient En Route Formation of Truck Platoons", | |||
IEEE Transactions on Intelligent Transportation Systems, | IEEE Transactions on Intelligent Transportation Systems, | |||
skipping to change at page 32, line 35 ¶ | skipping to change at page 32, line 35 ¶ | |||
Networking - Amendment 1", ISO 21210:2012/AMD 1:2017, | Networking - Amendment 1", ISO 21210:2012/AMD 1:2017, | |||
September 2017. | September 2017. | |||
[NHTSA-ACAS-Report] | [NHTSA-ACAS-Report] | |||
National Highway Traffic Safety Administration (NHTSA), | National Highway Traffic Safety Administration (NHTSA), | |||
"Final Report of Automotive Collision Avoidance Systems | "Final Report of Automotive Collision Avoidance Systems | |||
(ACAS) Program", DOT HS 809 080, August 2000. | (ACAS) Program", DOT HS 809 080, August 2000. | |||
[OMNI] Templin, F. and A. Whyman, "Transmission of IPv6 Packets | [OMNI] Templin, F. and A. Whyman, "Transmission of IPv6 Packets | |||
over Overlay Multilink Network (OMNI) Interfaces", draft- | over Overlay Multilink Network (OMNI) Interfaces", draft- | |||
templin-6man-omni-interface-24 (work in progress), June | templin-6man-omni-interface-27 (work in progress), June | |||
2020. | 2020. | |||
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast | [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast | |||
Listener Discovery (MLD) for IPv6", RFC 2710, October | Listener Discovery (MLD) for IPv6", RFC 2710, October | |||
1999. | 1999. | |||
[RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On- | ||||
Demand Distance Vector (AODV) Routing", RFC 3561, July | ||||
2003. | ||||
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", | [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", | |||
RFC 3753, June 2004. | RFC 3753, June 2004. | |||
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery | [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery | |||
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. | Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. | |||
[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix | [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix | |||
Reserved for Documentation", RFC 3849, July 2004. | Reserved for Documentation", RFC 3849, July 2004. | |||
[RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, | [RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, | |||
skipping to change at page 34, line 36 ¶ | skipping to change at page 34, line 33 ¶ | |||
[RFC6830BIS] | [RFC6830BIS] | |||
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. | Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. | |||
Cabellos, "The Locator/ID Separation Protocol (LISP)", | Cabellos, "The Locator/ID Separation Protocol (LISP)", | |||
draft-ietf-lisp-rfc6830bis-32 (work in progress), March | draft-ietf-lisp-rfc6830bis-32 (work in progress), March | |||
2020. | 2020. | |||
[RFC7149] Boucadair, M. and C. Jacquenet, "Software-Defined | [RFC7149] Boucadair, M. and C. Jacquenet, "Software-Defined | |||
Networking: A Perspective from within a Service Provider | Networking: A Perspective from within a Service Provider | |||
Environment", RFC 7149, March 2014. | Environment", RFC 7149, March 2014. | |||
[RFC7181] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, | ||||
"The Optimized Link State Routing Protocol Version 2", | ||||
RFC 7181, April 2014. | ||||
[RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. | [RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. | |||
Kivinen, "Internet Key Exchange Protocol Version 2 | Kivinen, "Internet Key Exchange Protocol Version 2 | |||
(IKEv2)", RFC 7296, October 2014. | (IKEv2)", RFC 7296, October 2014. | |||
[RFC7333] Chan, H., Liu, D., Seite, P., Yokota, H., and J. Korhonen, | [RFC7333] Chan, H., Liu, D., Seite, P., Yokota, H., and J. Korhonen, | |||
"Requirements for Distributed Mobility Management", | "Requirements for Distributed Mobility Management", | |||
RFC 7333, August 2014. | RFC 7333, August 2014. | |||
[RFC7429] Liu, D., Zuniga, JC., Seite, P., Chan, H., and CJ. | [RFC7429] Liu, D., Zuniga, JC., Seite, P., Chan, H., and CJ. | |||
Bernardos, "Distributed Mobility Management: Current | Bernardos, "Distributed Mobility Management: Current | |||
skipping to change at page 36, line 7 ¶ | skipping to change at page 35, line 45 ¶ | |||
Koukoumidis, E., Peh, L., and M. Martonosi, "SignalGuru: | Koukoumidis, E., Peh, L., and M. Martonosi, "SignalGuru: | |||
Leveraging Mobile Phones for Collaborative Traffic Signal | Leveraging Mobile Phones for Collaborative Traffic Signal | |||
Schedule Advisory", ACM MobiSys, June 2011. | Schedule Advisory", ACM MobiSys, June 2011. | |||
[TR-22.886-3GPP] | [TR-22.886-3GPP] | |||
3GPP, "Study on Enhancement of 3GPP Support for 5G V2X | 3GPP, "Study on Enhancement of 3GPP Support for 5G V2X | |||
Services", 3GPP TR 22.886/Version 16.2.0, December 2018. | Services", 3GPP TR 22.886/Version 16.2.0, December 2018. | |||
[Truck-Platooning] | [Truck-Platooning] | |||
California Partners for Advanced Transportation Technology | California Partners for Advanced Transportation Technology | |||
(PATH), "Automated Truck Platooning", [Online] Available: | (PATH), "Automated Truck Platooning", Available: | |||
http://www.path.berkeley.edu/research/automated-and- | http://www.path.berkeley.edu/research/automated-and- | |||
connected-vehicles/truck-platooning, 2017. | connected-vehicles/truck-platooning, 2017. | |||
[TS-23.285-3GPP] | [TS-23.285-3GPP] | |||
3GPP, "Architecture Enhancements for V2X Services", 3GPP | 3GPP, "Architecture Enhancements for V2X Services", 3GPP | |||
TS 23.285/Version 16.2.0, December 2019. | TS 23.285/Version 16.2.0, December 2019. | |||
[TS-23.287-3GPP] | [TS-23.287-3GPP] | |||
3GPP, "Architecture Enhancements for 5G System (5GS) to | 3GPP, "Architecture Enhancements for 5G System (5GS) to | |||
Support Vehicle-to-Everything (V2X) Services", 3GPP | Support Vehicle-to-Everything (V2X) Services", 3GPP | |||
End of changes. 11 change blocks. | ||||
23 lines changed or deleted | 18 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |