summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--internet-draft-satp.html2
-rw-r--r--internet-draft-satp.txt2
-rw-r--r--internet-draft-satp.xml2
3 files changed, 3 insertions, 3 deletions
diff --git a/internet-draft-satp.html b/internet-draft-satp.html
index 301b19a..db03d1f 100644
--- a/internet-draft-satp.html
+++ b/internet-draft-satp.html
@@ -457,7 +457,7 @@ Header format</h3>
<a name="rfc.section.4.2"></a><h3>4.2.&nbsp;
sender ID</h3>
-<p>The sender ID is a 16bit unsigned integer. It HAS TO be unique for every sender sharing the same anycast address
+<p>The sender ID is a 16 bit unsigned integer. It HAS TO be unique for every sender sharing the same anycast address
</p>
<a name="anchor15"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
diff --git a/internet-draft-satp.txt b/internet-draft-satp.txt
index c59599f..9209ff3 100644
--- a/internet-draft-satp.txt
+++ b/internet-draft-satp.txt
@@ -477,7 +477,7 @@ Internet-Draft secure anycast tunneling protocol (SATP) April 2007
4.2. sender ID
- The sender ID is a 16bit unsigned integer. It HAS TO be unique for
+ The sender ID is a 16 bit unsigned integer. It HAS TO be unique for
every sender sharing the same anycast address
4.3. sequence number
diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml
index cf981e6..01f717c 100644
--- a/internet-draft-satp.xml
+++ b/internet-draft-satp.xml
@@ -200,7 +200,7 @@ Tunneling of IPv6 over IPv4 with RTP payload
<t></t>
</section>
<section title="sender ID">
- <t>The sender ID is a 16bit unsigned integer. It HAS TO be unique for every sender sharing the same anycast address</t>
+ <t>The sender ID is a 16 bit unsigned integer. It HAS TO be unique for every sender sharing the same anycast address</t>
</section>
<section title="sequence number">
<t>The sequence number is a 32 bit unsigned integer in network byte order. It starts with a random value and is increased by 1 for every sent packet. After the maximum value, it starts over from 0. This overrun causes the ROC to be increased.</t>