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

[no subject]

</pre>
</blockquote><pre>the above is a repeat. it is previously described in detail in
section 4.


section 4.3.1

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>the MN's current AR
  SHALL extract the capability information from the payload of the
  received message and buffer the received capabilities in its local
  CAR table.

</pre>
</blockquote><pre>s/buffer/store/


section 4.3.2

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>AR-AR CARD Request. The CAR SHALL buffer the received capabilities

</pre>
</blockquote><pre>same as above


section 4.4.1

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>A MN SHALL detect the loss of a
  MN-AR CARD Request or MN-AR CARD Reply Message using a timeout
  mechanism (MN_AR_CARD_TIMEOUT). The MN SHALL start a timer
  (MN_AR_CARD_TIMER) after sending a MN-AR CARD Request message with
  the given sequence number. The MN SHALL stop the timer as soon as
  the reply to the MN-AR CARD Request is received by it. Upon
  expiration of the MN_AR_CARD_TIMER, the MN SHALL declare the
  outstanding message as lost, resends the same message and restart

  the MN_AR_CARD_TIMER.

</pre>
</blockquote><pre>
replace the above by

A MN SHOULD retransmit the CARD Request, if it does not receive a
CARD Reply within MR_AR_CARD_TIMEOUT seconds.


section 4.4.2

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>The MN's current AR MAY detect the loss of an AR-AR CARD
  Request or an AR-AR CARD Reply message using a timeout mechanism
  (AR_AR_CARD_TIMEOUT). The current AR MAY start a timer
  (AR_AR_CARD_TIMER) after sending the AR-AR CARD Request with the
  given sequence number. The current AR should then stop the timer as
  soon as the reply to the AR-AR CARD Request is received by it. Upon
  expiration of the AR_AR_CARD_TIMER, the MN's current AR declares the
  outstanding AR-AR CARD Request as lost and then resends the same
  message to the CAR.

</pre>
</blockquote><pre>
replace the above by

The MN's current AR SHOULD retransmit the CARD Request, if it does
not receive a CARD Reply within AR_AR_CARD_TIMEOUT seconds.

section 4.5

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>To allow MNs and ARs appending the ICMP-option type CARD Request and
  CARD Reply (Section 5.1.2) to the ICMP-type Fast Mobile IPv6
  signaling messages

</pre>
</blockquote><pre>I think this is the first time Fast MIPv6 appears. a reference to
the FMIPv6 draft will be useful.


section 4.6

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre> The MN-AR and AR-AR messages' authenticity MUST be ensured using
  IPsec ESP [10]. It is safe to assume that there will be an

</pre>
</blockquote><pre>
s/it is safe to assume/The CARD protocol assumes/

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>  appropriate SA between a MN and its connected AR, which MAY be used

</pre>
</blockquote><pre>
s/appropriate SA/IPsec Security Association/

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>  The proposed mechanism for authenticating unsolicited and multicast
  MN-AR CARD Reply messages at MNs is the use of digital signatures.
  This assumes that the MN has discovered the respective AR's public
  key before the received unsolicited CARD Reply messages can be
  validated.

</pre>
</blockquote><pre>
this is too vague. why not just say

 This document does not specify a mechanism for securing
 unsolicted multicast MN-AR CARD Reply messages.


section 5.1.1, delete the following. it is already said in a
couple of places in the draft.

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>        Encapsulating Security Payload (ESP) Header:
                       IPSec ESP MUST be used with a non-null
                       integrity protection and origin authentication
                       algorithm and SHOULD be used with a non-null
                       encryption algorithm for protecting the
                       confidentiality of the CARD information.

</pre>
</blockquote><pre>
section 5.1.3.1

</pre>
<blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em"><pre>  L2 type:       Indicates the interface type (optional).

                 If the L2 type indicator is not used, this field MUST
                 be set to 0x00.

                 The following types are initially defined:

                 Technology    |  L2 type
                 --------------+---------
                 IEEE802.11    |   T.B.A.
                 CDMA2000      |   T.B.A.
                 WCDMA         |   T.B.A.

</pre>
</blockquote><pre>
I think IANA does not have assign the L2 type. it can be done in
this draft itself. I know I was the one who raised this issue
earlier. but now I realise IANA's role is not needed for the L2
type. my mistake.


Vijay


_______________________________________________
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;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;Follow-Ups&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;02300&amp;quot; href=&amp;quot;msg02300.html&amp;quot;&amp;gt;Re: [Seamoby] CARD review - Minor issues&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; Marco Liebsch &amp;amp;lt;Marco.Liebsch@ccrle.nec.de&amp;amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;02288&amp;quot; href=&amp;quot;msg02288.html&amp;quot;&amp;gt;Re: [Seamoby] CARD review - Minor issues&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; Vijay Devarapalli &amp;amp;lt;vijayd@iprg.nokia.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-Follow-Ups-End--&amp;gt;
&amp;lt;!--X-References--&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;msg02286.html&amp;quot;&amp;gt;Re: [Seamoby] CARD Review from Henrik Petander&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;msg02288.html&amp;quot;&amp;gt;Re: [Seamoby] CARD review - Minor issues&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;msg02283.html&amp;quot;&amp;gt;[Seamoby] I-D ACTION: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;Next by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg02288.html&amp;quot;&amp;gt;Re: [Seamoby] CARD review - Minor issues&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;mail3.html#02287&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#02287&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;msg02284.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;msg02286.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;msg02284.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;msg02286.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#02285&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#02285&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="msg02284.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg02286.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg02284.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg02286.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#02285"><strong>Date</strong></a></li>
<li><a href="threads.html#02285"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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