[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

James Kempf wrote:

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em">Below is a Last Call review from Henrik Petander. Vijay has requested more<br>
time for his review.<br>
<br>
           jak<br>
----------------------------------------------------------------<br>
<br>
1. Protocol issues<br>
==================<br>
<br>
The handling of sequence numbers in MN and RA for resending is not<br>
defined. Should MN increase the sequence number on resend? Should AR<br>
identify a CARD request similar to an old one, except for the sequence<br>
number, as a resend and set a new timer for AR-AR resending? How does<br>
AR identify a "new" request from MN from resends of an old one?<br>
<br>
The timeout values in MN -AR resending and AR-AR resending make AR-AR<br>
resending overlap: If a message is lost between AR and CAR, both MN and<br>
AR will resend it at the same time. Based on the discussion about AR-AR<br>
resending, I understood that its purpose was to decrease the amount<br>
of over-the-air messages, if a message is lost in the fixed<br>
network. Now this does not happen.<br>
<br>
To fix this, change the values for resending, so that MN_AR_CARD_TIMEOUT ><br>
AR_AR_CARD_TIMEOUT * MN_AR_CARD_RETRIES. This should IMO be done by<br>
decreasing the AR_AR timeout and amount of retries to avoid problems<br>
with MN noticing messages lost between MN and AR slowly.<br>
<br>
Should the sequence number be stored in CAR table to enforce ordering<br>
of CARD replies ?<br>
<br>
Now unsolicited CARD replies are to be authenticated with signatures,<br>
which MN can verify with the public key of the AR, that MN has learned<br>
from somewhere. This is very vague. The description of CARD should be<br>
sufficient for two implementations to be interoperable. IMO you should<br>
either remove the whole unsolicited CARD reply functionality, or clarify<br>
the use of signatures so that it will actually work between two<br>
independent implementations.<br>
<br>
L2 id suboption should have address length field which MUST be<br>
used at least with with L2 type = 0x00.<br>
<br>
2. Editorial issues<br>
===================<br>
<br>
4. ...CARD Reply contains one or more L2 ids and IP addresses" Isn't<br>
  this contradictory with the use of context id of L2 IDs from CARD<br>
  Request in CARD reply to avoid including L2 ids? Change this to<br>
  "may contain".<br>
<br>
5.1.1<br>
<br>
The text in 5.1.1 on including suboptions in CARD MN-AR request is<br>
confusing to me. Which suboptions must be present in all messages? Isn't<br>
it valid to send just a MN-AR CARD request to get all CARs and their<br>
capabilities from AR?<br>
<br>
5.1.2 Should maybe have a note that flag combination A= 0 with C=0 is<br>
invalid.<br>
<br>
6.3 Second paragraph is repeated from 4.6. Shouldn't this section<br>
analyze the security, whereas section 4.6 should describe the<br>
implementation of the security mechanisms.<br>
<br>
6.4 CARD Reply DoS: Is this really a relevant threat, since CAR is<br>
 authenticated with IPSec ESP? It seems to require compromise of CAR,<br>
 so IMO this is out of scope.<br>
<br>
7. Protocol constants<br>
<br>
What is the purpose of CARD_RETRANSMISSION_INTERVAL and CARD_MAX_RETRIES?<br>
<br>
<br>
<br>
_______________________________________________<br>
Seamoby mailing list<br>
Seamoby@ietf.org<br>
&amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;&amp;lt;br&amp;gt;
 
&amp;lt;br&amp;gt;
&amp;lt;/blockquote&amp;gt;&amp;lt;pre&amp;gt;


_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
&amp;lt;a  href=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/a&amp;gt;



&amp;lt;/pre&amp;gt;

&amp;lt;!--X-Body-of-Message-End--&amp;gt;
&amp;lt;!--X-MsgBody-End--&amp;gt;
&amp;lt;!--X-Follow-Ups--&amp;gt;
&amp;lt;hr&amp;gt;
&amp;lt;!--X-Follow-Ups-End--&amp;gt;
&amp;lt;!--X-References--&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;References&amp;lt;/strong&amp;gt;:
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;02281&amp;quot; href=&amp;quot;msg02281.html&amp;quot;&amp;gt;[Seamoby] CARD Review from Henrik Petander&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;em&amp;gt;From:&amp;lt;/em&amp;gt; &amp;amp;quot;James Kempf&amp;amp;quot; &amp;amp;lt;kempf@docomolabs-usa.com&amp;amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;
&amp;lt;!--X-References-End--&amp;gt;
&amp;lt;!--X-BotPNI--&amp;gt;
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;Prev by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg02290.html&amp;quot;&amp;gt;Re: Preferences and Requirements Options (was Re: [Seamoby] Proposal to resolve remaining CARD issues)&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg02292.html&amp;quot;&amp;gt;[Seamoby] CARD: handling of sequence numbers&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Previous by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg02325.html&amp;quot;&amp;gt;CARD protocol constants related / was: Re: [Seamoby] CARD Reviewfrom Henrik Petander&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg02282.html&amp;quot;&amp;gt;[Seamoby] Working Group Last Call on draft-ietf-seamoby-ctp-04.txt&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Index(es):
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;mail2.html#02291&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Date&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;thrd2.html#02291&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Thread&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

&amp;lt;!--X-BotPNI-End--&amp;gt;
&amp;lt;!--X-User-Footer--&amp;gt;
&amp;lt;!--X-User-Footer-End--&amp;gt;
&amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;
&lt;/pre&gt;
&lt;!--X-Body-of-Message-End--&gt;
&lt;!--X-MsgBody-End--&gt;
&lt;!--X-Follow-Ups--&gt;
&lt;hr&gt;
&lt;!--X-Follow-Ups-End--&gt;
&lt;!--X-References--&gt;
&lt;!--X-References-End--&gt;
&lt;!--X-BotPNI--&gt;
&lt;ul&gt;
&lt;li&gt;Prev by Date:
&lt;strong&gt;&lt;a href=&quot;msg02288.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by Date:
&lt;strong&gt;&lt;a href=&quot;msg02290.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Previous by thread:
&lt;strong&gt;&lt;a href=&quot;msg02288.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by thread:
&lt;strong&gt;&lt;a href=&quot;msg02290.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Index(es):
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;maillist.html#02289&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#02289&quot;&gt;&lt;strong&gt;Thread&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;!--X-BotPNI-End--&gt;
&lt;!--X-User-Footer--&gt;
&lt;!--X-User-Footer-End--&gt;
&lt;/body&gt;
&lt;/html&gt;
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg02288.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg02290.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg02288.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg02290.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#02289"><strong>Date</strong></a></li>
<li><a href="threads.html#02289"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>