[no subject]

> You seem to refer to Yoshi"s mail on orthogonality and also assume
that
> L2 paging areas always exist.

No, I don't. L2 paging areas may or may not exist. The L3
paging design needs to accommodate both, according to
the requirements.

> Orthogonality or L2 paging area
> configuration regardless of IP subnet structure can only happen in 2G
> voice-based cellular networks where the mobile is searched with its
link
> address, e.g. IMSI.

I'm sorry, I don't understand where you are coming from here. If one
defines a L3 paging area independently of the L2 paging area,
what difference does it make what the L2 identifier is? One
can define an abstraction to use.

> In 2.5G and 3G cellular networks IP communication is
> of prime concern. L2 paging areas regardless of IP subnet
configuration
> when  the mobile has to be searched with its IP address seems a wrong
> approach to me,

Which IP address? If it's MIP, then there are two. I don't think it
is possible to use the IP address of the MN to page, since one
use of dormant mode is to remove the need to maintain
routes.

>its only justification could be to reuse old paging
> areas already configured for 2G networks. Also I don't think IP Paging
> protocol could go into so much to link-related issues.

Sure, that's why it is important to design an appropriate abstraction
for L2 paging identifiers.

>   Secondly L2 paging areas exist only on cellular network links and
not
> of a given to any link.In where it exists (GPRS, 3GPP),  would they be
> interested in  IETF's IP Paging protocol is a big question mark, IMHO.
>

Well, I don't think existing cellular networks would be all that
interested,
frankly. They have Location Area Identifiers and updates for them
that are based on a paging area to subnet mapping. One of the
goals of the IP paging design is to move to an independent design.

>   Regarding renker draft, firstly renker-00 draft was based on MIPv6
and
> it was home agent based paging.

There were two cases, one with and one without MIPv6. The
requirements say that the protocol must be independent
of mobility protocol  but support existing mobility protocols.
It is up to the working group discussion as to
how to modify draft-renker to do this. Please
state your opinion if you have one.

>Jim mentioned in one of his previous
> emails the disadvantageous of HA based paging. Now, renker-01 draft is
a
> mess as Marco admits,

This is an inaccurate characterization of Marco's email. It was not any
more "a mess" then any of the other drafts. It needs cleaning up
w.r.t. holes and overspecifications.

>and its architecture is based on lumping
> everything together, which means, the authors do not know what to do
> with each architectural entity, so lets combine them. I also agree
with
> Yoshi on the marks given by the assessment team correctly marked it
low.
>

Behcet, instead of posting these negative generalizations of the
assessment
process, the selected draft, etc., I wish you would move on and
try to contribute something positive to actually defining the
protocol. As I've said, I think your team's contributions in
the area of time-slotted paging and L2 paging interface
were good, and your team's experience in this area would
be useful for the end result.

Rough concensus doesn't mean everybody agrees, it means
that almost everyone does. My reading of the list traffic
and the meeting is that we've got rough concensus
on starting the process of harmonizing the designs
based on draft-renker. Let's move on.

            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;00069&amp;quot; href=&amp;quot;msg00069.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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; Behcet Sarikaya &amp;amp;lt;behcet.sarikaya@alcatel.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;00065&amp;quot; href=&amp;quot;msg00065.html&amp;quot;&amp;gt;[Seamoby] IP Paging ]Framework discussion&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; Behcet Sarikaya &amp;amp;lt;behcet.sarikaya@alcatel.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;00066&amp;quot; href=&amp;quot;msg00066.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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;00067&amp;quot; href=&amp;quot;msg00067.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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; Behcet Sarikaya &amp;amp;lt;behcet.sarikaya@alcatel.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;msg00067.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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;msg00069.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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;msg00067.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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;msg00069.html&amp;quot;&amp;gt;Re: [Seamoby] IP Paging ]Framework discussion&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#00068&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;thrd74.html#00068&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;msg00066.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;msg00068.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;msg00066.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;msg00068.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#00067&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#00067&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="msg00066.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00068.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00066.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00068.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00067"><strong>Date</strong></a></li>
<li><a href="threads.html#00067"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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