summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOthmar Gsenger <otti@anytun.org>2007-04-13 16:42:55 +0000
committerOthmar Gsenger <otti@anytun.org>2007-04-13 16:42:55 +0000
commit83c016713faa080c518c40c615f531c6d5454aa7 (patch)
tree55d126214b853955fe97175b9321f04244a2e8ac
parentProtocol type (diff)
table fixed
-rw-r--r--draft-gsenger-anycast-relay-00.txt36
-rw-r--r--internet-draft-anytun.xml23
2 files changed, 33 insertions, 26 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
index 8a5a9dd..0d10e86 100644
--- a/draft-gsenger-anycast-relay-00.txt
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -457,24 +457,24 @@ Internet-Draft Anycast stream relaying March 2007
The protocol field defines the payload protocol. ETHER TYPE protocol
numerbers are used. http://www.iana.org/assignments/ethernet-numbers
- Values from 0 to 0000-05DC are not used for DIX ethernet lenght, but
- are reservered for special purposes. As the definition of
- transparent ethernet bridging is very unclear 2 special types are
- added for ethernet frames HEX 0001 Raw Ethernet - both IEEE 802.3 and
- DIX Etherernet without preamble,SFD, PAD and FCS 0002 Raw Ethernet
- with FCS further special types MAY be added in the furture. Most
- important ETHER TYPEs 0800 Internet IP (IPv4) 86DD IPv6
-
-
-
-
-
-
-
-
-
-
-
+ . The values 0000-05DC are not used for DIX ethernet lenght, but are
+ reservered for special purposes. As the definition of transparent
+ ethernet bridging is very unclear 2 special types are added for
+ ethernet frames
+
+ Protocol Types
+
+ HEX
+ 0000 Reserved
+ 0001 Raw Ethernet - both IEEE 802.3 and DIX Etherernet
+ without preamble,SFD, PAD and FCS
+ 0002 Raw Ethernet with FCS
+ 0003-05DC Reserved
+ 05DD and above as in http://www.iana.org/assignments/ethernet-numbers
+ 0800 Internet IP (IPv4)
+ 86DD IPv6
+
+ Figure 6
diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml
index e4679df..07eeae7 100644
--- a/internet-draft-anytun.xml
+++ b/internet-draft-anytun.xml
@@ -183,14 +183,21 @@ client 1 ----------- -> |server 3| -> ----------- client 2
<section title="Header format">
</section>
<section title="Protocol field">
- <t>The protocol field defines the payload protocol. ETHER TYPE protocol numerbers are used. http://www.iana.org/assignments/ethernet-numbers Values from 0 to 0000-05DC are not used for DIX ethernet lenght, but are reservered for special purposes. As the definition of transparent ethernet bridging is very unclear 2 special types are added for ethernet frames<br/>
-HEX<br/>
-0001 Raw Ethernet - both IEEE 802.3 and DIX Etherernet without preamble,SFD, PAD and FCS<br/>
-0002 Raw Ethernet with FCS<br/>
-further special types MAY be added in the furture.<br/>
-<br/>Most important ETHER TYPEs<br/>
-0800 Internet IP (IPv4)<br/>
-86DD IPv6<br/>
+ <t>The protocol field defines the payload protocol. ETHER TYPE protocol numerbers are used. http://www.iana.org/assignments/ethernet-numbers . The values 0000-05DC are not used for DIX ethernet lenght, but are reservered for special purposes. As the definition of transparent ethernet bridging is very unclear 2 special types are added for ethernet frames<br/>
+ <figure anchor="prot_type_table">
+ <preamble>Protocol Types</preamble>
+ <artwork>
+HEX
+0000 Reserved
+0001 Raw Ethernet - both IEEE 802.3 and DIX Etherernet
+ without preamble,SFD, PAD and FCS
+0002 Raw Ethernet with FCS
+0003-05DC Reserved
+05DD and above as in http://www.iana.org/assignments/ethernet-numbers
+0800 Internet IP (IPv4)
+86DD IPv6
+</artwork>
+</figure>
</t>
</section>
</section>