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

[no subject]

On Thu, 21 Aug 2003, James Kempf wrote:

> Jukka,
> 
> For CARD, the problem is that if the FMIP prehandover information signaling is
> not specified as the vehicle, CARD must specify a separate protocol that
> performs a substantially identical function. This is in direct violation of RFC
> 1958 Principle 3.2 (and I quote):
> 
>        3.2 If there are several ways of doing the same thing, choose one.
>    If a previous design, in the Internet context or elsewhere, has
>    successfully solved the same problem, choose the same solution unless
>    there is a good technical reason not to.  Duplication of the same
>    protocol functionality should be avoided as far as possible, without
>    of course using this argument to reject improvements.
> 
> Using the FMIP prehandover signaling does not mean that FMIP must be used for
> handover. One could use GPRS or any other protocol for that purpose.
> 
> With respect to CT, its a bit murkier, since the proposal is to directly use the
> FMIP handover signaling (as opposed to the prehandover signaling) as transport
> for the context and for the signaling from the Mobile Node to trigger the
> context transfer.
> One way we could finesse this is to define CT as an extension mechanism, then
> define in an appendix how it would apply to FMIP. This would avoid the problem
> of tying the base design to FMIP, while still ensuring it would work well with
> FMIP.
> 
>             jak
> 
> 
> ----- Original Message -----
> From: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <seamoby@ietf.org>
> Sent: Friday, March 21, 2003 11:27 AM
> Subject: Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work
> 
> 
> >
> > Hi,
> >
> > maybe I'm out of line here, but I would really like to see that CARD and
> > CT are not tied directly to (F)MIP. The reason is that there are other
> > ways to support mobile hosts, where you don't need (F)MIPv4/6. You could
> > use SIP to find the initial location of the user (if needed) and then use
> > a local mobility management mechanism to support the mobility within the
> > local domain. You would still need CARD and CT to enable seamless
> > mobility, though.
> >
> > Regards,
> > Jukka
> >
> > On Thu, 21 Aug 2003, James Kempf wrote:
> >
> > > Folks,
> > >
> > > This email is to confirm the concensus at the IETF 56 meeting to proceed
> toward
> > > completing the Seamoby work and closing the Working Group. This email also
> > > advances proposals for a couple of other issues that were not discussed at
> the
> > > meeting but are required to close out Seamoby.
> > >
> > > CARD:
> > >       - Drop draft-ietf-seamoby-card-requirements-02.txt.
> > >       - Take draft-ietf-seamoby-card-protocol-01.txt to Experimental rather
> than
> > >          Proposed Standard
> > >       - Use FMIP PrxyRtSol/SolPrxyRtAdv as transport for CARD information on
> > >         AR-MN interface. Consult with FMIP draft editor about best way to do
> > > this..
> > >       - Complete protocol on AR-AR interface that will support both learning
> > > based
> > >          and server based approaches.
> > >       - Protocol design complete by IETF 57 in Vienna.
> > >
> > > CT:
> > >
> > >     - Drop draft-ietf-seamoby-ct-reqs-05.txt.
> > >     - Take draft-ietf-seamobyh-ctp-01.txt to Experimental rather than
> > >        Proposed Standard.
> > >     - Complete protocol design by IETF 57 in Vienna.
> > >
> > > We did not discuss the following issues, here they are with some
> suggestions:
> > > about how to resolve them
> > >
> > >     - What to do with draft-ietf-seamoby-cardiscovery-issues-04.txt.
> > >        Since a clear statement of the problem is necessary for formulating
> > >        the research questions, continue to advance this document to
> > >        Informational.
> > >
> > >     - Relationship between CT and FMIP. Since the purpose of
> > >       Seamoby is to support fast handover, focus on a design
> > >       that integrated well with FMIP signaling.
> > >
> > > Discussion?
> > >
> > >             jak
> > >
> > >
> > > _______________________________________________
> > > Seamoby mailing list
> > > Seamoby@ietf.org
&amp;amp;gt; &amp;amp;gt; &amp;amp;gt; &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;amp;gt; &amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; &amp;amp;gt;
&amp;amp;gt; 
&amp;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;01899&amp;quot; href=&amp;quot;msg01899.html&amp;quot;&amp;gt;Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work&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;msg01900.html&amp;quot;&amp;gt;Re: [Seamoby] CT and access routers&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;msg01902.html&amp;quot;&amp;gt;RE: [Seamoby] Confirmation of Concensus on Completing Seamoby Work&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;msg01899.html&amp;quot;&amp;gt;Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work&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;msg01903.html&amp;quot;&amp;gt;Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work&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#01901&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#01901&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;msg01898.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;msg01900.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;msg01898.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;msg01900.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#01899&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#01899&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="msg01898.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01900.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01898.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01900.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01899"><strong>Date</strong></a></li>
<li><a href="threads.html#01899"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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