[no subject]

----- Original Message -----
From: "Eunsoo Shim" <eunsoo@nec-labs.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
Sent: Monday, March 24, 2003 12:34 PM
Subject: Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work


> James,
>
> Right.The design team proposed that the specification allows two options:
> piggybacking as ICMP options and stand-alone messages.
> I think this is a good approach that can satisfy many things.
>
> Eunsoo
>
> ----- Original Message -----
> From: "James Kempf" <kempf@docomolabs-usa.com>
> To: "Eunsoo Shim" <eunsoo@nec-labs.com>; <seamoby@ietf.org>
> Sent: Sunday, August 24, 2003 8:21 AM
> Subject: Re: [Seamoby] Confirmation of Concensus on Completing Seamoby Work
>
>
> > Defining the CARD messages as generalized ICMP options for RFC 2461 and
> > associated extentions is acceptable. I presume this is what you mean by
> > "piggybacking".
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Eunsoo Shim" <eunsoo@nec-labs.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
> > Sent: Sunday, March 23, 2003 8:37 AM
> > Subject: Re: [Seamoby] Confirmation of Concensus on Completing Seamoby
> Work
> >
> >
> > > It was agreed to make the CARD messages piggyback-able in the past.
> > > Then the CARD messages could be transported even on top of other
> messages
> > > than FMIP messages.
> > > Also we don't have to worry about how FMIP will turn out in the future.
> Or
> > > the FMIP designers don't have to worry about the semantics change
> required
> > > by the CARD protocol.
> > > Piggybacking wouldn't be better than tight-coupling with FMIP?
> > >
> > > Eunsoo
> > >
> > > > Extending the semantics is the proposal. Or, alternatively, delivering
> the
> > > > learning-based information via a RS.
> > > >
> > > > If it turns out not to be a good match, then an additional message
> could
> > > be
> > > > added for the learning based approach.
> > > >
> > > >             jak
> > > >
> > > > ----- Original Message -----
> > > > From: "Eunsoo Shim" <eunsoo@nec-labs.com>
> > > > To: "James Kempf" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
> > > > Sent: Saturday, March 22, 2003 1:13 PM
> > > > Subject: Re: [Seamoby] Confirmation of Concensus on Completing Seamoby
> > > Work
> > > >
> > > >
> > > > > FMIP PrxyRtSol/SolPrxyRtAdv are just for delivering the CAR
> information
> > > > > after discovery.
> > > > > In Dycard, the discovery requires messages between MN and AR for
> > > delivering
> > > > > the IP address of the previous AR to the current AR. This is beyond
> the
> > > > > purpose of FMIP PrxyRtSol/SolPrxyRtAdv messages.
> > > > > I wonder whether the proposal is to extend the semantics of FMIP
> > > > > PrxyRtSol/SolPrxyRtAdv for all the necessary signaling messages
> between
> > > AR
> > > > > and MN for CARD.
> > > > >
> > > > > Eunsoo
> > > > >
> > > > >
> > > > > > 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;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; &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; &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;
&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;01894&amp;quot; href=&amp;quot;msg01894.html&amp;quot;&amp;gt;[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;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;01903&amp;quot; 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;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;em&amp;gt;From:&amp;lt;/em&amp;gt; &amp;amp;quot;Eunsoo Shim&amp;amp;quot; &amp;amp;lt;eunsoo@nec-labs.com&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;01906&amp;quot; href=&amp;quot;msg01906.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;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;01908&amp;quot; href=&amp;quot;msg01908.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;Eunsoo Shim&amp;amp;quot; &amp;amp;lt;eunsoo@nec-labs.com&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;01911&amp;quot; href=&amp;quot;msg01911.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;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;01912&amp;quot; href=&amp;quot;msg01912.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;Eunsoo Shim&amp;amp;quot; &amp;amp;lt;eunsoo@nec-labs.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;msg01913.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 Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg01915.html&amp;quot;&amp;gt;[Seamoby] Re: MN defined twice and lack of MH (was: The NEMO/Seamoby terminology)&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;msg01912.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;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;Index(es):
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;mail2.html#01914&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;thrd3.html#01914&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;msg01911.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;msg01913.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;msg01911.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;msg01913.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#01912&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#01912&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="msg01911.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01913.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01911.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01913.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01912"><strong>Date</strong></a></li>
<li><a href="threads.html#01912"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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