Internet DRAFT - draft-zhang-coordinate-based-ipv6-multicast
draft-zhang-coordinate-based-ipv6-multicast
INTERNET-DRAFT haihong zhang
Intended Status: Standards Track lin luo
Expires: May 26, 2020 H3C Corporation
Qianli Zhang
Tsinghua University
November 23, 2019
Coordinate-Based Dynamic IPv6 Multicast Addresses Allocation
draft-zhang-coordinate-based-ipv6-multicast-00
Abstract
This specification defines an extension to the multicast addressing
architecture of the IP Version 6 protocol. The extension presented
in this document allows for coordinate-based allocation of IPv6
multicast addresses.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
zhang, et al. Expires May 26, 2020 [Page 1]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Specification of Requirements . . . . . . . . . . . . . . . . . 3
3. ND Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 Multicast Address . . . . . . . . . . . . . . . . . . . . . . . 4
5 Address Lifetime . . . . . . . . . . . . . . . . . . . . . . . 6
6 Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
8 Informative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
zhang, et al. Expires May 26, 2020 [Page 2]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
1 Introduction
With the advancement of information technology and the advancement of
geographic information socialization, location information plays an
increasingly important role in social services and applications. This
document provides a way to dynamically allocate multicast addresses
based on geographic location information. Location-based multicasting
can be implemented. Currently, there are two general schemes for
identifying geographical locations, one is latitude and longitude,
the other is residential address, and the residential address is more
readable, but the coding of residential address is relatively poor.
This document uses latitude and longitude to identify location
information, and carry location information into an IPv6 multicast
address.
2 Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. ND Option
In [RFC6225], DHCPv6 adds the GeoLoc Option to carry latitude and
longitude information. You can use this option to obtain the latitude
and longitude information of the server. Currently, the latitude and
longitude information cannot be obtained in the case of stateless
address configuration. This document add options to the Neighbor
Discovery Router Advertisement message. The option is use to carry
sub-option. The GeoLoc Option is carried in the sub-option. The
GeoLoc Option format remains the same with which defined in
[RFC6225].
The definition is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ND_OPTION_Extern(140) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-option-type | suboption-len +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-option +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-option +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-option +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
zhang, et al. Expires May 26, 2020 [Page 3]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_GEOLOCATION(1) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LatUnc | Latitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lat (cont'd) | LongUnc | Longitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Longitude (cont'd) | AType | AltUnc | Altitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude (cont'd) |Ver| Res |Datum|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A detailed explanation of the format is given in [RFC6225].
4 Multicast Address
Section 2.7 of [RFC4291] defines the following operational format of
IPv6 multicast addresses:
| 8 | 4 | 4 | 112 bits |
+-------+----+----+-----------------------------------------------+
|11111111|flags|scop| group ID |
+--------+----+----+----------------------------------------------+
flags is a set of 4 flags:
+-+-+-+-+
|0|0|0|T|
+-+-+-+-+
Unicast-Prefix-based Multicast Address updated by [RFC7371]:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+--------+----------------+----------+
|11111111|ff1 |scop|ff2 |rsvd| plen | network prefix | group ID |
+--------+----+----+----+----+--------+----------------+----------+
zhang, et al. Expires May 10, 2020 [Page 4]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
ff1 (flag field 1) is a set of 4 flags:
+-+-+-+-+
|0|0|P|T|
+-+-+-+-+
Embedding the Address of the RP in the Multicast Address updated
by [RFC7371]:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+----+----------------+----------+
|11111111|ff1 |scop|ff2 |RIID|plen| network prefix | group ID |
+--------+----+----+----+----+----+----------------+----------+
ff1 is a set of four flags:
+-+-+-+-+
|0|R|P|T|
+-+-+-+-+
This document introduces a new format that incorporates geographic
coordinate information in the multicast address:
| 8 | 4 | 4 | 98 | 14 |
+--------+----+----+--------------------------------+---------------+
|11111111|flgs|scop| geographic coordinate |group ID |
+--------+----+----+--------------------------------+---------------+
The geographic coordinate is the value of Latitude, Longitude, and
Altitude, including 34bit longitude, 34bit latitude, and 30bit
height.
flags is a set of 4 flags:
+-+-+-+-+
|G|R|P|T|
+-+-+-+-+
If G= 0 indicates a multicast address that is not assigned
based on geographic coordinate. This indicates a multicast
address as defined in [RFC4291].
If G = 1 indicates a multicast address that is assigned based
on geographic coordinate.
zhang, et al. Expires May 26, 2020 [Page 5]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
If G = 1, T MUST be set to 1, otherwise the setting of the T
bit is defined in [RFC4291].
Group ID is in the range of 1 to 0x3FFF.The Group ID is
configurable.
The geographic coordinate based dynamic multicast function are
configurable. Server can specify whether client should use
stateful(DHCPv6) and/or autonomous (stateless) address configuration.
When the DHCPv6 address allocation mode is adopted, the client sends
the OPTION_GEOLOCATION option through the OPTION_ORO defined in
RFC8415 to request the server to send the location information. After
receiving the location option information of the server, the client
generates an IPv6 multicast address according to the geographic
coordinate information. When the stateless address is automatically
allocated,the Neighbor Discovery Router Advertisement message carries
the location information through the OPTION_GEOLOCATION option
defined in this document.
5 Address Lifetime
The lifetime of a geographic coordinate based multicast address
SHOULD NOT exceed the Valid Lifetime of the delegated address. In
stateless address configuration the lifetime SHOULD NOT exceed the
Valid Lifetime field in the Prefix Information option,corresponding
to the unicast prefix being used, contained in the Neighbor Discovery
Router Advertisement message [RFC4861]. In stateful (DHCPv6) address
configuration the lifetime SHOULD NOT exceed the Valid Lifetime of an
address or delegated prefix[RFC8415].
6 Security Considerations
Since there is no privacy protection for DHCPv6 and ND RA messages,
an eavesdropper who can monitor the link between the server and
requesting client can discover this OPTION_GEOLOCATION.
To minimize the unintended exposure of location information, the MD5-
keyed hash algorithm can be supported.While the MD5 digest is not
correct the message MUST be dropped.
zhang, et al. Expires May 26, 2020 [Page 6]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_LOCATIONMD5(145) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| key-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MD5 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MD5 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MD5 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MD5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7 IANA Considerations
This document does not include an IANA request.
8 Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8415] T. Mrugalski,M. Siodelski, B. Volz,A. Yourtchenko,
M. Richardson,S. Jiang,T. Lemon and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>.
[RFC4291] R. Hinden and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291,
February 2006,
<https://www.rfc-editor.org/info/rfc4291
[RFC6225] J. Polk, M. Linsner, M. Thomson and B. Aboba, Ed,
"Dynamic Host Configuration Protocol Options for
Coordinate-Based Location Configuration Information",
RFC 6225, DOI 10.17487/RFC6225, July 2011,
<https://www.rfc-editor.org/info/rfc6225>.
[RFC4861] T. Narten, E. Nordmark,W. Simpson and H.Soliman,"Neighbor
Discovery for IP Version 6 (IPv6)", RFC 4861, September
2007
zhang, et al. Expires May 26, 2020 [Page 7]
INTERNET DRAFT coordinate-based-dynamic-ipv6-multicasct November 7,2019
[RFC7371] M. Boucadair, S. Venaas,,"Updates to the IPv6 Multicast
Addressing Architecture", RFC 7371,
September 2014
Authors' Addresses
Haihong Zhang
H3c Corporation
Beijing
P.R.China
Email: zhanghaihong.04355@h3c.com
Lin Luo
H3c Corporation
Hangzhou
P.R.China
Email: extrall@h3c.com
Qianli Zhang
Tsinghua University
Beijing
P.R.China
Email: zhang@cernet.edu.cn
zhang, et al. Expires May 10, 2020 [Page 8]
