[no subject]

> As assessment team correctly evaluated,
> draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies independency
> from mobility protocol.
>

Yes.

> draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies indepenency of
> paging area from subnet topology, but unfortunately the selection team
> seems to misunderstand that the protocol does not satisfy this
> requirement, which I also pointed out this both on the mike in the SLC
> meeting and in my comments posted before the SLC meeting.  Actually,
> we paid a special care on this point, for example we explitly
> mentioned in the draft that:
>
>    Paging Area
>
>      (snip)
>
>      An arbitrary mapping between subnets and paging areas is allowed
in
>      this protocol.
>

But do you think it is realistic to expect the paging team to rate
the design based on this single sentence when the name of the protocol
implies a connection between the subnet and paging area, and the
rest of the design is described in terms of having a paging agent (which
controls the paging area) in the last hop subnet?

> Jim also mentioned in the SLC meeting that our protocol requires
> extranous signaling (among separate agents), which is not desirable.
> This is not exactly correct because our protocol allows elimination of
> extranous signaling by implementing those agents in a single box (for
> small size networks).  Extranous signaling is inevitable if
> scalability matters.  For the same reason, extranous signaling is also
> described in the selected protocol if PA is hierachically configured.
> There is always tradeoff between scalability and centralized agent.
>

Exactly what functional elements to group into a network element
is a design, not an implementation, choice. The draft-ohba design chose
a one to one mapping between functional elements and network
elements. While it is certainly possible to deploy by bundling
multiple network entities on a single host, the interface between
the entities, and thus the protocols on those interfaces, remain
as does the potential for extraneous signaling.

That said, I agree that it is certainly a challenge to come up with
a design that minimizes signaling, and I think that, going
forward, we need to keep this in mind.

> Jim also mentioned in the SLC meeting that our protocol does not
> support time-slotted dormant mode at L3.  This is true, but
> time-slotted dormant mode at L3 was not explicitly described in the
> requirements document, and I don't think the basic issue of how to
> synchronize at L3 can be solved by just definig a set of
> synchronization timing parameters.  Additional consideration of
> hardware-based IP-paging implementation and interference with other
> traffic, etc. would be still necessary if we really want to archive
> it.
>

The requirements do call out the need to support multiple dormant
modes, and that requires the ability to support time-slotted paging.
For example, draft-sarikaya has a good description of how
to support time-slotted paging. I recall having discussed this
in the requirements phase, but perhaps we should have been
clearer in the requirements document about what support for multiple
dormant modes means.


            jak


_______________________________________________
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;00056&amp;quot; href=&amp;quot;msg00056.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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; Yoshihiro Ohba &amp;amp;lt;yohba@tari.toshiba.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;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;00034&amp;quot; href=&amp;quot;msg00034.html&amp;quot;&amp;gt;[Seamoby] comments on the paging protocol assessment draft&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; Yoshihiro Ohba &amp;amp;lt;yohba@tari.toshiba.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;00049&amp;quot; href=&amp;quot;msg00049.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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;00052&amp;quot; href=&amp;quot;msg00052.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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; Yoshihiro Ohba &amp;amp;lt;yohba@tari.toshiba.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;msg00052.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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;msg00054.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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;msg00052.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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;msg00056.html&amp;quot;&amp;gt;Re: [Seamoby] comments on the paging protocol assessment draft&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;mail76.html#00053&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;thrd76.html#00053&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;msg00052.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;msg00054.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;msg00052.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;msg00054.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#00053&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#00053&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="msg00052.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00054.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00052.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00054.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00053"><strong>Date</strong></a></li>
<li><a href="threads.html#00053"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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