RE: [802.21] [DNA] Prefix information for link identification in DNA
Peretz, could it perhaps because you are giving a protocol-like interpretation to a generic functional model? An example: MIH communicates with L2, L3 and layers above L3. Also, MIH makes use of L3 transport services for 802.21 @ L3 and above. This makes it very difficult to call the MIH a protocol layer between L2 and L3.
Stefano
> -----Original Message-----
> From: ext Peretz Feder [mailto:pfeder@lucent.com]
> Sent: Friday, September 30, 2005 11:16
> To: Faccin Stefano (Nokia-NRC/Dallas)
> Cc: STDS-802-21@listserv.ieee.org
> Subject: Re: [802.21] [DNA] Prefix information for link identification
> in DNA
>
>
>
>
> On 9/30/2005 9:14 AM, stefano.faccin@nokia.com wrote:
>
> >Peretz, I thought we had decided to get away from the
> thinking that MIH is "below" L3 and "above" L2, since this is
> anyway incorrect.
> >
> This is not what Figure 1 shows in P802-21-D00-02.
>
> >I still think we hve both L2 PoAs and L3 PoAs, depending on
> the specific scenarios. Limiting the PoA to be at L2 is ...
> well, too limiting. For 802.21 @ L3, the PoA is of course @
> L3 snce the very first location where the <MIHF in the UE can
> send e.g. an IS request is @ or beyond the subnet where the
> UE gets its own IP address.
> >Stefano
> >
> >________________________________
> >
> >From: ext Peretz Feder [mailto:pfeder@LUCENT.COM]
> >Sent: Fri 9/30/2005 7:42 AM
> >To: STDS-802-21@listserv.ieee.org
> >Subject: Re: [802.21] [DNA] Prefix information for link
> identification in DNA
> >
> >
> >Within the discussion of MIH services, which is below layer
> 3, I would assume that MIH centric PoA should be below layer 3, no?
> >This is the 802.21 reflector, correct?
> >
> >Once PoA L2 (or L2.5) is established between MIH on the UE
> and MIH in the 802.21 compliant PoA and MIH services provided
> thereof, we can discuss higher layers PoAs in relation to
> other relevant MIH elements that require L3 transport services.
> >
> >Peretz Feder
> >
> >On 9/30/2005 4:09 AM, Mike Moreton wrote:
> >
> >
> > To extend (I think!) Stefano's point, before
> determining what the PoA is, you have first to be very clear
> about what you're attaching. Just saying "the terminal"
> makes no sense, because different layers in the terminal's
> protocol stack attach to different places in the network.
> >
> > For example, the PHY layer attaches to the AP, but the
> TCP layer attaches to the destination host.
> >
> > Mike.
> >
> >
> >
> > -----Original Message-----
> > From: Stefano M. Faccin
> [mailto:stefano.faccin@NOKIA.COM]
> > Sent: Friday, September 30, 2005 1:08 AM
> > To: STDS-802-21@listserv.ieee.org
> > Subject: Re: [802.21] [DNA] Prefix information for link
> > identification in DNA
> >
> >
> > Yoshihiro,
> > I'm not sure why should restrict the term PoA
> to have only a
> > L2 meaning as you suggest below. I think we should
> > distinguish clearly between L2 PoA and L3 PoA.
> For me, the L3
> > PoA is where the terminal gets IP conenctivity.
> E.g. for GPRS
> > the L3 PoA is the IP link on which the GGSN is
> located. In
> > L2, PoA is the point where the access-specific
> L2 connection
> > terminates (e.g. an AP in 802.11).
> > Stefano
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>