Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802.21] [DNA] Prefix information for link identification in DNA

Title:
Stefano:

This may be the case, which indicates we need a better definition. Andrea and I attempted to bring those last week in our comments, except we couldn't attend and present to the group.

I'll take the blame for that.

Peretz Feder

On 9/30/2005 10:47 AM, Stefano M. Faccin wrote:
Anyway, I have to agree with Srini. We're going in circles, we're back to discussing stuff discussed last week at the meeting and also a few mo nths agp (I recall a long detailed discussion in Atlanta about this).
Stefano

________________________________

From: ext Peretz Feder [mailto:pfeder@LUCENT.COM]
Sent: Fri 9/30/2005 9:38 AM
To: STDS-802-21@listserv.ieee.org
Subject: Re: [802.21] [DNA] Prefix information for link identification in DNA



Are you indicating attaching to a non MIH enabled AP/BS and receiving
MIH IS over R4 from a remote MIH info server?


On 9/30/2005 10:27 AM, Srinivas.Sreemanthula@nokia.com wrote:

  
Did we miss the whole discussion of MIH information services?


________________________________

      From: ext Peretz Feder [mailto:pfeder@LUCENT.COM]
      Sent: Friday, September 30, 2005 9:16 AM
      To: STDS-802-21@LISTSERV.IEEE.ORG
      Subject: Re: [802.21] [DNA] Prefix information for link
identification in DNA
     
     
      "you have first to be very clear about what you're attaching"
     
      I would think that in 802.21, we first attach the UE's MIH to a
BS/AP that supports MIH capability.
     
      On 9/30/2005 8:55 AM, Stefano M. Faccin wrote:
     

              Mike, well said!
              Stefano
             
              ________________________________
             
              From: ext Mike Moreton [mailto:mm2006@MAILSNARE.NET]
              Sent: Fri 9/30/2005 3:09 AM
              To: STDS-802-21@listserv.ieee.org
              Subject: Re: [802.21] [DNA] Prefix information for link
identification in DNA
             
             
             
              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