SIST EN 302 636-6-1 V1.2.1:2014
(Main)Intelligent Transport Systems (ITS) - Vehicular Communications - GeoNetworking - Part 6: Internet Integration - Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols
Intelligent Transport Systems (ITS) - Vehicular Communications - GeoNetworking - Part 6: Internet Integration - Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols
The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol as defined in ETSI EN 302 636-4-1 [7] via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL. The techniques specified in the present document fulfil the requirements for GeoNetworking and IPv6 integration described in ETSI EN 302 636-1 [3]. In particular, these techniques allow for the transport of IPv6 packets by ETSI GeoNetworking protocol given in ETSI EN 302 636-4-1 [7], enabling sub-IP multi-hop delivery of IPv6 packets, e.g. in a vehicular network. As a result, the connectivity provided by points-of-attachment to IPv6 infrastructure networks is extended by means of mobile relay nodes. In addition to that, the techniques described in the present document allow for geocasting of IPv6 multicast packets. The scope of the GN6ASL is limited to the fulfilment of the requirements for GeoNetworking and IPv6 integration described in ETSI EN 302 636-1 [3], clause 5.9, by enabling an ITS station including a GeoAdhoc router as given in ETSI EN 302 636-4-1 [7] running the GeoNetworking protocol and an IPv6-compliant protocol layer to:
• exchange IPv6 packets with other ITS stations;
• acquire globally routable IPv6 unicast addresses and communicate with an arbitrary IPv6 host located in the Internet, whenever an ITS station including a GeoAdhoc router and including or connected to an access router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations;
• perform the operations required by IETF RFC 3963 [14] for a Mobile Router whenever:
a) an ITS mobile router supporting Network Mobility Basic Support (NEMO BS) as defined in IETF RFC 3963 [14] is present in the ITS station and runs on top of the GN6ASL; and
b) an ITS station including a GeoAdhoc router and including or connected to an access router as defined in ETSI TS 102 636-3 [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations.
NOTE: The present document adopts the definition of "IPv6-compliant" and "sub-IP multi-hop delivery"
introduced in clause 3.1. Extending the IPv6 basic standards IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF RFC 4861 [11] and IETF RFC 4862 [13] to support new features is outside the scope of the present document. Extensions to NEMO BS as given in IETF RFC 3963 [14] are outside the scope of the present document. Mechanisms for the dissemination of IPv6 routing information for hosts and routers not directly attaching to the network where GeoNetworking is used are outside the scope of the present document (e.g. discovery of IPv6 in-vehicle prefixes). However, the present document aims at providing the underlying support for the dissemination of such routing information, i.e. IPv6 multicast support for the network where the GeoNetworking protocol is used. With respect to IPv6 multicast and anycast support, the present document is limited to the support required to enable distribution of IPv6 multicast and anycast traffic on a shared link. Amendments to specific IPv6 multicast forwarding mechanisms are out of the scope of the present document. However, the present document aims at not preventing existing IPv6 multicast forwarding mechanisms from being used in conjunction with the GN6ASL. In order to facilitate the deployment of ITS systems, the present document aims at maintaining backward compatibility with pre-existent IPv6-compliant protocol implementations and NEMO BS implementations compliant with IETF RFC 3963 [14]. A usage example of NEMO BS with the GN6ASL is presented in the informative annex F. The mechanisms specified in the present document are distinct from but compatible with the IPv6-related functionalities given in ISO 21210-2010 [i.20], which specifies how IPv6 networking is generally operated in ITS stations.
Inteligentni transportni sistemi (ITS) - Komunikacije med vozili - Geomreženje - 6. del: Vključitev v internet - 1. poddel: Prenos paketov IPv6 po protokolih geomreženja
Ta dokument določa prenos paketov IPv6 po protokolu geomreženj ETSI, kot je opredeljeno v ETSI EN 302 636-4-1 [7], prek podsloja prilagoditve protokola, imenovanega GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). Obseg tega dokumenta je omejen na GN6ASL. Tehnike, določene v tem dokumentu, izpolnjujejo zahteve za vključitev geomreženja in IPv6, opisane v ETSI EN 302 636-1 [3]. Te tehnike predvsem omogočajo prenos paketov IPv6 s protokolom geomreženja ETSI, podanim v ETSI EN 302 636-4-1 [7], kar omogoča sub-IP multi-hop prenose paketov IPv6 v, na primer v omrežju vozil. Povezljivost, ki jo zagotavljajo točke za povezovanje na omrežja z infrastrukturo IPv6, je posledično razširjena prek mobilnih posredniških vozlišč. Poleg tega metode, opisane v tem dokumentu, omogočajo usmerjanje prenosa paketov IPv6 več prejemnikom glede na geografsko lokacijo. Področje uporabe GN6ASL je omejeno na izpolnjevanje zahtev za integracijo geomreženja in IPv6, opisano v točki 5.9 ETSI EN 302 636-1 [3], z omogočanjem postaje ITS, ki vključuje usmerjevalnik GeoAdhoc, kot je določeno v ETSI EN 302 636-4-1 [7], ki poganja protokol geomreženja in sloj protokola, ki je združljiv z IPv6 za:
• izmenjavo IPv6 paketov z drugimi postajami ITS;
• pridobitev globalno usmerjenih unicast naslovov IPv6 in komuniciranje z arbitrarnim gostiteljem IPv6, ki se nahaja v internetu, vedno, ko je postaja ITS z usmerjevalnikom GeoAdhoc, ki vključuje ali je povezana na dostopni usmerjevalnik [5], ki zagotavlja povezljivost IPv6 z internetom, neposredno dostopna ali dostopna prek drugih posredniških postaj ITS;
• izvajanje operacij, ki jih zahteva IETF RFC 3963 [14] za mobilni usmerjevalnik vedno, ko:
a) je mobilni usmerjevalnik ITS, ki podpira Network Mobility Basic Support (NEMO BS), definiran v IETF RFC 3963 [14], prisoten v postaji ITS in deluje poleg GN6ASL; in
b) je postaja ITS z usmerjevalnikom GeoAdhoc, ki vključuje ali je povezana na dostopni usmerjevalnik, ki je definirana v ETSI TS 102 636-3 [5] in ki zagotavlja povezljivost IPv6 z internetom, neposredno dostopna ali dostopna prek drugih posredniških postaj ITS
OPOMBA: Ta dokument sprejme definiciji za »združljiv z IPv6« in »sub-IP multi-hop prenos«,
ki sta bili vpeljani v točki 3.1. Razširitev osnovnih standardov IPv6 IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF RFC 4861 [11] in IETF RFC 4862 [13] za podporo novih funkcij ne spada na področje uporabe tega dokumenta. Razširitve za NEMO BS, kot so določene v IETF RFC 3963 [14], ne spadajo v področje uporabe tega dokumenta. Mehanizmi za širjenje informacij o usmerjanju IPv6 za gostitelje in usmerjevalnike, ki niso neposredno povezani v omrežje, kjer se uporablja geomreženje, ne spadajo v področje uporabe tega dokumenta (npr. odkritje predpon IPv6 v vozilu). Kljub temu je cilj tega dokumenta zagotavljanje osnovne podpore za širjenje informacij o usmerjanju, tj. podpora prenosa paketov več prejemnikom IPv6 za omrežja, kjer se uporablja geomreženje. V zvezi s podporo za prenos paketov več uporabnikom (multicast) in najbližjim uporabnikom (anycast) IPv6 je ta dokument omejen na podporo, ki je potrebna za porazdelitev prometa več uporabnikom in najbližjim uporabnikom prek skupne povezave. Dodatki k določenim mehanizmom za posredovanje podatkov več uporabnikom IPv6 ne spadajo v področje uporabe tega dokumenta.
General Information
Standards Content (Sample)
Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
European Standard
Intelligent Transport Systems (ITS);
Vehicular Communications;
GeoNetworking;
Part 6: Internet Integration;
Sub-part 1: Transmission of IPv6 Packets over
GeoNetworking Protocols
2 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
Reference
REN/ITS-0030037
Keywords
addressing, Autonomic Networking, IPv6, ITS,
network, protocol
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2013.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 8
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definitions, symbols and abbreviations . 12
3.1 Definitions . 12
3.2 Symbols . 12
3.3 Abbreviations . 12
4 GN6ASL in the ITS station architecture . 13
5 IPv6 link models and interfaces . 14
5.1 Rationale. 14
5.2 Properties of supported IPv6 link models . 15
5.2.1 Geographical virtual links . 15
5.2.1.1 Static geographical virtual links . 15
5.2.1.2 Dynamic geographical virtual links . 15
5.2.2 Topological virtual links . 16
5.2.3 Virtual links indexing . 16
5.3 Properties of virtual interfaces . 16
5.3.1 Number and types of virtual interfaces . 16
5.3.2 Usage of specific virtual interfaces . 17
5.3.2.1 Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 17
6 Bridging support . 18
6.1 Rationale. 18
6.2 Required properties . 20
6.3 Media-dependent implementations . 20
6.3.1 IEEE 802 integration service . 20
7 IPv6/GeoNetworking interface service specification . 20
8 Encapsulation characteristics . 21
8.1 Maximum transmission unit . 21
8.2 Packet delivery . 21
8.2.1 Outbound traffic . 21
8.2.2 Inbound traffic . 22
8.3 Frame format . 24
9 IPv6 multicast and anycast support . 24
9.1 Overview . 24
9.2 IPv6 multicast support . 25
9.2.1 IPv6 link-local multicast . 25
9.2.2 IPv6 wider-scope multicast . 25
9.2.3 Geocasting of IPv6 multicast traffic . 26
9.3 IPv6 anycast support . 26
9.4 Geographic IPv6 anycast support . 26
10 IPv6 neighbor discovery support . 27
10.1 On-link determination . 27
10.2 Address configuration . 27
10.2.1 Stateless address autoconfiguration . 27
10.2.2 Stateful address configuration. 28
10.2.3 Manual address configuration . 28
ETSI
4 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
10.3 Address resolution . 28
10.3.1 Non-ND-based address resolution . 28
10.3.2 ND-based address resolution . 29
10.4 Neighbor unreachability detection . 29
10.5 Protocol constants. 29
11 Support for pseudonym change . 29
11.1 Rationale. 29
11.2 Required operations . 30
Annex A (normative): ASN.1 encoding of the GN6ASL MIB . 31
A.1 Modules . 31
A.1.1 ITSGN6ASL-MIB . 31
Annex B (normative): MIB attributes . 35
B.1 ITSGN6ASL-MIB attributes values . 35
Annex C (informative): IPv6/GeoNetworking data SAP . 36
C.1 Basic data SAP (GN6_SAP) . 36
C.1.1 Overview . 36
C.1.2 Service primitives . 36
C.1.2.1 GN6-UNITDATA.request . 36
C.1.2.1.1 Semantics . 36
C.1.2.1.2 When generated . 36
C.1.2.1.3 Effect on receipt . 36
C.1.2.2 GN6-UNITDATA.indication . 37
C.1.2.2.1 Semantics . 37
C.1.2.2.2 When generated . 37
C.1.2.2.3 Effect on receipt . 37
C.2 Experimental extended data SAP (EGN6_SAP) . 37
C.2.1 Overview . 37
C.2.2 Service primitives . 38
C.2.2.1 EGN6-UNITDATA.request . 38
C.2.2.1.1 Semantics . 38
C.2.2.1.2 When generated . 38
C.2.2.1.3 Effect on receipt . 38
C.2.2.2 EGN6-UNITDATA.indication . 39
C.2.2.2.1 Semantics . 39
C.2.2.2.2 When generated . 39
C.2.2.2.3 Effect on receipt . 39
Annex D (informative): Geographic IPv6 multicast support (experimental) . 40
D.1 Overview . . 40
D.2 Pre-defined geographical IPv6 multicast groups . 40
D.3 Other studied mechanisms. 40
Annex E (informative): Implementation examples . 42
E.1 Virtual links and interfaces . 42
E.2 Packet delivery with Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 42
E.2.1 Outbound traffic . 42
E.2.2 Inbound traffic . 43
E.3 GeoNet project implementations results . 43
Annex F (informative): Support for Network Mobility Basic Support . 44
F.1 Purpose of this annex . 44
ETSI
5 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
F.2 Mode of operation via GN6ASL . 44
F.3 Sub-optimal routing issues . 44
Annex G (informative): Security and privacy considerations . 45
G.1 Recommendations for security mechanisms . 45
G.2 Recommendations for privacy-protecting deployment . 45
Annex H (informative): Bibliography . 46
History . 47
ETSI
6 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This draft European Standard (EN) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS), and is now submitted for the combined Public Enquiry and Vote phase of the ETSI standards EN Approval
Procedure.
The present document is part 6, sub-part 1 of a multi-part deliverable. Full details of the entire series can be found in
part 1 [3].
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 18 months after doa
Introduction
The ETSI GeoNetworking protocol [7] and [i.23] is a non-IP network-layer protocol that provides geographic
addressing and forwarding and belongs to the position-based routing protocols category. Applications and facilities
specifically designed for GeoNetworking exploit these functionalities, for example to disseminate warning or generic
information messages to geographically scoped areas. The GeoNetworking protocol satisfies the requirements of
several ITS services, whose application domain is limited to networks that are disconnected from large existing network
infrastructures. However, several ITS applications require the integration of ITS stations with larger networks such as
private transport networks or the Internet.
In order to connect networks based on GeoNetworking to networks running the Internet Protocol (IP), which represent
the majority of currently deployed large networks, it is necessary to allow GeoNetworking ITS stations to act like
Internet hosts or routers. The ETSI Technical Committee ITS recognizes IP version 6 (IPv6 [8]) as the primary version
of IP to be necessarily supported by ITS stations.
The present document introduces a set of mechanisms that allow the GeoNetworking protocol to transport IPv6 packets
without introducing modifications to existing IPv6 protocol implementations. By deploying these mechanisms, the
following two main advantages are achieved:
1) coverage offered by points-of-attachment to the Internet, such as road-side ITS stations, is extended by means
of sub-IP geographic routing; and
2) IPv6 multicast traffic can be geocasted, i.e. addressed and delivered to all ITS stations currently located within
a geographic area.
ETSI
7 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
The present document includes a data SAP that enables an IPv6 protocol entity to send and receive packets over the
GeoNetworking protocol. This SAP is described in the informative annex C. The present document does not include a
management SAP towards the ITS station management entity.
NOTE: In the reminder of the present document, when the sole term "GeoNetworking" is used, it is to be
regarded as the ETSI GeoNetworking protocol combining the media-independent part [7] and at least one
of the media-dependent parts (such as [i.23]). It should be noted that the media-dependent extensions do
not represent distinct protocol layers.
ETSI
8 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
1 Scope
The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol [7] via a
protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of
the present document is limited to the GN6ASL.
The techniques specified in the present document fulfil the requirements for GeoNetworking and IPv6 integration
described in [3]. In particular, these techniques allow for the transport of IPv6 packets by ETSI GeoNetworking
protocol [7], enabling sub-IP multi-hop delivery of IPv6 packets, e.g. in a vehicular network. As a result, the
connectivity provided by points-of-attachment to IPv6 infrastructure networks is extended by means of mobile relay
nodes. In addition to that, the techniques described in the present document allow for geocasting of IPv6 multicast
packets.
The scope of the GN6ASL is limited to the fulfilment of the requirements for GeoNetworking and IPv6 integration
described in [3], clause 5.9, by enabling an ITS station including a GeoAdhoc router [7] running the GeoNetworking
protocol and an IPv6-compliant protocol layer to:
• exchange IPv6 packets with other ITS stations;
• acquire globally routable IPv6 unicast addresses and communicate with an arbitrary IPv6 host located in the
Internet, whenever an ITS station including a GeoAdhoc router and including or connected to an access
router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations;
• perform the operations required by [14] for a Mobile Router whenever:
a) an ITS mobile router supporting Network Mobility Basic Support (NEMO BS) [14] is present in the
ITS station and runs on top of the GN6ASL; and
b) an ITS station including a GeoAdhoc router and including or connected to an access router [5]
providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations.
NOTE: The present document adopts the definition of "IPv6-compliant" and "sub-IP multi-hop delivery"
introduced in clause 3.1.
Extending the IPv6 basic standards [8], [9], [10], [11] and [13] to support new features is outside the scope of the
present document. Extensions to NEMO BS [14] are outside the scope of the present document. Mechanisms for the
dissemination of IPv6 routing information for hosts and routers not directly attaching to the network where
GeoNetworking is used are outside the scope of the present document (e.g. discovery of IPv6 in-vehicle prefixes).
However, the present document aims at providing the underlying support for the dissemination of such routing
information, i.e. IPv6 multicast support for the network where the GeoNetworking protocol is used.
With respect to IPv6 multicast and anycast support, the present document is limited to the support required to enable
distribution of IPv6 multicast and anycast traffic on a shared link. Amendments to specific IPv6 multicast forwarding
mechanisms are out of the scope of the present document. However, the present document aims at not preventing
existing IPv6 multicast forwarding mechanisms from being used in conjunction with the GN6ASL.
In order to facilitate the deployment of ITS systems, the present document aims at maintaining backward compatibility
with pre-existent IPv6-compliant protocol implementations and NEMO BS implementations compliant with [14]. A
usage example of NEMO BS with the GN6ASL is presented in the informative annex F.
The present document requires the assignment by IANA of an anycast identifier for ETSI GeoAnycast Reserved IPv6
Subnet Anycast Address (see clause 9.4).
The mechanisms specified in the present document are distinct from but compatible with the IPv6-related functionalities
in [i.20], which specifies how IPv6 networking is generally operated in ITS stations. The techniques described in the
present document provide a way to transport IPv6 packets that is fully compatible with the IPv6 specifications and
pre-existing implementations, and hence is compatible with [i.20].
ETSI
9 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbo0x.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture".
[2] ETSI EN 302 663: "Intelligent Transport Systems (ITS); Access layer specification for Intelligent
Transport Systems operating in the 5 GHz frequency band".
[3] ETSI EN 302 636-1: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 1: Requirements".
[4] ETSI EN 302 636-2: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 2: Scenarios".
[5] ETSI TS 102 636-3: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 3: Network architecture".
[6] ETSI EN 302 931: "Intelligent Transport Systems (ITS); Vehicular Communications;
Geographical Area Definition".
[7] ETSI EN 302 636-4-1: "Intelligent Transport System (ITS); Vehicular communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and
point-to-multipoint communications; Sub-part 1: Media independent functionalities".
[8] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[9] IETF RFC 4291: "IP Version 6 (IPv6) Addressing Architecture".
[10] IETF RFC 4007: "IPv6 Scoped Address Architecture".
[11] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[12] IETF RFC 5942: "IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes".
[13] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[14] IETF RFC 3963: "Network Mobility (NEMO) Basic Support Protocol".
[15] IETF RFC 6724: "Default Address Selection for Internet Protocol version 6 (IPv6)".
[16] IETF RFC 2464: "Transmission of IPv6 Packets over Ethernet Networks".
[17] IETF RFC 5072: "IP Version 6 over PPP".
[18] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
[19] IETF RFC 4601: "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
Specification (Revised)".
[20] IETF RFC 4605: "Internet Group Management Protocol (IGMP) / Multicast Listener Discovery
(MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")".
ETSI
10 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
[21] IETF RFC 3306: "Unicast-Prefix-based IPv6 Multicast Addresses".
[22] IETF RFC 2022: "Support for Multicast over UNI 3.0/3.1 based ATM Networks".
[23] IETF RFC 1042: "Standard for the Transmission of IP Datagrams over IEEE 802 Networks".
[24] IETF RFC 3971: "SEcure Neighbor Discovery (SEND)".
[25] IETF RFC 4293: "Management Information Base for the Internet Protocol (IP)".
[26] IETF RFC 2526: "Reserved IPv6 Subnet Anycast Addresses".
[27] ISO/IEC 8802-2:1998: "Information technology-Telecommunications and information exchange
between systems-Local and metropolitan area networks-Specific requirements-Part 2: Logical link
control".
[28] ISO/IEC 15802-3: "Information Technology-Telecommunications and information exchange
between systems-Local and metropolitan area networks-Common specifications-Part 3: Media
Access Control (MAC) Bridges" (previously known as IEEE Std 802.1D-1998).
[29] IEEE 802.11:2012: "IEEE Standard for Information Technology - Telecommunications and
Information Exchange Between Systems-Local and Metropolitan Area Networks - Specific
Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[30] IEEE 802.1Q:1998: "IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged
Local Area Networks".
[31] IEEE 802.3:2008 "IEEE Standard for Information Technology - Telecommunications and
information exchange between systems-Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
Access Method and Physical Layer Specifications".
[32] IEEE "Guidelines For 64-bit Global Identifier (EUI-64)".
NOTE: Available at: http://standards.ieee.org/regauth/oui/tutorials/EUI64.html.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 3753: "Mobility Related Terminology".
[i.2] IETF RFC 4885: "Network Mobility Support Terminology".
[i.3] IETF RFC 6434: "IPv6 Node Requirements".
[i.4] IETF RFC 4903: "Multi-Link Subnet Issues".
[i.5] IETF RFC 4840: "Multiple Encapsulation Methods Considered Harmful".
[i.6] IETF RFC 3316: "Internet Protocol Version 6 (IPv6) for Some Second and Third Generation
Cellular Hosts".
[i.7] IETF RFC 5154: "IP over IEEE 802.16 Problem Statement and Goals".
[i.8] IETF RFC 3549: "Linux Netlink as an IP Services Protocol".
[i.9] IETF RFC 3314: "Recommendations for IPv6 in Third Generation Partnership Project (3GPP)
Standards".
[i.10] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".
[i.11] IETF RFC 2578: "Structure of Management Information Version 2 (SMIv2)".
ETSI
11 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
[i.12] IETF RFC 2579: "Textual Conventions for SMIv2".
[i.13] IETF RFC 2491: "IPv6 over Non-Broadcast Multiple Access (NBMA) networks".
[i.14] IETF RFC 6775: "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs)".
[i.15] ETSI TR 102 893: "Intelligent Transport Systems (ITS); Security; Threat, Vulnerability and Risk
Analysis (TVRA)".
[i.16] ETSI TS 102 731: "Intelligent Transport Systems (ITS); Security; Security Services and
Architecture".
[i.17] ETSI TS 103 097:"Intelligent Transport Systems (ITS); Security; Security header and certificate
formats for ITS G5".
[i.18] ETSI TS 102 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set
of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[i.19] Universal TUN/TAP driver for Linux, Solaris and FreeBSD.
NOTE: Available at http://vtun.sourceforge.net/tun/index.html.
[i.20] ISO 21210-2010: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - IPv6 networking".
[i.21] ETSI TS 123 060: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service
description; Stage 2 (3GPP TS 23.060 Release 9)".
[i.22] ISO/IEC Technical Report 11802-5:1997(E): "Information technology-Telecommunications and
information exchange between systems-Local and metropolitan area networks-Technical reports
and guidelines-Part 5: Medium Access Control (MAC) Bridging of Ethernet V2.0 in Local Area
Networks" (previously known as IEEE Std 802.1H-1997).
[i.23] ETSI TS 102 636-4-2: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-
multipoint communications; Sub-part 2: Media dependent functionalities for ITS-G5A media".
[i.24] ETSI TS 102 723-10: "Intelligent Transport Systems; OSI cross-layer topics; Part 10: Interface
between access layer and network and transport layers".
[i.25] GeoNet D1.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D1.2 v1.1: "Final GeoNet Architecture
Design".
[i.26] GeoNet D2.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D2.2 v1.1: "Specification - Final Release".
[i.27] GeoNetD7.1: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D7.1 v1.0: "GeoNet Experimentation Results".
[i.28] NemoROReqDraft: IETF draft-ietf-mext-nemo-ro-automotive-req-02 (July 2009): "Automotive
Industry Requirements for NEMO Route Optimization".
ETSI
12 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1], [5], [11], [i.3], [i.2] and the following
apply:
geographical virtual link: link-local multicast-capable virtual link spanning multiple physical links with
geographically scoped boundaries
GN6 adaptation sub-layer: protocol adaptation sub-layer supporting the transmission of IPv6 packets over the
GeoNetworking protocol
GVL area: geographical area associated with a GVL
IPv6-compliant: compliant with [8], [9], [10], [11] and [13]
IPv6 next hop: IPv6 node resulting from the next-hop determination described in [11], section 5.2
sub-IP multi-hop delivery: IP packet delivery traversing several ITS stations where the Hop Limit field of the IPv6
header [8] is not decreased
topological virtual link: link-local multicast-capable virtual link spanning multiple physical links with topologically
scoped boundaries
3.2 Symbols
For the purposes of the present document, the following symbols apply:
GEO Size of the largest GeoNetworking header
MAX
GN_SAP GeoNetworking Service Access Point
MTU Maximum transmission unit offered by the protocol layer below GeoNetworking
AL
MTU Maximum transmission unit offered by GN6ASL to IPv6
GN6
MTU Typical maximum transmission unit associated to the type of a virtual interface
VI
STALE Stale state of an IPv6 Neighbor Cache entry
VL_ID Virtual Link IDentifier
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASL Adaptation Sub-Layer
ASN.1 Abstract Syntax Notation One
CGA Cryptographically Generated Addresses
DGVL Dynamic Geographical Virtual Link
EDCA Enhanced Distributed Channel Access
EIID Extended Interface Identifier
EUI Extended Unique Identifier
GN6 GeoNetworking-IPv6
GN6ASL GeoNetworking-IPv6 Adaptation Sub-Layer
GN6SDU GN6 Service Data Unit
GPRS General Packet Radio Service
GVL Geographical Virtual Link
IANA Internet Assigned Numbers Authority
ID Identifier
IID Interface Identifier
IP Internet Protocol
ITS Intelligent Transport System
LAN Local Area Network
ETSI
13 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
LLC Logical Link Control
MAC Media Access Control
MIB Managed Information Base
MID MAC ID
MTU Maximum Transmission Unit
NA Neighbor Advertisement
ND Neighbor Discovery
NEMO BS NEtwork MObility Basic Support
NH Next Header
NIC Network Interface Controller
NS Neighbor Solicitation
NS/NA Neighbour Solicitation/Neighbour Advertisement
NUD Neighbor Unreachability Detection
OUI Organizationally Unique Identifier
PDCP Packet Data Convergence Protocol
PHY PHYsical
PPP Point-to-Point Protocol
RA Router Advertisement
SAP Service Access Point
SDU Service Data Unit
SEND SEcure Neighbor Discovery
SGVL Static Geographical Virtual Link
SLAAC StateLess Address AutoConfiguration
SMI Structure of Management Information
SNAP SubNetwork Access Protocol
SNMPv2-TC Simple Network Management Protocol version 2 - Textual Conventions
STA STAtion
TAP Terminal Access Point
TBD To Be Defined
TCP Transmission Control Protocol
TSB Topologically Scoped Broadcast
TUN network TUNnel
TVL Topological Virtual Link
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications Systems
VC Virtual Circuit
VLAN Virtual Local Area Network
4 GN6ASL in the ITS station architecture
With respect to the ITS station reference architecture [1], the present document only affects the layer Networking &
Transport. As depicted in figure 1, within the layer Networking & Transport, the present document introduces
GN6ASL, an adaptation sub-layer for the transmission of IPv6 packets over the GeoNetworking protocol. The other
protocols depicted in figure 1 (e.g. TCP and UDP) are represented for sake of completeness in order to represent a
typical usage of the present document.
ETSI
14 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
Figure 1: GN6ASL in the ITS station architecture
As depicted in figure 1, the present document builds an adaptation sub-layer (GN6ASL) between the ETSI
GeoNetworking protocol [7] and an IPv6-compliant protocol layer with mobility extensions. The default IPv6 mobility
extension in the ETSI ITS architecture [1] (as well as in [i.20]) is the Network Mobility Basic Support (NEMO BS)
protocol [14]. The present document enables the usage of NEMO BS over the ETSI GeoNetworking protocol [7].
NOTE: With respect to figure 1, the scope of [i.20] includes the protocol layer IPv6 + Mobility Extensions,
directly above the adaptation sub-layer specified in the present document.
5 IPv6 link models and interfaces
5.1 Rationale
The Neighbor Discovery (ND) protocol [11] is a mandatory part of IPv6 stacks that includes functionalities such as
Router and Prefix Discovery as well as Address Resolution and Neighbor Unreachability Detection. Some of ND's
services use link-layer multicast addresses. This implies that the link-layer protocol is required to support multicast
addressing in order to run the ND protocol as described in [11]. ND adaptations or alternative protocols or mechanisms
to implement its services are commonly introduced for link-layer technologies that do not support multicast addressing
(e.g. [i.13], [i.6], [i.7]).
In addition to link-local multicast support, ND also requires symmetric reachability (defined in [11]).
GN6ASL is presented to the IPv6 layer as a link-layer protocol which relies on the GeoNetworking protocol [7]. The
GeoNetworking protocol provides both point-to-point and point-to-multipoint communications, as well as
geographically scoped addressing such as GeoAnycast and GeoBroadcast [4]. Furthermore, the GeoNetworking
protocol [7] provides upper layers with a sub-IP multi-hop delivery service as required by [3].
NOTE: "sub-IP multi-hop delivery" is defined in clause 3.1.
The present document introduces three types of virtual link, one providing symmetric reachability by means of stable
geographically scoped boundaries. The other two do not provide symmetric reachablity but can be used when the
dynamic definition of the broadcast domain is required. The combination of these types of virtual link in the same
station allows running the ND protocol including SLAAC [13] as well as to distribute other IPv6 link-local multicast
traffic and, at the same time, to reach nodes that are outside specific geographic boundaries.
ETSI
15 Draft ETSI EN 302 636-6-1 V1.2.0 (2013-10)
EXAMPLE: In 3GPP Release 9, IPv6 is transported directly over PDCP, and optionally via PPP [i.21]. In both
cases, over PDCP and via PPP, virtual point-to-point links are used. [i.21] uses some ND
operations such as the issuing of a Router Solicitation although, as pointed out in [i.9], the IETF
has not specified a point-to-point architecture, nor how the standard IPv6 address assignment
mechanisms are applicable to IPv6 over point-to-point links. [i.9] called for the (at that time still
existing) IPv6 WG to carry out these activities but to date no specification exists.
In the following, virtual links are distinguished from virtual interfaces. A virtual interface represents an instance of a
virtual link that is presented to the IPv6 layer in an implementation-specific way.
5.2 Properties of supported IPv6 link models
5.2.1 Geographical virtual links
A Geographical Virtual Link (GVL) is a link-local multicast-capable virtual link spanning multiple physical links with
geographically scoped boundaries. GN6ASL of a GeoAdhoc router shall support GVLs.
Each GVL shall be associated with one single GeoNetworking GEOBROADCAST/GEOANYCAST area (also called
geoarea in [7] and specified in [6]) stored in the per-GVL MIB attributes itsGn6aslGvlAreaCenterLatitude
itsGn6aslGvlAreaCenterLongitude itsGn6aslGvlAreaDistA itsGn6aslGvlAreaDistB itsGn6aslGvlAreaAngle. These
attributes are referred to as the GVL Area.
A GVL is shared among several GeoAdhoc routers when all of the GeoAdhoc routers use the same GVL area.
The per-link MIB attributes of a GVL are specified in annex B.
Two sub-types of GVL exist: Static GVL (SGVL) and Dynamic GVL (DGVL).
5.2.1.1 Static geographical virtual links
A Static Geographical Virtual Link (SGVL) is a GVL whose GVL Area shall be:
• derived from a received GeoNetworking header encapsulating a Router Advertisements (RA) message [11] as
described in clause 10.2.1; or
• assigned by the ITS station management entity only in roadside ITS stations.
When no GVL Area is set, a SGVL shall be disabled. When the GVL Area is set, the SGVL shall be (re)enabled. While
a GVL is enabled, the GVL Area may not be modified.
Multiple SGVLs may be enabled simultaneously per entry in the GeoNet
...
ETSI EN 302 636-6-1 V1.2.1 (2014-05)
European Standard
Intelligent Transport Systems (ITS);
Vehicular Communications;
GeoNetworking;
Part 6: Internet Integration;
Sub-part 1: Transmission of IPv6 Packets over
GeoNetworking Protocols
2 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
Reference
REN/ITS-0030037
Keywords
addressing, Autonomic Networking, IPv6, ITS,
network, protocol
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2014.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 8
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definitions, symbols and abbreviations . 12
3.1 Definitions . 12
3.2 Symbols . 12
3.3 Abbreviations . 12
4 GN6ASL in the ITS station architecture . 13
5 IPv6 link models and interfaces . 14
5.1 Rationale. 14
5.2 Properties of supported IPv6 link models . 15
5.2.1 Geographical virtual links . 15
5.2.1.1 Static geographical virtual links . 15
5.2.1.2 Dynamic geographical virtual links . 15
5.2.2 Topological virtual links . 16
5.2.3 Virtual links indexing . 16
5.3 Properties of virtual inter faces . 16
5.3.1 Number and types of virtual interfaces . 16
5.3.2 Usage of specific virtual interfaces . 17
5.3.2.1 Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 17
6 Bridging support . 18
6.1 Rationale. 18
6.2 Required properties . 20
6.3 Media-dependent implementations . 20
6.3.1 IEEE 802 integration service . 20
7 IPv6/GeoNetworking interface service specification . 20
8 Encapsulation characteristics . 21
8.1 Maximum transmission unit . 21
8.2 Packet delivery . 21
8.2.1 Outbound traffic . 21
8.2.2 Inbound traffic . 22
8.3 Frame format . 24
9 IPv6 multicast and anycast support . 24
9.1 Overview . 24
9.2 IPv6 multicast support . 25
9.2.1 IPv6 link-local multicast . 25
9.2.2 IPv6 wider-scope multicast . 25
9.2.3 Geocasting of IPv6 multicast traffic . 26
9.3 IPv6 anycast support . 26
9.4 Geographic IPv6 anycast support . 26
10 IPv6 neighbor discovery support . 27
10.1 On-link determination . 27
10.2 Address configuration . 27
10.2.1 Stateless address autoconfiguration . 27
10.2.2 Stateful address configuration. 28
10.2.3 Manual address configuration . 28
ETSI
4 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
10.3 Address resolution . 28
10.3.1 Non-ND-based address resolution . 28
10.3.2 ND-based address resolution . 29
10.4 Neighbor unreachability detection . 29
10.5 Protocol constants. 29
11 Support for pseudonym change . 30
11.1 Rationale. 30
11.2 Required operations . 30
Annex A (normative): ASN.1 encoding of the GN6ASL MIB . 31
A.1 Modules . 31
A.1.1 ITSGN6ASL-MIB . 31
Annex B (normative): MIB attributes . 35
B.1 ITSGN6ASL-MIB attributes values . 35
Annex C (informative): IPv6/GeoNetworking data SAP . 36
C.1 Basic data SAP (GN6_SAP) . 36
C.1.1 Overview . 36
C.1.2 Service primitives . 36
C.1.2.1 GN6-UNITDATA.request . 36
C.1.2.1.1 Semantics . 36
C.1.2.1.2 When generated . 36
C.1.2.1.3 Effect on receipt . 36
C.1.2.2 GN6-UNITDATA.indication . 37
C.1.2.2.1 Semantics . 37
C.1.2.2.2 When generated . 37
C.1.2.2.3 Effect on receipt . 37
C.2 Experimental extended data SAP (EGN6_SAP) . 37
C.2.1 Overview . 37
C.2.2 Service primitives . 38
C.2.2.1 EGN6-UNITDATA.request . 38
C.2.2.1.1 Semantics . 38
C.2.2.1.2 When generated . 38
C.2.2.1.3 Effect on receipt . 38
C.2.2.2 EGN6-UNITDATA.indication . 39
C.2.2.2.1 Semantics . 39
C.2.2.2.2 When generated . 39
C.2.2.2.3 Effect on receipt . 39
Annex D (informative): Geographic IPv6 multicast support (experimental) . 40
D.1 Overview . 40
D.2 Pre-defined geographical IPv6 multicast groups . 40
D.3 Other studied mechanisms. 40
Annex E (informative): Implementation examples . 42
E.1 Virtual links and interfaces . 42
E.2 Packet delivery with Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 42
E.2.1 Outbound traffic . 42
E.2.2 Inbound traffic . 43
E.3 GeoNet project implementations results . 43
Annex F (informative): Support for Network Mobility Basic Support . 44
F.1 Purpose of this annex . 44
ETSI
5 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
F.2 Mode of operation via GN6ASL . . 44
F.3 Sub-optimal routing issues . 44
Annex G (informative): Security and privacy considerations . 45
G.1 Recommendations for security mechanisms . 45
G.2 Recommendations for privacy-protecting deployment . 45
Annex H (informative): Bibliography . 46
History . 47
ETSI
6 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS).
The present document is part 6, sub-part 1 of a multi-part deliverable. Full details of the entire series can be found in
ETSI EN 302 636-1 [3].
National transposition dates
Date of adoption of this EN: 3 February 2014
Date of latest announcement of this EN (doa): 31 May 2014
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 November 2014
Date of withdrawal of any conflicting National Standard (dow): 30 November 2015
Introduction
The ETSI GeoNetworking protocol as defined in ETSI EN 302 636-4-1 [7] and given in ETSI TS 102 636-4-2 [i.23] is
a non-IP network-layer protocol that provides geographic addressing and forwarding and belongs to the position-based
routing protocols category. Applications and facilities specifically designed for GeoNetworking exploit these
functionalities, for example to disseminate warning or generic information messages to geographically scoped areas.
The GeoNetworking protocol satisfies the requirements of several ITS services, whose application domain is limited to
networks that are disconnected from large existing network infrastructures. However, several ITS applications require
the integration of ITS stations with larger networks such as private transport networks or the Internet.
In order to connect networks based on GeoNetworking to networks running the Internet Protocol (IP), which represent
the majority of currently deployed large networks, it is necessary to allow GeoNetworking ITS stations to act like
Internet hosts or routers. The ETSI Technical Committee ITS recognizes IP version 6 as defined in IETF RFC 2460 [8]
as the primary version of IP to be necessarily supported by ITS stations.
The present document introduces a set of mechanisms that allow the GeoNetworking protocol to transport IPv6 packets
without introducing modifications to existing IPv6 protocol implementations. By deploying these mechanisms, the
following two main advantages are achieved:
1) coverage offered by points-of-attachment to the Internet, such as road-side ITS stations, is extended by means
of sub-IP geographic routing; and
2) IPv6 multicast traffic can be geocasted, i.e. addressed and delivered to all ITS stations currently located within
a geographic area.
ETSI
7 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
The present document includes a data SAP that enables an IPv6 protocol entity to send and receive packets over the
GeoNetworking protocol. This SAP is described in the informative annex C. The present document does not include a
management SAP towards the ITS station management entity.
NOTE: In the reminder of the present document, when the sole term "GeoNetworking" is used, it is to be
regarded as the ETSI GeoNetworking protocol combining the media-independent part outlined in ETSI
EN 302 636-4-1 [7] and at least one of the media-dependent parts (such as ETSI TS 102 636-4-2 [i.23]).
It should be noted that the media-dependent extensions do not represent distinct protocol layers.
ETSI
8 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
1 Scope
The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol as defined in
ETSI EN 302 636-4-1 [7] via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6
Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL.
The techniques specified in the present document fulfil the requirements for GeoNetworking and IPv6 integration
described in ETSI EN 302 636-1 [3]. In particular, these techniques allow for the transport of IPv6 packets by ETSI
GeoNetworking protocol given in ETSI EN 302 636-4-1 [7], enabling sub-IP multi-hop delivery of IPv6 packets, e.g. in
a vehicular network. As a result, the connectivity provided by points-of-attachment to IPv6 infrastructure networks is
extended by means of mobile relay nodes. In addition to that, the techniques described in the present document allow
for geocasting of IPv6 multicast packets.
The scope of the GN6ASL is limited to the fulfilment of the requirements for GeoNetworking and IPv6 integration
described in ETSI EN 302 636-1 [3], clause 5.9, by enabling an ITS station including a GeoAdhoc router as given in
ETSI EN 302 636-4-1 [7] running the GeoNetworking protocol and an IPv6-compliant protocol layer to:
• exchange IPv6 packets with other ITS stations;
• acquire globally routable IPv6 unicast addresses and communicate with an arbitrary IPv6 host located in the
Internet, whenever an ITS station including a GeoAdhoc router and including or connected to an access
router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations;
• perform the operations required by IETF RFC 3963 [14] for a Mobile Router whenever:
a) an ITS mobile router supporting Network Mobility Basic Support (NEMO BS) as defined in IETF
RFC 3963 [14] is present in the ITS station and runs on top of the GN6ASL; and
b) an ITS station including a GeoAdhoc router and including or connected to an access router as defined
in ETSI TS 102 636-3 [5] providing IPv6 connectivity to the Internet is reachable directly or via other
relay ITS stations.
NOTE: The present document adopts the definition of "IPv6-compliant" and "sub-IP multi-hop delivery"
introduced in clause 3.1.
Extending the IPv6 basic standards IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF
RFC 4861 [11] and IETF RFC 4862 [13] to support new features is outside the scope of the present document.
Extensions to NEMO BS as given in IETF RFC 3963 [14] are outside the scope of the present document. Mechanisms
for the dissemination of IPv6 routing information for hosts and routers not directly attaching to the network where
GeoNetworking is used are outside the scope of the present document (e.g. discovery of IPv6 in-vehicle prefixes).
However, the present document aims at providing the underlying support for the dissemination of such routing
information, i.e. IPv6 multicast support for the network where the GeoNetworking protocol is used.
With respect to IPv6 multicast and anycast support, the present document is limited to the support required to enable
distribution of IPv6 multicast and anycast traffic on a shared link. Amendments to specific IPv6 multicast forwarding
mechanisms are out of the scope of the present document. However, the present document aims at not preventing
existing IPv6 multicast forwarding mechanisms from being used in conjunction with the GN6ASL.
In order to facilitate the deployment of ITS systems, the present document aims at maintaining backward compatibility
with pre-existent IPv6-compliant protocol implementations and NEMO BS implementations compliant with IETF
RFC 3963 [14]. A usage example of NEMO BS with the GN6ASL is presented in the informative annex F.
The mechanisms specified in the present document are distinct from but compatible with the IPv6-related functionalities
given in ISO 21210-2010 [i.20], which specifies how IPv6 networking is generally operated in ITS stations. The
techniques described in the present document provide a way to transport IPv6 packets that is fully compatible with the
IPv6 specifications and pre-existing implementations, and hence is compatible with ISO 21210-2010 [i.20].
ETSI
9 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbo0x.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture".
[2] ETSI EN 302 663: "Intelligent Transport Systems (ITS); Access layer specification for Intelligent
Transport Systems operating in the 5 GHz frequency band".
[3] ETSI EN 302 636-1: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 1: Requirements".
[4] ETSI EN 302 636-2: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 2: Scenarios".
[5] ETSI TS 102 636-3: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 3: Network architecture".
[6] ETSI EN 302 931: "Intelligent Transport Systems (ITS); Vehicular Communications;
Geographical Area Definition".
[7] ETSI EN 302 636-4-1: "Intelligent Transport System (ITS); Vehicular communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and
point-to-multipoint communications; Sub-part 1: Media independent functionalities".
[8] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[9] IETF RFC 4291: "IP Version 6 (IPv6) Addressing Architecture".
[10] IETF RFC 4007: "IPv6 Scoped Address Architecture".
[11] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[12] IETF RFC 5942: "IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes".
[13] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[14] IETF RFC 3963: "Network Mobility (NEMO) Basic Support Protocol".
[15] IETF RFC 6724: "Default Address Selection for Internet Protocol version 6 (IPv6)".
[16] IETF RFC 2464: "Transmission of IPv6 Packets over Ethernet Networks".
[17] IETF RFC 5072: "IP Version 6 over PPP".
[18] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
[19] IETF RFC 4601: "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
Specification (Revised)".
[20] IETF RFC 4605: "Internet Group Management Protocol (IGMP) / Multicast Listener Discovery
(MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")".
ETSI
10 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
[21] IETF RFC 3306: "Unicast-Prefix-based IPv6 Multicast Addresses".
[22] IETF RFC 2022: "Support for Multicast over UNI 3.0/3.1 based ATM Networks".
[23] IETF RFC 1042: "Standard for the Transmission of IP Datagrams over IEEE 802 Networks".
[24] IETF RFC 3971: "SEcure Neighbor Discovery (SEND)".
[25] IETF RFC 4293: "Management Information Base for the Internet Protocol (IP)".
[26] IETF RFC 2526: "Reserved IPv6 Subnet Anycast Addresses".
[27] ISO/IEC 8802-2:1998: "Information technology-Telecommunications and information exchange
between systems-Local and metropolitan area networks-Specific requirements-Part 2: Logical link
control".
[28] ISO/IEC 15802-3: "Information Technology-Telecommunications and information exchange
between systems-Local and metropolitan area networks-Common specifications - Part 3: Media
Access Control (MAC) Bridges" (previously known as IEEE Std 802.1D-1998).
[29] IEEE 802.11:2012: "IEEE Standard for Information Technology - Telecommunications and
Information Exchange Between Systems-Local and Metropolitan Area Networks - Specific
Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[30] IEEE 802.1Q:1998: "IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged
Local Area Networks".
[31] IEEE 802.3:2008 "IEEE Standard for Information Technology - Telecommunications and
information exchange between systems-Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
Access Method and Physical Layer Specifications".
[32] IEEE "Guidelines For 64-bit Global Identifier (EUI-64)".
NOTE: Available at http://standards.ieee.org/regauth/oui/tutorials/EUI64.html.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 3753: "Mobility Related Terminology".
[i.2] IETF RFC 4885: "Network Mobility Support Terminology".
[i.3] IETF RFC 6434: "IPv6 Node Requirements".
[i.4] IETF RFC 4903: "Multi-Link Subnet Issues".
[i.5] IETF RFC 4840: "Multiple Encapsulation Methods Considered Harmful".
[i.6] IETF RFC 3316: "Internet Protocol Version 6 (IPv6) for Some Second and Third Generation
Cellular Hosts".
[i.7] IETF RFC 5154: "IP over IEEE 802.16 Problem Statement and Goals".
[i.8] IETF RFC 3549: "Linux Netlink as an IP Services Protocol".
[i.9] IETF RFC 3314: "Recommendations for IPv6 in Third Generation Partnership Project (3GPP)
Standards".
[i.10] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".
[i.11] IETF RFC 2578: "Structure of Management Information Version 2 (SMIv2)".
ETSI
11 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
[i.12] IETF RFC 2579: "Textual Conventions for SMIv2".
[i.13] IETF RFC 2491: "IPv6 over Non-Broadcast Multiple Access (NBMA) networks".
[i.14] IETF RFC 6775: "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs)".
[i.15] ETSI TR 102 893: "Intelligent Transport Systems (ITS); Security; Threat, Vulnerability and Risk
Analysis (TVRA)".
[i.16] ETSI TS 102 731: "Intelligent Transport Systems (ITS); Security; Security Services and
Architecture".
[i.17] ETSI TS 103 097:"Intelligent Transport Systems (ITS); Security; Security header and certificate
formats for ITS G5".
[i.18] ETSI TS 102 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set
of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[i.19] Universal TUN/TAP driver for Linux, Solaris and FreeBSD.
NOTE: Available at http://vtun.sourceforge.net/tun/index.html.
[i.20] ISO 21210-2010: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - IPv6 networking".
[i.21] ETSI TS 123 060: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service
description; Stage 2 (3GPP TS 23.060 Release 9)".
[i.22] ISO/IEC Technical Report 11802-5:1997(E): "Information technology-Telecommunications and
information exchange between systems-Local and metropolitan area networks-Technical reports
and guidelines-Part 5: Medium Access Control (MAC) Bridging of Ethernet V2.0 in Local Area
Networks" (previously known as IEEE Std 802.1H-1997).
[i.23] ETSI TS 102 636-4-2: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-
multipoint communications; Sub-part 2: Media dependent functionalities for ITS-G5A media".
[i.24] ETSI TS 102 723-10: "Intelligent Transport Systems; OSI cross-layer topics; Part 10: Interface
between access layer and network and transport layers".
[i.25] GeoNet D1.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D1.2 v1.1: "Final GeoNet Architecture
Design".
[i.26] GeoNet D2.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D2.2 v1.1: "Specification - Final Release".
[i.27] GeoNet D7.1: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and
routing for vehicular communications - Deliverable D7.1 v1.0: "GeoNet Experimentation Results".
[i.28] NemoROReqDraft: IETF draft-ietf-mext-nemo-ro-automotive-req-02 (July 2009): "Automotive
Industry Requirements for NEMO Route Optimization".
ETSI
12 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI EN 302 665 [1], ETSI
TS 102 636-3 [5], IETF RFC 4861 [11], IETF RFC 6434 [i.3], IETF RFC 4885 [i.2] and the following apply:
geographical virtual link: link-local multicast-capable virtual link spanning multiple physical links with
geographically scoped boundaries
GN6 adaptation sub-layer: protocol adaptation sub-layer supporting the transmission of IPv6 packets over the
GeoNetworking protocol
GVL area: geographical area associated with a GVL
IPv6-compliant: compliant with IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF RFC 4861 [11]
and IETF RFC 4862 [13]
IPv6 next hop: IPv6 node resulting from the next-hop determination described in IETF RFC 4861 [11], section 5.2
sub-IP multi-hop delivery: IP packet delivery traversing several ITS stations where the Hop Limit field of the IPv6
header given in IETF RFC 2460 [8] is not decreased
topological virtual link: link-local multicast-capable virtual link spanning multiple physical links with topologically
scoped boundaries
3.2 Symbols
For the purposes of the present document, the following symbols apply:
GEO Size of the largest GeoNetworking header
MAX
GN_SAP GeoNetworking Service Access Point
Maximum transmission unit offered by the protocol layer below GeoNetworking
MTU
AL
MTU Maximum transmission unit offered by GN6ASL to IPv6
GN6
MTU Typical maximum transmission unit associated to the type of a virtual interface
VI
STALE Stale state of an IPv6 Neighbor Cache entry
VL_ID Virtual Link IDentifier
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASL Adaptation Sub-Layer
ASN.1 Abstract Syntax Notation One
CGA Cryptographically Generated Addresses
DGVL Dynamic Geographical Virtual Link
EDCA Enhanced Distributed Channel Access
EIID Extended Interface Identifier
EUI Extended Unique Identifier
GN6 GeoNetworking-IPv6
GN6ASL GeoNetworking-IPv6 Adaptation Sub-Layer
GN6SDU GN6 Service Data Unit
GPRS General Packet Radio Service
GVL Geographical Virtual Link
IANA Internet Assigned Numbers Authority
ID Identifier
IID Interface Identifier
IP Internet Protocol
ITS Intelligent Transport System
ETSI
13 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
LAN Local Area Network
LLC Logical Link Control
MAC Media Access Control
MIB Managed Information Base
MID MAC ID
MTU Maximum Transmission Unit
NA Neighbor Advertisement
ND Neighbor Discovery
NEMO BS NEtwork MObility Basic Support
NH Next Header
NIC Network Interface Controller
NS Neighbor Solicitation
NS/NA Neighbour Solicitation/Neighbour Advertisement
NUD Neighbor Unreachability Detection
OUI Organizationally Unique Identifier
PDCP Packet Data Convergence Protocol
PHY PHYsical
PPP Point-to-Point Protocol
RA Router Advertisement
SAP Service Access Point
SDU Service Data Unit
SEND SEcure Neighbor Discovery
SGVL Static Geographical Virtual Link
SLAAC StateLess Address AutoConfiguration
SMI Structure of Management Information
SNAP SubNetwork Access Protocol
SNMPv2-TC Simple Network Management Protocol version 2 - Textual Conventions
STA STAtion
TAP Terminal Access Point
TBD To Be Defined
TCP Transmission Control Protocol
TSB Topologically Scoped Broadcast
TUN network TUNnel
TVL Topological Virtual Link
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications Systems
VC Virtual Circuit
VLAN Virtual Local Area Network
4 GN6ASL in the ITS station architecture
With respect to the ITS station reference architecture defined in ETSI EN 302 665 [1], the present document only
affects the layer Networking & Transport. As depicted in figure 1, within the layer Networking & Transport, the present
document introduces GN6ASL, an adaptation sub-layer for the transmission of IPv6 packets over the GeoNetworking
protocol. The other protocols depicted in figure 1 (e.g. TCP and UDP) are represented for sake of completeness in order
to represent a typical usage of the present document.
ETSI
14 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
Figure 1: GN6ASL in the ITS station architecture
As depicted in figure 1, the present document builds an adaptation sub-layer (GN6ASL) between the ETSI
GeoNetworking protocol defined in ETSI EN 302 636-4-1 [7] and an IPv6-compliant protocol layer with mobility
extensions. The default IPv6 mobility extension in the ETSI ITS architecture given in ETSI EN 302 665 [1] (as well as
outlined in ISO 21210-2010 [i.20]) is the Network Mobility Basic Support (NEMO BS) protocol defined in IETF
RFC 3963 [14]. The present document enables the usage of NEMO BS over the ETSI GeoNetworking protocol given in
ETSI EN 302 636-4-1 [7].
NOTE: With respect to figure 1, the scope of ISO 21210-2010 [i.20] includes the protocol layer IPv6 + Mobility
Extensions, directly above the adaptation sub-layer specified in the present document.
5 IPv6 link models and interfaces
5.1 Rationale
The Neighbor Discovery (ND) protocol specified in IETF RFC 4861 [11] is a mandatory part of IPv6 stacks that
includes functionalities such as Router and Prefix Discovery as well as Address Resolution and Neighbor
Unreachability Detection. Some of ND's services use link-layer multicast addresses. This implies that the link-layer
protocol is required to support multicast addressing in order to run the ND protocol as described in IETF
RFC 4861 [11]. ND adaptations or alternative protocols or mechanisms to implement its services are commonly
introduced for link-layer technologies that do not support multicast addressing (e.g. IETF RFC 2491 [i.13], IETF
RFC 3316 [i.6], IETF RFC 5154 [i.7]).
In addition to link-local multicast support, ND also requires symmetric reachability (defined in IETF RFC 4861 [11]).
GN6ASL is presented to the IPv6 layer as a link-layer protocol which relies on the GeoNetworking protocol specified
in ETSI EN 302 636-4-1 [7]. The GeoNetworking protocol provides both point-to-point and point-to-multipoint
communications, as well as geographically scoped addressing such as GeoAnycast and GeoBroadcast specified in ETSI
EN 302 636-2 [4]. Furthermore, the GeoNetworking protocol specified in ETSI EN 302 636-4-1 [7] provides upper
layers with a sub-IP multi-hop delivery service as required by ETSI EN 302 636-1 [3].
NOTE: "sub-IP multi-hop delivery" is defined in clause 3.1.
The present document introduces three types of virtual link, one providing symmetric reachability by means of stable
geographically scoped boundaries. The other two do not provide symmetric reachablity but can be used when the
dynamic definition of the broadcast domain is required. The combination of these types of virtual link in the same
station allows running the ND protocol including SLAAC as specified in IETF RFC 4862 [13] as well as to distribute
other IPv6 link-local multicast traffic and, at the same time, to reach nodes that are outside specific geographic
boundaries.
ETSI
15 ETSI EN 302 636-6-1 V1.2.1 (2014-05)
EXAMPLE: In 3GPP Release 9, IPv6 is transported directly over PDCP, and optionally via PPP, see ETSI
TS 123 060 [i.21]. In both cases, over PDCP and via PPP, virtual point-to-point links are used.
ETSI TS 123 060 [i.21] uses some ND operations such as the issuing of a Router Solicitation
although, as pointed out in IETF RFC 3314 [i.9], the IETF has not specified a point-to-point
architecture, nor how the standard IPv6 address assignment mechanisms are applicable to IPv6
over point-to-point links. IETF RFC 3314 [i.9] called for the (at that time still existing) IPv6 WG
to carry out these activities but to date no specification exists.
In the following, virtual links are distinguished from virtual interfaces. A virtual interface represents an instance of a
virtual link that is presented to the IPv6 layer in an implementation-specific way.
5.2 Properties of supported IPv6 link models
5.2.1 Geographical virtual links
A Geographical Virtual Link (GVL) is a link-local multicast-capable virtual link spanning multiple physical links with
geographically scoped boundaries. GN6ASL of a GeoAdhoc router shall support GVLs.
Each GVL shall be associated with one single GeoNetworking GEOBROADCAST/GEOANYC
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.RWRNROLKJHRPUHåHQMDIntelligent Transport Systems (ITS) - Vehicular Communications - GeoNetworking - Part 6: Internet Integration - Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and trade35.110OmreževanjeNetworkingICS:Ta slovenski standard je istoveten z:EN 302 636-6-1 Version 1.2.1SIST EN 302 636-6-1 V1.2.1:2014en01-julij-2014SIST EN 302 636-6-1 V1.2.1:2014SLOVENSKI
STANDARD
ETSI EN 302 636-6-1 V1.2.1 (2014-05) Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols
European Standard SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)2
Reference REN/ITS-0030037 Keywords addressing, Autonomic Networking, IPv6, ITS, network, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88
Important notice The present document can be downloaded from: http://www.etsi.org The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2014. All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)3 Contents Intellectual Property Rights . 6 Foreword . 6 Introduction . 6 1 Scope . 8 2 References . 9 2.1 Normative references . 9 2.2 Informative references . 10 3 Definitions, symbols and abbreviations . 12 3.1 Definitions . 12 3.2 Symbols . 12 3.3 Abbreviations . 12 4 GN6ASL in the ITS station architecture . 13 5 IPv6 link models and interfaces . 14 5.1 Rationale. 14 5.2 Properties of supported IPv6 link models . 15 5.2.1 Geographical virtual links . 15 5.2.1.1 Static geographical virtual links . 15 5.2.1.2 Dynamic geographical virtual links . 15 5.2.2 Topological virtual links . 16 5.2.3 Virtual links indexing . 16 5.3 Properties of virtual interfaces . 16 5.3.1 Number and types of virtual interfaces . 16 5.3.2 Usage of specific virtual interfaces . 17 5.3.2.1 Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 17 6 Bridging support . 18 6.1 Rationale. 18 6.2 Required properties . 20 6.3 Media-dependent implementations . 20 6.3.1 IEEE 802 integration service . 20 7 IPv6/GeoNetworking interface service speciÞcation . 20 8 Encapsulation characteristics . 21 8.1 Maximum transmission unit . 21 8.2 Packet delivery . 21 8.2.1 Outbound traffic . 21 8.2.2 Inbound traffic . 22 8.3 Frame format . 24 9 IPv6 multicast and anycast support . 24 9.1 Overview . 24 9.2 IPv6 multicast support . 25 9.2.1 IPv6 link-local multicast . 25 9.2.2 IPv6 wider-scope multicast . 25 9.2.3 Geocasting of IPv6 multicast traffic . 26 9.3 IPv6 anycast support . 26 9.4 Geographic IPv6 anycast support . 26 10 IPv6 neighbor discovery support . 27 10.1 On-link determination . 27 10.2 Address configuration . 27 10.2.1 Stateless address autoconfiguration . 27 10.2.2 Stateful address configuration. 28 10.2.3 Manual address configuration . 28 SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)4 10.3 Address resolution . 28 10.3.1 Non-ND-based address resolution . 28 10.3.2 ND-based address resolution . 29 10.4 Neighbor unreachability detection . 29 10.5 Protocol constants. 29 11 Support for pseudonym change . 30 11.1 Rationale. 30 11.2 Required operations . 30 Annex A (normative): ASN.1 encoding of the GN6ASL MIB . 31 A.1 Modules . 31 A.1.1 ITSGN6ASL-MIB . 31 Annex B (normative): MIB attributes . 35 B.1 ITSGN6ASL-MIB attributes values . 35 Annex C (informative): IPv6/GeoNetworking data SAP . 36 C.1 Basic data SAP (GN6_SAP) . 36 C.1.1 Overview . 36 C.1.2 Service primitives . 36 C.1.2.1 GN6-UNITDATA.request . 36 C.1.2.1.1 Semantics . 36 C.1.2.1.2 When generated . 36 C.1.2.1.3 Effect on receipt . 36 C.1.2.2 GN6-UNITDATA.indication . 37 C.1.2.2.1 Semantics . 37 C.1.2.2.2 When generated . 37 C.1.2.2.3 Effect on receipt . 37 C.2 Experimental extended data SAP (EGN6_SAP) . 37 C.2.1 Overview . 37 C.2.2 Service primitives . 38 C.2.2.1 EGN6-UNITDATA.request . 38 C.2.2.1.1 Semantics . 38 C.2.2.1.2 When generated . 38 C.2.2.1.3 Effect on receipt . 38 C.2.2.2 EGN6-UNITDATA.indication . 39 C.2.2.2.1 Semantics . 39 C.2.2.2.2 When generated . 39 C.2.2.2.3 Effect on receipt . 39 Annex D (informative): Geographic IPv6 multicast support (experimental) . 40 D.1 Overview . 40 D.2 Pre-defined geographical IPv6 multicast groups . 40 D.3 Other studied mechanisms. 40 Annex E (informative): Implementation examples . 42 E.1 Virtual links and interfaces . 42 E.2 Packet delivery with Ethernet V2.0/IEEE 802.3 LAN virtual interfaces . 42 E.2.1 Outbound traffic . 42 E.2.2 Inbound traffic . 43 E.3 GeoNet project implementations results . 43 Annex F (informative): Support for Network Mobility Basic Support . 44 F.1 Purpose of this annex . 44 SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)5 F.2 Mode of operation via GN6ASL . 44 F.3 Sub-optimal routing issues . 44 Annex G (informative): Security and privacy considerations . 45 G.1 Recommendations for security mechanisms . 45 G.2 Recommendations for privacy-protecting deployment . 45 Annex H (informative): Bibliography . 46 History . 47
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). The present document is part 6, sub-part 1 of a multi-part deliverable. Full details of the entire series can be found in ETSI EN 302 636-1 [3].
National transposition dates Date of adoption of this EN: 3 February 2014 Date of latest announcement of this EN (doa): 31 May 2014 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 November 2014 Date of withdrawal of any conflicting National Standard (dow): 30 November 2015
Introduction The ETSI GeoNetworking protocol as defined in ETSI EN 302 636-4-1 [7] and given in ETSI TS 102 636-4-2 [i.23] is a non-IP network-layer protocol that provides geographic addressing and forwarding and belongs to the position-based routing protocols category. Applications and facilities specifically designed for GeoNetworking exploit these functionalities, for example to disseminate warning or generic information messages to geographically scoped areas. The GeoNetworking protocol satisfies the requirements of several ITS services, whose application domain is limited to networks that are disconnected from large existing network infrastructures. However, several ITS applications require the integration of ITS stations with larger networks such as private transport networks or the Internet. In order to connect networks based on GeoNetworking to networks running the Internet Protocol (IP), which represent the majority of currently deployed large networks, it is necessary to allow GeoNetworking ITS stations to act like Internet hosts or routers. The ETSI Technical Committee ITS recognizes IP version 6 as defined in IETF RFC 2460 [8] as the primary version of IP to be necessarily supported by ITS stations. The present document introduces a set of mechanisms that allow the GeoNetworking protocol to transport IPv6 packets without introducing modifications to existing IPv6 protocol implementations. By deploying these mechanisms, the following two main advantages are achieved: 1) coverage offered by points-of-attachment to the Internet, such as road-side ITS stations, is extended by means of sub-IP geographic routing; and 2) IPv6 multicast traffic can be geocasted, i.e. addressed and delivered to all ITS stations currently located within a geographic area. SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)7 The present document includes a data SAP that enables an IPv6 protocol entity to send and receive packets over the GeoNetworking protocol. This SAP is described in the informative annex C. The present document does not include a management SAP towards the ITS station management entity. NOTE: In the reminder of the present document, when the sole term "GeoNetworking" is used, it is to be regarded as the ETSI GeoNetworking protocol combining the media-independent part outlined in ETSI EN 302 636-4-1 [7] and at least one of the media-dependent parts (such as ETSI TS 102 636-4-2 [i.23]). It should be noted that the media-dependent extensions do not represent distinct protocol layers. SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)8 1 Scope The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol as defined in ETSI EN 302 636-4-1 [7] via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL. The techniques specified in the present document fulfil the requirements for GeoNetworking and IPv6 integration described in ETSI EN 302 636-1 [3]. In particular, these techniques allow for the transport of IPv6 packets by ETSI GeoNetworking protocol given in ETSI EN 302 636-4-1 [7], enabling sub-IP multi-hop delivery of IPv6 packets, e.g. in a vehicular network. As a result, the connectivity provided by points-of-attachment to IPv6 infrastructure networks is extended by means of mobile relay nodes. In addition to that, the techniques described in the present document allow for geocasting of IPv6 multicast packets. The scope of the GN6ASL is limited to the fulfilment of the requirements for GeoNetworking and IPv6 integration described in ETSI EN 302 636-1 [3], clause 5.9, by enabling an ITS station including a GeoAdhoc router as given in ETSI EN 302 636-4-1 [7] running the GeoNetworking protocol and an IPv6-compliant protocol layer to:
• exchange IPv6 packets with other ITS stations; • acquire globally routable IPv6 unicast addresses and communicate with an arbitrary IPv6 host located in the Internet, whenever an ITS station including a GeoAdhoc router and including or connected to an access router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations; • perform the operations required by IETF RFC 3963 [14] for a Mobile Router whenever:
a) an ITS mobile router supporting Network Mobility Basic Support (NEMO BS) as defined in IETF RFC 3963 [14] is present in the ITS station and runs on top of the GN6ASL; and
b) an ITS station including a GeoAdhoc router and including or connected to an access router as defined in ETSI TS 102 636-3 [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations.
NOTE: The present document adopts the definition of "IPv6-compliant" and "sub-IP multi-hop delivery" introduced in clause 3.1. Extending the IPv6 basic standards IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF RFC 4861 [11] and IETF RFC 4862 [13] to support new features is outside the scope of the present document. Extensions to NEMO BS as given in IETF RFC 3963 [14] are outside the scope of the present document. Mechanisms for the dissemination of IPv6 routing information for hosts and routers not directly attaching to the network where GeoNetworking is used are outside the scope of the present document (e.g. discovery of IPv6 in-vehicle prefixes). However, the present document aims at providing the underlying support for the dissemination of such routing information, i.e. IPv6 multicast support for the network where the GeoNetworking protocol is used. With respect to IPv6 multicast and anycast support, the present document is limited to the support required to enable distribution of IPv6 multicast and anycast traffic on a shared link. Amendments to specific IPv6 multicast forwarding mechanisms are out of the scope of the present document. However, the present document aims at not preventing existing IPv6 multicast forwarding mechanisms from being used in conjunction with the GN6ASL. In order to facilitate the deployment of ITS systems, the present document aims at maintaining backward compatibility with pre-existent IPv6-compliant protocol implementations and NEMO BS implementations compliant with IETF RFC 3963 [14]. A usage example of NEMO BS with the GN6ASL is presented in the informative annex F. The mechanisms specified in the present document are distinct from but compatible with the IPv6-related functionalities given in ISO 21210-2010 [i.20], which specifies how IPv6 networking is generally operated in ITS stations. The techniques described in the present document provide a way to transport IPv6 packets that is fully compatible with the IPv6 specifications and pre-existing implementations, and hence is compatible with ISO 21210-2010 [i.20]. SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)9 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbo0x.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture". [2] ETSI EN 302 663: "Intelligent Transport Systems (ITS); Access layer specification for Intelligent Transport Systems operating in the 5 GHz frequency band". [3] ETSI EN 302 636-1: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 1: Requirements". [4] ETSI EN 302 636-2: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 2: Scenarios". [5] ETSI TS 102 636-3: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 3: Network architecture". [6] ETSI EN 302 931: "Intelligent Transport Systems (ITS); Vehicular Communications; Geographical Area Definition". [7] ETSI EN 302 636-4-1: "Intelligent Transport System (ITS); Vehicular communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and
point-to-multipoint communications; Sub-part 1: Media independent functionalities". [8] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". [9] IETF RFC 4291: "IP Version 6 (IPv6) Addressing Architecture". [10] IETF RFC 4007: "IPv6 Scoped Address Architecture". [11] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)". [12] IETF RFC 5942: "IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes". [13] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". [14] IETF RFC 3963: "Network Mobility (NEMO) Basic Support Protocol". [15] IETF RFC 6724: "Default Address Selection for Internet Protocol version 6 (IPv6)". [16] IETF RFC 2464: "Transmission of IPv6 Packets over Ethernet Networks". [17] IETF RFC 5072: "IP Version 6 over PPP". [18] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". [19] IETF RFC 4601: "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)". [20] IETF RFC 4605: "Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")". SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)10 [21] IETF RFC 3306: "Unicast-Prefix-based IPv6 Multicast Addresses". [22] IETF RFC 2022: "Support for Multicast over UNI 3.0/3.1 based ATM Networks". [23] IETF RFC 1042: "Standard for the Transmission of IP Datagrams over IEEE 802 Networks". [24] IETF RFC 3971: "SEcure Neighbor Discovery (SEND)". [25] IETF RFC 4293: "Management Information Base for the Internet Protocol (IP)". [26] IETF RFC 2526: "Reserved IPv6 Subnet Anycast Addresses". [27] ISO/IEC 8802-2:1998: "Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 2: Logical link control". [28] ISO/IEC 15802-3: "Information Technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Common specifications - Part 3: Media Access Control (MAC) Bridges" (previously known as IEEE Std 802.1D-1998). [29] IEEE 802.11:2012: "IEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks - Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". [30] IEEE 802.1Q:1998: "IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks". [31] IEEE 802.3:2008 "IEEE Standard for Information Technology - Telecommunications and information exchange between systems-Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications". [32] IEEE "Guidelines For 64-bit Global Identifier (EUI-64)". NOTE: Available at http://standards.ieee.org/regauth/oui/tutorials/EUI64.html. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 3753: "Mobility Related Terminology". [i.2] IETF RFC 4885: "Network Mobility Support Terminology". [i.3] IETF RFC 6434: "IPv6 Node Requirements". [i.4] IETF RFC 4903: "Multi-Link Subnet Issues". [i.5] IETF RFC 4840: "Multiple Encapsulation Methods Considered Harmful". [i.6] IETF RFC 3316: "Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts". [i.7] IETF RFC 5154: "IP over IEEE 802.16 Problem Statement and Goals". [i.8] IETF RFC 3549: "Linux Netlink as an IP Services Protocol". [i.9] IETF RFC 3314: "Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards". [i.10] IETF RFC 1661: "The Point-to-Point Protocol (PPP)". [i.11] IETF RFC 2578: "Structure of Management Information Version 2 (SMIv2)". SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)11 [i.12] IETF RFC 2579: "Textual Conventions for SMIv2". [i.13] IETF RFC 2491: "IPv6 over Non-Broadcast Multiple Access (NBMA) networks". [i.14] IETF RFC 6775: "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)". [i.15] ETSI TR 102 893: "Intelligent Transport Systems (ITS); Security; Threat, Vulnerability and Risk Analysis (TVRA)". [i.16] ETSI TS 102 731: "Intelligent Transport Systems (ITS); Security; Security Services and Architecture". [i.17] ETSI TS 103 097:"Intelligent Transport Systems (ITS); Security; Security header and certificate formats for ITS G5". [i.18] ETSI TS 102 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service". [i.19] Universal TUN/TAP driver for Linux, Solaris and FreeBSD. NOTE: Available at http://vtun.sourceforge.net/tun/index.html. [i.20] ISO 21210-2010: "Intelligent Transport Systems - Communications access for land mobiles (CALM) - IPv6 networking". [i.21] ETSI TS 123 060: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service description; Stage 2 (3GPP TS 23.060 Release 9)". [i.22] ISO/IEC Technical Report 11802-5:1997(E): "Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Technical reports and guidelines-Part 5: Medium Access Control (MAC) Bridging of Ethernet V2.0 in Local Area Networks" (previously known as IEEE Std 802.1H-1997). [i.23] ETSI TS 102 636-4-2: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-multipoint communications; Sub-part 2: Media dependent functionalities for ITS-G5A media". [i.24] ETSI TS 102 723-10: "Intelligent Transport Systems; OSI cross-layer topics; Part 10: Interface between access layer and network and transport layers". [i.25] GeoNet D1.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and routing for vehicular communications - Deliverable D1.2 v1.1: "Final GeoNet Architecture Design". [i.26] GeoNet D2.2: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and routing for vehicular communications - Deliverable D2.2 v1.1: "Specification - Final Release".
[i.27] GeoNet D7.1: FP7 STREP N 216269 European Project GeoNet - Geographic addressing and routing for vehicular communications - Deliverable D7.1 v1.0: "GeoNet Experimentation Results". [i.28] NemoROReqDraft: IETF draft-ietf-mext-nemo-ro-automotive-req-02 (July 2009): "Automotive Industry Requirements for NEMO Route Optimization". SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)12 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI EN 302 665 [1], ETSI TS 102 636-3 [5], IETF RFC 4861 [11], IETF RFC 6434 [i.3], IETF RFC 4885 [i.2] and the following apply: geographical virtual link: link-local multicast-capable virtual link spanning multiple physical links with geographically scoped boundaries GN6 adaptation sub-layer: protocol adaptation sub-layer supporting the transmission of IPv6 packets over the GeoNetworking protocol GVL area: geographical area associated with a GVL IPv6-compliant: compliant with IETF RFC 2460 [8], IETF RFC 4291 [9], IETF RFC 4007 [10], IETF RFC 4861 [11] and IETF RFC 4862 [13] IPv6 next hop: IPv6 node resulting from the next-hop determination described in IETF RFC 4861 [11], section 5.2 sub-IP multi-hop delivery: IP packet delivery traversing several ITS stations where the Hop Limit field of the IPv6 header given in IETF RFC 2460 [8] is not decreased topological virtual link: link-local multicast-capable virtual link spanning multiple physical links with topologically scoped boundaries 3.2 Symbols For the purposes of the present document, the following symbols apply: GEOMAX Size of the largest GeoNetworking header GN_SAP GeoNetworking Service Access Point MTUAL Maximum transmission unit offered by the protocol layer below GeoNetworking MTUGN6 Maximum transmission unit offered by GN6ASL to IPv6 MTUVI Typical maximum transmission unit associated to the type of a virtual interface STALE Stale state of an IPv6 Neighbor Cache entry VL_ID Virtual Link IDentifier 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: ASL Adaptation Sub-Layer ASN.1 Abstract Syntax Notation One CGA Cryptographically Generated Addresses DGVL Dynamic Geographical Virtual Link EDCA Enhanced Distributed Channel Access EIID Extended Interface Identifier EUI Extended Unique Identifier GN6 GeoNetworking-IPv6 GN6ASL GeoNetworking-IPv6 Adaptation Sub-Layer GN6SDU GN6 Service Data Unit GPRS General Packet Radio Service GVL Geographical Virtual Link IANA Internet Assigned Numbers Authority ID Identifier IID Interface Identifier IP Internet Protocol ITS Intelligent Transport System SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)13 LAN Local Area Network LLC Logical Link Control MAC Media Access Control MIB Managed Information Base MID MAC ID MTU Maximum Transmission Unit NA Neighbor Advertisement ND Neighbor Discovery NEMO BS NEtwork MObility Basic Support NH Next Header NIC Network Interface Controller NS Neighbor Solicitation NS/NA Neighbour Solicitation/Neighbour Advertisement NUD Neighbor Unreachability Detection OUI Organizationally Unique Identifier PDCP Packet Data Convergence Protocol PHY PHYsical PPP Point-to-Point Protocol RA Router Advertisement SAP Service Access Point SDU Service Data Unit SEND SEcure Neighbor Discovery SGVL Static Geographical Virtual Link SLAAC StateLess Address AutoConfiguration SMI Structure of Management Information SNAP SubNetwork Access Protocol SNMPv2-TC Simple Network Management Protocol version 2 - Textual Conventions STA STAtion TAP Terminal Access Point TBD To Be Defined TCP Transmission Control Protocol TSB Topologically Scoped Broadcast TUN network TUNnel TVL Topological Virtual Link UDP User Datagram Protocol UMTS Universal Mobile Telecommunications Systems VC Virtual Circuit VLAN Virtual Local Area Network 4 GN6ASL in the ITS station architecture With respect to the ITS station reference architecture defined in ETSI EN 302 665 [1], the present document only affects the layer Networking & Transport. As depicted in figure 1, within the layer Networking & Transport, the present document introduces GN6ASL, an adaptation sub-layer for the transmission of IPv6 packets over the GeoNetworking protocol. The other protocols depicted in figure 1 (e.g. TCP and UDP) are represented for sake of completeness in order to represent a typical usage of the present document. SIST EN 302 636-6-1 V1.2.1:2014
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)14
Figure 1: GN6ASL in the ITS station architecture As depicted in figure 1, the present document builds an adaptation sub-layer (GN6ASL) between the ETSI GeoNetworking protocol defined in ETSI EN 302 636-4-1 [7] and an IPv6-compliant protocol layer with mobility extensions. The default IPv6 mobility extension in the ETSI ITS architecture given in ETSI EN 302 665 [1] (as well as outlined in ISO 21210-2010 [i.20]) is the Network Mobility Basic Support (NEMO BS) protocol defined in IETF RFC 3963 [14]. The present document enables the usage of NEMO BS over the ETSI GeoNetworking protocol given in ETSI EN 302 636-4-1 [7]. NOTE: With respect to figure 1, the scope of ISO 21210-2010 [i.20] includes the protocol layer IPv6 + Mobility Extensions, directly above the adaptation sub-layer specified in the present document. 5 IPv6 link models and interfaces 5.1 Rationale The Neighbor Discovery (ND) protocol specified in IETF RFC 4861 [11] is a mandatory part of IPv6 stacks that includes functionalities such as Router and Prefix Discovery as well as Address Resolution and Neighbor Unreachability Detection. Some of ND's services use link-layer multicast addresses. This implies that the link-layer protocol is required to support multicast addressing in order to run the ND protocol as described in IETF RFC 4861 [11]. ND adaptations or alternative protocols or mechanisms to implement its services are commonly introduced for link-layer technologies that do not support multicast addressing (e.g. IETF RFC 2491 [i.13], IETF RFC 3316 [i.6], IETF RFC 5154 [i.7]). In addition to link-local multicast support, ND also requires symmetric reachability (defined in IETF RFC 4861 [11]). GN6ASL is presented to the IPv6 layer as a link-layer protocol which relies on the GeoNetworking protocol specified in ETSI EN 302 636-4-1 [7]. The GeoNetworking protocol provides both point-to-point and point-to-multipoint communications, as well as geographically scoped addressing such as GeoAnycast and GeoBroadcast specified in ETSI EN 302 636-2 [4]. Furthermore, the GeoNetworking protocol specified in ETSI EN 302 636-4-1 [7] provides upper layers with a sub-IP multi-hop delivery service as required by ETSI EN 302 636-1 [3]. NOTE: "sub-IP multi-hop delivery" is defined in clause 3.1. The present document introduces three types of virtual link, one providing symmetric reachability by means of stable geographically scoped boundaries. The other two do not provide symmetric reachablity but can be used when the dynamic definition of the broadcast domain is required. The combination of these types of virtual link in the same station allows running the ND protocol including SLAAC as specified in IETF RFC 4862 [13] as well as to distribute other IPv6 link-local multicast traffic and, at the same time, to reach nodes that are outside specific geographic boundaries.
ETSI ETSI EN 302 636-6-1 V1.2.1 (2014-05)15 EXAMPLE: In 3GPP Release 9, IPv6 is transported directly over PDCP, and optionally via PPP, see ETSI TS 123 060 [i.21]. In both cases, over PDCP and via PPP, virtual point-to-point links are used. ETSI TS 123 060 [i.21] uses some ND operations such as the issuing of a Router Solicitation although, as pointed out in IETF RFC 3314 [i.9], the IETF has not specified a point-to-point architecture, nor how the standard IPv6 address assignment mechanisms are applicable to IPv6 over point-to-point links. IETF RFC 3314 [i.9] called for the (at that time still existing) IPv6 WG to carry out these activities but to date no specification exists.
In the following, virtual links are distinguished from virtual interfaces. A virtual interface represents an instance of a virtual link that is presented to the IPv6 layer in an implementation-specific way.
5.2 Properties of supported IPv6 link models 5.2.1 Geographical virtual links A Geographical Virtual Link (GVL) is a link-local multicast-capable virtual link spanning multiple physical links with geographically scoped boundaries. GN6ASL of a GeoAdhoc router shall support GVLs. Each GVL shall be associated with one single GeoNetworking GEOBROADCAST/GEOANYCAST area (also called geoarea in ETSI EN 302 636-4-1 [7] and specified in ETSI EN 302 931 [6]) stored in the per-GVL MIB attributes itsGn6aslGvlAreaCenterLatitude itsGn6aslGvlAreaCenterLongitude itsGn6aslGvlAreaDistA itsGn6aslGvlAreaDistB itsGn6aslGvlAr
...












Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...