<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.jiang-v6ops-semantic-prefix" target="https://datatracker.ietf.org/doc/html/draft-jiang-v6ops-semantic-prefix-04">
   <front>
      <title>Analysis of Semantic Embedded IPv6 Address Schemas</title>
      <author initials="S." surname="Jiang" fullname="Sheng Jiang">
         <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author initials="Q." surname="Sun" fullname="Qiong Sun">
         <organization>China Telecom</organization>
      </author>
      <author initials="I." surname="Farrer" fullname="Ian Farrer">
         <organization>Deutsche Telekom AG</organization>
      </author>
      <author initials="Y." surname="Bo" fullname="Yang Bo">
         <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author initials="T." surname="Yang" fullname="Tianle Yang">
         <organization>China Mobile</organization>
      </author>
      <date month="July" day="15" year="2013" />
      <abstract>
	 <t>   This informational document discusses the use of embedded semantics
   within IPv6 address schemas.  Network operators who have large IPv6
   address space may choose to embed some semantics into their IPv6
   addressing by assigning additional significance to specific bits
   within the prefix.  By embedding semantics into IPv6 prefixes, the
   semantics of packets can be easily inspected.  This can simplify the
   packet differentiation process.  However, semantic embedded IPv6
   address schemas have their own operational cost and even potential
   pitfalls.  Some complex semantic embedded IPv6 address schemas may
   also require new technologies in addition to existing Internet
   protocols.

   The document aims to understand the usage of semantic embedded IPv6
   address schemas, and neutrally analyze on the associated advantages,
   drawbacks and technical gaps for more complex address schemas.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-jiang-v6ops-semantic-prefix-04" />
   
</reference>
