[rocketmq.wiki] branch master updated: Created RIP 15 RocketMQ IPv6 Support Project (markdown)

[du...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

duhengforever pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 66048cd  Created RIP 15 RocketMQ IPv6 Support Project (markdown)
66048cd is described below

commit 66048cd88a69dc33b219633952695a8b80628b18
Author: Heng Du <du...@gmail.com>
AuthorDate: Mon Sep 16 17:40:26 2019 +0800

    Created RIP 15 RocketMQ IPv6 Support Project (markdown)
---
 RIP-15-RocketMQ-IPv6-Support-Project.md | 34 +++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/RIP-15-RocketMQ-IPv6-Support-Project.md b/RIP-15-RocketMQ-IPv6-Support-Project.md
new file mode 100644
index 0000000..e375570
--- /dev/null
+++ b/RIP-15-RocketMQ-IPv6-Support-Project.md
@@ -0,0 +1,34 @@
+# Status
+Current State: Implemented    
+Authors: fubaoyu,chenyongming    
+Shepherds: duhengforever    
+Mailing List discussion: users@rocketmq.apache.org;dev@rocketmq.apache.org    
+Released: <4.6.0>    
+ 
+
+# Background & Motivation
+## What do we need to do
+RocketMQ does not currently support running in an IPv6 network environment. Therefore, we plan to make certain modifications to RocketMQ so that it can be deployed in both IPv4 and IPv6 network environments.
+
+# Goals
+## What problem is this proposal designed to solve?
+We plan to modify the RocketMQ system flag so that the Broker can choose different stored procedures based on the message IP version. For messages from different IP versions, the client can also decode correctly. The modified version works in both IPv4 and IPv6 network environments and is compatible with previous versions.
+
+## To what degree should we solve the problem?
+(1)Modify system flag;    
+(2)Modify storage process;    
+(3)Modify message encoding and decoding  process.    
+
+# Non-Goals
+## What problem is this proposal NOT designed to solve?
+In this phase, the project will not support transactional message and message trace function. We will improve these functions in our subsequent work.
+
+# Changes
+## Enahncement 1: Sub-project: storage module
+The storage structure of the message contains the IP. The storage module performs different storage processes depending on whether the message is from an IPv4 or IPv6 client.
+
+## Enahncement 2: Sub-project: Message encoding and decoding module
+When it comes to message encoding with IP information, for example, msgID, RocketMQ will call different encoding methods depending on the IP version. At the same time, the client will call different decoding methods for each message according to the system flag when decoding.
+
+## new features
+RocketMQ can be deployed in an IPv6 network environment.