<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.8 (Ruby 3.2.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ma-cats-ngid-01" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.20.1 -->
  <front>
    <title abbrev="NGID">The Network Geographic identification in Computing-Aware Traffic Steering</title>
    <seriesInfo name="Internet-Draft" value="draft-ma-cats-ngid-01"/>
    <author fullname="Yuyin Ma">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>myy@ieee.org</email>
      </address>
    </author>
    <author fullname="Tianhao Peng">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>th.peng@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Guoqing Dong">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>22120037@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Qixuan Zhang">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>23120155@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Xiaoshuang Lv">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>20251239@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Guangjing He">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>heguangjing@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Yuanming Sun">
      <organization>China University of Petroleum-Beijing at Karamay(CUPK)</organization>
      <address>
        <email>2021015417@st.cupk.edu.cn</email>
      </address>
    </author>
    <author fullname="Yiyun Zhang">
      <organization>China University of Petroleum-Beijing at Karamay(CUPK)</organization>
      <address>
        <email>2021015367@st.cupk.edu.cn</email>
      </address>
    </author>
    <author fullname="Jiali Chen">
      <organization>China University of Petroleum-Beijing at Karamay(CUPK)</organization>
      <address>
        <email>2021015433@st.cupk.edu.cn</email>
      </address>
    </author>
    <author fullname="Qihao Si">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>21211129@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Haocheng Lang">
      <organization>Beijing Jiaotong University</organization>
      <address>
        <email>22211145@bjtu.edu.cn</email>
      </address>
    </author>
    <author fullname="Xiuling Wang">
      <organization>Alibaba Cloud Computing Co. Ltd.</organization>
      <address>
        <email>wangxiuling.wxl@alibaba-inc.com</email>
      </address>
    </author>
    <date year="2024" month="April" day="14"/>
    <area>Routing area</area>
    <workgroup>cats</workgroup>
    <keyword>Collaborative Networking</keyword>
    <abstract>
      <?line 73?>

<t>This document proposes a novel network address encoding scheme, called Network Geoidentifier (NGID), which aims to improve the efficiency and accuracy of network device management by directly embedding geolocation information (latitude and longitude) into IPv6 and IPv4 addresses.</t>
      <t>This approach provides a native support for the geolocation of network devices and is expected to have a significant impact on the future of network management and service positioning.</t>
    </abstract>
  </front>
  <middle>
    <?line 80?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>With the rapid growth of Internet devices, the traditional IP address system has shown its limitations in efficiently managing and identifying the physical location of devices.</t>
      <t>The NGID scheme proposed in this draft aims to solve this problem by directly encoding geolocation information in IPv6 and IPv4 addresses, so as to improve the management efficiency of network resources and optimize the geolocation of services.</t>
    </section>
    <section anchor="the-definition-of-terms">
      <name>The Definition of Terms</name>
      <t>NGID: Network geographic identification code, a new type of network address coding scheme.</t>
      <t>Latitude: North or south latitude, measured from the equator to the north or south.</t>
      <t>Longitude: East or west longitude, the angle measured from the prime meridian to east or west.</t>
    </section>
    <section anchor="design-of-ngid">
      <name>Design of NGID</name>
      <t>This section describes in detail the encoding scheme for NGID, including its implementation in the IPv6 and IPv4 address schemes.</t>
      <section anchor="bit-ngid">
        <name>8-bit NGID</name>
        <t>1st place: North and south latitude identifiers (0 for north latitude, 1 for south latitude).</t>
        <t>Digits 2-4: Latitude position (binary encoding, can represent the range from 0 to 15, roughly representing latitude information)</t>
        <t>5th place: East and West longitude identification (0 for east longitude, 1 for west longitude).</t>
        <t>Bits 6-8: Longitude position (binary encoded, can represent the interval from 0 to 15, roughly represent longitude information)</t>
      </section>
      <section anchor="bit-ngid-1">
        <name>12-bit NGID</name>
        <t>1st place: North and south latitude identifiers (0 for north latitude, 1 for south latitude).</t>
        <t>Bits 2-6: Latitude position (binary encoded, which can represent a range from 0 to 31, providing better latitude accuracy than an 8-bit scheme)</t>
        <t>7th place: East and West longitude identification (0 for east longitude, 1 for west longitude).</t>
        <t>Bits 8-12: Longitude position (binary encoded, which can represent a range from 0 to 31, providing better longitude accuracy than the 8-bit scheme)</t>
      </section>
      <section anchor="bit-ngid-2">
        <name>16-bit NGID</name>
        <t>1st place: North and south latitude identifiers (0 for north latitude, 1 for south latitude).</t>
        <t>Digits 2-8: Latitude position (binary encoded to represent the range from 0 to 127, which significantly improves the accuracy of latitude representation)</t>
        <t>9th place: East and West longitude identification (0 represents east longitude, 1 represents west longitude).</t>
        <t>Digits 10-16: Longitude position (binary encoded to represent the range from 0 to 127, significantly improving the accuracy of longitude representation)</t>
      </section>
      <section anchor="bit-ngid-3">
        <name>24-bit NGID</name>
        <t>1st place: North and south latitude identifiers (0 for north latitude, 1 for south latitude).</t>
        <t>Digits 2-12: Latitude position (can represent latitude information from 0 to 4095 with an accuracy of 90/4095 degrees)</t>
        <t>13th place: East and West longitude identification (0 for east longitude, 1 for west longitude).</t>
        <t>Digits 14-24: Longitude position (can represent longitude information from 0 to 4095 with an accuracy of 180/4095 degrees)</t>
      </section>
      <section anchor="bit-ngid-4">
        <name>32-bit NGID</name>
        <t>1st place: North and south latitude identifiers (0 for north latitude, 1 for south latitude).</t>
        <t>Digits 2-16: Latitude position (can represent latitude information from 0 to 32767 with an accuracy of 90/32767 degrees)</t>
        <t>17th place: East and West longitude identification (0 for east longitude, 1 for west longitude).</t>
        <t>Digits 18-32: Longitude position (can represent longitude information from 0 to 32767 with an accuracy of 180/32767 degrees)</t>
      </section>
      <section anchor="bit-ngid-expand-altitudeoptional">
        <name>8-bit NGID Expand Altitude(Optional)</name>
        <t>The first digit is used to indicate the positive or negative altitude (0 represents a negative value, 1 represents a positive value).</t>
        <t>The 2nd to 8th digits are used to indicate the magnitude of altitude.</t>
        <t>If the altitude is negative, set the first digit to 0; If positive, set to 1.</t>
        <t>Divide the absolute value of altitude by 20 meters (new step value), then convert the result to binary form and store it in bits 2-8.</t>
      </section>
    </section>
    <section anchor="encoding-and-decoding-process">
      <name>Encoding and decoding process</name>
      <section anchor="ngid-encoding-steps">
        <name>NGID encoding steps</name>
        <t>Determine latitude and longitude: Get the actual latitude and longitude information of the device.</t>
        <t>Convert to Binary: Converts latitude and longitude values to binary format.</t>
        <t>The latitude is from 0 to 90 degrees from north to south, and the longitude from 0 to 180 degrees from east to west.</t>
        <t>Set the north-south latitude marker: set the first digit to 0 if it is north latitude, and set it to 1 if it is south latitude.</t>
        <t>Set Latitude Position: Padding the binary value of latitude to bits 2-16.</t>
        <t>Set the east-west longitude marker: set the 17th bit to 0 if it is east longitude, and set it to 1 if it is west longitude.</t>
        <t>Set longitude position: Padding the binary value of longitude to bits 18-32.</t>
        <t>Combined NGID: Combines the above binary bits into a 32-bit NGID.</t>
        <t>The geographical location is N 37.7749° and the longitude is W 122.4194°
North and South Latitude Identification: Since the latitude is north latitude (N), the first digit is set to 0.</t>
        <t>Latitude position: The latitude range is 0° to 90°.This range needs to be mapped into 15 bits.</t>
        <t>To simplify the process, the latitude value can be multiplied by a factor that allows it to be represented between 0 and 32767 (2^15 - 1).</t>
        <t>Specifically, multiply by (2^15 - 1)/90.</t>
        <t>For 37.7749°, the corresponding coded value is (37.7749 * (32767 / 90)).</t>
        <t>East-West Longitude Mark: Because the longitude is West Longitude (W), the 17th position is set to 1.</t>
        <t>Longitude position: Longitude ranges from 0° to 180°.</t>
        <t>Similar to latitude, this range needs to be mapped into 15 bits.</t>
        <t>Multiply by the factor (2^15 - 1)/180.</t>
        <t>For 122.4194°, the corresponding coded value is (122.4194 * (32767/180)).</t>
      </section>
      <section anchor="ngid-decoding-steps">
        <name>NGID decoding steps</name>
        <t>Extract the north-south latitude marker: Check the first position to determine whether it is north or south.</t>
        <t>Extract latitude position: Read the binary values of bits 2-16 and convert them to decimal latitude values.</t>
        <t>Extract the East and West meridian markers: Check the 17th position to determine whether it is east or west longitude.</t>
        <t>Extract longitude position: Read the binary value of bits 18-32 and convert it to a decimal longitude value.</t>
        <t>Convert to latitude and longitude: Converts the extracted latitude and longitude values to the actual latitude and longitude information.</t>
        <t>North and South Latitude Markers: Look at the 1st position, if it is 0, it is the north latitude, if it is 1, it is the south latitude.</t>
        <t>Latitude Position: Extracts the values of bits 2-16 and converts them back to the original latitude.</t>
        <t>Assuming the extracted value is X, the original latitude is X / (32767 / 90).</t>
        <t>East-West Longitude Mark: Look at the 17th position, if it is 0, it is east longitude, if it is 1, it is west longitude.</t>
        <t>Longitude Position: Extract the values of the 18th-32nd digits and convert them back to the original longitude.</t>
        <t>Assuming the extracted value is Y, the original longitude is Y / (32767 / 180).</t>
      </section>
    </section>
    <section anchor="implementation-considerations">
      <name>Implementation considerations</name>
      <ul spacing="normal">
        <li>
          <t>The address space remains the same: The NGID design uses only a subset of bits in the IP address to encode geolocation information without changing the total length of the address.</t>
        </li>
      </ul>
      <t>This means that existing network equipment and software can continue to use these addresses without any modifications.</t>
      <ul spacing="normal">
        <li>
          <t>No need to modify existing protocols: Geolocation information is encoded within the existing address structure and does not require the introduction of new protocols or modifications to existing network protocol stacks.</t>
        </li>
        <li>
          <t>Backwards compatible: Newly designed addresses can be recognized and processed by legacy network devices that do not support NGI because these devices ignore specific bits used to encode geolocation.</t>
        </li>
        <li>
          <t>Transparency: For applications and services that do not require geolocation information, the newly designed address is no different from a normal IP address and can be used transparently.</t>
        </li>
        <li>
          <t>Optional: NGIDs are optional features that network administrators can choose to enable in the appropriate network environment without affecting other parts of the network that do not use these features.</t>
        </li>
        <li>
          <t>Simple address resolution: Geo-coding is simple and intuitive, making it easy to implement address resolution in existing systems without the need for complex conversion or mapping processes.</t>
        </li>
        <li>
          <t>Maintain network hierarchy: The design of the NGID takes into account the hierarchy of the existing network, ensuring that the assignment and management of addresses still follows the existing network architecture and policies.</t>
        </li>
      </ul>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="security-risks">
        <name>Security Risks</name>
        <ul spacing="normal">
          <li>
            <t>Location tracking: If an attacker is able to access an NGID, they may track the physical location of the device, causing a breach of the user's privacy.</t>
          </li>
          <li>
            <t>Address mapping: By analyzing NGIDs, an attacker could construct an accurate map of the device's location, which could be used for inappropriate purposes, such as targeted attacks.</t>
          </li>
          <li>
            <t>Traffic analysis: Attackers may use geolocation information to analyze network traffic patterns to infer sensitive information.</t>
          </li>
          <li>
            <t>Identity association: If an NGID is associated with a specific person or organization, an attacker may use this information to build a profile of a user's behavior.</t>
          </li>
        </ul>
      </section>
      <section anchor="response">
        <name>Response</name>
        <ul spacing="normal">
          <li>
            <t>Encryption: Encrypt NGIDs to ensure that only authorized network entities can parse and use this information.</t>
          </li>
          <li>
            <t>Anonymization: Use a mechanism to change the NGID periodically to prevent long-term tracking.</t>
          </li>
          <li>
            <t>Access control: Restrict access to NGIDs to ensure that only trusted network nodes can access this information.</t>
          </li>
          <li>
            <t>Network isolation: Establish logical or physical isolation between network devices that process NGIDs and other network devices to reduce the risk of leakage.</t>
          </li>
          <li>
            <t>Monitoring &amp; Auditing: Implement monitoring systems to detect and record access to NGIDs for tracking and responding to security incidents as they occur.</t>
          </li>
          <li>
            <t>Laws and Policies: Formulate relevant laws and policies to regulate the use of NGID and protect user privacy.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>There is no need for IANA to make new digital resource allocations and related management issues.</t>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>To Do</t>
    </section>
    <section anchor="references">
      <name>References</name>
      <t>To Do</t>
    </section>
    <section anchor="author-information">
      <name>Author Information</name>
      <t>To Do</t>
    </section>
  </middle>
  <back>






  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8Va23IbNxJ9n69A2VW78hapiJRs2dwXy5c43thex3LKyT5s
FTgDkljNDCbAjGj6q/IN+bI93QDmwoslrzeJq1wiOZi+9+lGA+PxOKl1nauZ
eL9S4o2q18ZeiRfKLK2sVjoVOlNlrRc6lbU2pdCleGqKqql1uRxfrKVV4r2V
CzwXl7VSFj8ncj636nom3rx4+SzBe2pp7GaGVxcmSTKTlrIAvwyv1eNCjrHC
jculzsYnk8Q180I7B1b1psKql8/ff5uUTTFXdpZkoDVLUlM6VbrGzURtG5WA
02kCQeRMvDMsmKBvCWmytKapZoJYJFdqg5+yWSLG0CHP5dxYKHXdqk2yJ4ls
6pWxtCoR+Ldo8twLfOfnZgP1X8s7/MDYpSz1JzbLTDxR+j/E+R9amtrgw48l
KFun6w2vVoXUOWgUm81jrZQ6xut39vB4r2W5kka8VeXya/jUq+MKJB7P/1M3
xyprjtNyH7sXjfmFyD0zX8duOp1MT05Oz2/i94P+2MhS/Gslv5LfKfhN7t+/
id9PoONWYLkUr66/iuHJ9P5kevroZoOCF1P8Tn0Nv5VaRko3sfwZCwuiedmU
+1g+XelS9vgIs0B41dbkqinGUSBZi++llYXcHD398e3397a1n8DcZ5Pzx64+
Tpvq6nPy6E3zGRf//8Q5fXAbcWDpXIOr+r2Nc3p6C2l+0JTdl/qrYnEynUwm
0xtj8TtpUqiN0P/abJsSw7NbZFuTE70PB/hd5Hou51I8zU2TdXUEn47Fqzo7
HjBdg8hHT/B4/TF/LP3LY12mx6kp7iRJaWzBAD5LEiou3bdkPB4LOXe1lWmd
JO9X2gkUnqZALROVNZVxygkpSnOtclGGqiezzCrnhCpTk5FcDuYr1AjlI89V
1q+OsSoqK46ozN0biTWq5UpIXThRG6ELsEFpqVFVFZVHDaobIctMyDRtIBeH
WmSdqWudKlHIUi4VSznfiExbldb5BiaZq4wlWiqTm7YUB5Xx+SjH37rJFHPI
4Uv+dg+LIMzLt9cP+AE+nEU1lTsOlpEVZJUQnkSGZmwZXxldU1XG1gKcWJU+
/x3xHfMAQfWxguCwGHivJMhI4fSy5C4CqsE2cIsACSK5aOoGXUSPWs8KRNAp
y8aB0zQxpoAILi50luUqSe6KlyVyNmtSWpAkH3S9YuJoYnQm0AWs8QNYYJmy
4BMlHvEqhEnGpGUOE7Vx4DauVgU0wMeVWcPitRO5LnTNBnDUDEXfkptYboYL
MoOPkA19Jx7VauOgfi769gtSsCMU90sh5mKQZsSj5vCldqkNL2dyDi48wMp5
DjEHARMj+FC8gOqBoBiBtpA7MdzzSS+ce07D26axMQhMVcNOn9S+oAn+JK3h
OFL8mVroUsfn75UtXJKQNWZtzi0PdqTQFCmKiFVrQT1jX6joyUE+g++rkC2g
j+hGZFhojb5PxDQaiUJJh7jMxMKawqfxL42sKQ8Mfy0HbxLRmHUz8Vy6mh6t
Ff622eiDDbCWqz3kK6sL+t3qDD0gcVE9Kt5YzxTlEWnIvXXIX6c47BFNLrV6
rjgwM1UDR73gQzzjZKb3R1iX5g0/otCGv3N2cRsj9PbeOAmkyId374qH47mu
g0gTyFzlMm1tyyk8MK7o0NOJoxOWx1uzM/+Efx2+dw/cnukliTodn81E9GKL
DOJojmpuu/gn6C4RmhVkptD1kFAulTf7CVl5cn8ksEtYrpA37UoySSdulzj3
kuQ+JAoKsptJvw8DP29HaFCR3dkLBq/iMERIxSek4IPxQyjYUtyvocr2KagJ
466BNDfo2Bd4oCE8Opn+cS594h364EaHkrq+yg6Vljs+PZ2MQjEjR85VDYt0
srYFuEaPCmVC/PqQhv7nf4iHH44n09u5+Gt0bskPlaY42dKavP7gT0jkh7fw
O+l3QxZPz6Oheq0Gwj0UMeext9d6tUq0hGP8P/pf/N9ScXvCoPdwNxqCJSYn
48mD2wTELY2xzwyxGRnYoWW4YwiExPTsTwgJTozdmBhmwD547tng7OTRfbHW
LORA30cn3/CzTC2tUg5qTk5/74SPLj4bT8/2u3hLt33IfBvlJg93tIMTT/9A
NO+cuB/Qv8iJp9PzB+eHvOgf9tz4u+N2dOPD8ekB6P4yNx5Wj/y4rd+g0RLP
P1ak30XuDXj0z8pvYO75vcRCW0ifkcC0I2ucxw1dZqS778u92Gjwyb1q6Xd8
MhDcwjTZrUBr0WyjmuyI8eN7YUszLZntQ2iYeePRxHivNIUEXjFn6B+lAJmX
Cw9ZUS5oE0UByCmPgH11Qfjk7wKvRZHCMuAi+5C2uJ7kHNuopg4i99nSZmp6
gma85gygrQW2glXQjft42niU18oGBFauyZlHwGpyt88sbBkgdE3t9DxUPN/M
i+exL6d1mQpfgNPYHDn2N3u6a98hAn5/RlIVulRi/6Z/Jl4Eq2CX3dCOc++y
QUwab2S/H4V4T6NuRjxhhWYi/OQOkWPbuC0TyDoEQpforpcAj05ifPsfPcjw
/ha4MmIOJFfHpVfkHm69zFmMB2G7dBmMwDTHWwBXSHul7Oxg/Ai9ED5ztnHP
TyRq4RdOuoVDDkGAFgDfBoiYibfSj3KIbbBUG3+tfGzFAKM9XUjF8RCXdlRh
GJzv6LGNcQf1GJIPzPMdrLtBkXZ91IRBkyOrwGKapvH+PnwN7dmcxg2BFr/F
4yvZL2Ahnrp5QH+kAvHfiNPz4/Pzs0e//bonfLDgA9qj6fHZ5NHZb78mXQW8
ZPe1/no5KBQzcYmtskeNfiQPg0McvfHYsI2+AX5OepOHnh0H6eFbObxzAvk5
Q3779Zh3+f5JqVTmk4w8X1U8IeIdHhuMrIPsoZ28XmzCXIHxZDQU3nuKyhUR
AnZpvAFiAD4pFgAOHvhJFNE8N2sXwmTeaxJpsarXCkh4whb09epo+m/IMhYT
KgGXlUrZiHm+GUU2G2LSLfvmEdnlW/BrHedlTY0Fp8qUHGW+9fViwxpHYbH4
Gz4y429gq3vElGr/mOt+V6FfI0lo3p1K1J49MTFcffQh+NG3FLG6d56c9Mc9
PVd2v7G3ItR5VwKw4EsYRRc6lzxH6mCl/hIXv+4ZksPN+6tnU/AKRu2C/TZW
jatbsxIltmqsRm2dCtXo+Ucest8MtU9XKr3qZUdrVqiWtSVtvVJYYgfg25ux
RW75bhq9UzLbwSJHYNQiKYdpr2wXnneqi36V9C8eD1UbNpTtlM4r5/raDWPm
M8qpvUPCvpJ7Imyvlq2SDLIDLX3eyk7LYb0elvpD/URb+rkGeekQNjc2Al/U
g0CUg2j8Opr5lTFXdBrHhu4F0airXyej8KEb0nZp1q6a9FftlO49ZTs4xb9w
Q2w5H1xzSSHhzWAsikHZMwS4XDjXFLGCdmZts/Gn0f5X+Rnwrg98n8W9gdX6
4bnPbNuNwq7JdgK247djry1zsQTYDSBMqecNW4LtrNxvuB7Dmyz387bl+mD/
c990BG/HfIA0HH7TJRPsE6w/6UmSMZfpdvpdYZeJUlhIXYYQ4hPQ9hQn84P6
ho4ZTZlTUXXNnKpHjJl2ut4SpYk/T3gOntrQThGhKlI6W4/q16YmDVW59Edc
dSdnPOArlGQxEQLqo3Y83Y5HJOqXRlfdWZtZ1HyphzoD2ABLG+7hQtl0qjsp
asWR5UYUKAqxWyK+Y/HGcCWjl/nhpuONlqQ2qckdbVUOHFC5dtxFbIK1Wgqt
I2rbpHx+yHsoo6hm1PAMtLIqjsPbk0F/NrTuBCD8HYjOXti2UVwOdohMr94T
fIKlMjpcKiq8PKdLVG/UGs723ofona1Cp2VRPbHN/UTPIHDozXzflWNXi93/
9pkquy0zrFc8jkWMgVrbzDjVrgZf2m+60Hj5WIv77d3wYlXeo+9ARFs60psJ
ahrQdeStRXpnsENpopUPhKvPwXKvRXxxBwAsFspS8HGjRAfythgewjI4eON5
NVph63zD4sfJh79w5icMJvwmFkpSeATBu3NBoIem6wHom7xz0pUxTnkrSfgy
JigfjldW05iizZnyWltTcta0SQBNUo4awzUeItYt5MUX+9brfBdlZG0u+RSu
VZ+OVfPGQypyZRyaL2pFw8KS28MmTDoKeeWP8wjHN+EUNw+H6Ts0+QQ7Rrs/
7u7S2gtOR5SICAryXH0MOO04lyy3p72ZRVDhNVCxxv9W7ZUGkNp0tfEImbWn
mHXEy1peqbjbS1PThMF2+2JcvJ2aI0E3Aa3HwlDhpCPyLaT1Tq5pwtNmJOjk
iA/j9zf7iAtirWvVAUxlcjr65mNPcalScK431B4NasXd3rN32l1x+XgVM4SK
FfloRiMqGvvVBCrUFSJ0KfC8DXzsh3NaSEfXCzb+5cP3CboZDh0MNo6hUsyt
otsd4Tnizv6Vrg3oa8ANO+wiBEZwJzZKdFNF5ptPRICzajQQFR7KuWZ7/O2m
lzVvWYaigFmUsT3L4vdjSlN8oUz3Eq1qLF/RGQHx6FIN/CPtUlGN9zK4CFx8
85RldRrl5CJI6NhalGKHailZmVXsZWcgBzSnWyL+DkQJgBJ039RPN4cN6zjM
CeBoRJ1JdZgWeM9yZJNXw6NQy6gXiPBcQVSfSv2bUkNjR014i7ilwrzRMKSk
BFzo3M8wo4fnaiWvtbF+8/aON31OkdDPy9RuqtCn+c8BOxn+6GKCTyffuvCF
WK5ZHQBCZx3KGpDO+fTYJ6UPsNKUm6K9B/YjrUdXQn2MdrwL45ZGdYAAw2iT
+ckBPa+suo4j9THtp9o88gx8wlDHYk1O2yREpqbI9A9A4bCCiGFX97QrTRZU
i2/v0yneTNEA06DXc/QH81w77CXMkpMTjm0TtV3Yzk32lvqApbGY0WUaLig7
i+kUEH2NN5oFzvDgTckrwJ3HYVNq1DfK4b+Ii4auODHstAWh6BZE8A/71dRj
J7UrNtsxIt8GC+YP69qJAg1vI/jpMuUDF8cZTBhmCCVYuFdy7bV7GzCVO4+i
ySn/rcrVteTzobAqIq9Xe+mXBTiL92FiS8XiUxL0QA4N/sWbix2oRjmyYZLX
1TpeSW0rihK3i7xPgQfjHSceivXbI8jL6d2rNRpblFAoLtKr0qxzlS3piaMJ
3TNDD94p7n5g3O63C8428bKLtvDsvwkQKIarLwAA

-->

</rfc>
