RE: [Geopriv] Geopriv L7 LCP: New Requirement

From: Dawson, Martin ^lt;Martin.Dawson@andrew.com>
Date: Wed Feb 14 2007 - 16:38:46 EST

The acquisition protocol attribute that supports doing this is a client identity extension. RELO supports a form of it and HELD supports generic client ID extensions. A subscriber is identified to the visited LIS by their source IP@. An ISP LIS may be able to determine the L2TP tunnel identifier from a DSL provider that this subscriber is associated with. In order to query the DSL infrastructure provider LIS, the ISP LIS has to be able to add this L2TP tunnel to the client identifier (the IP@ is no longer a usable correlator). The DSL provider LIS can then associate the L2TP tunnel ID to the user's civic address as Guy, Barbara, and Otmar have described. Given the premise that nobody wants to define yet another acquisition protocol purely for the purpose of LIS-LIS communication, this requirement boils down to the need for the location request to be able to support other (typically access technology dependent) forms of client identifier than the IP address. Cheers, Martin -----Original Message----- From: g.caron@bell.ca [mailto:g.caron@bell.ca] Sent: Thursday, 15 February 2007 7:43 AM To: andy@hxr.us Cc: geopriv@ietf.org; Barbara.Stark@BellSouth.com; lendl@nic.at; hgs@cs.columbia.edu Subject: RE: [Geopriv] Geopriv L7 LCP: New Requirement Andrew, <Your requirement is that you need to communicate the location of a subscriber from the DSL provider to the ISP.> I agree with you and it would go like this: 0) VEP discovers the targeted LIS based on IP address and finds the ISP LIS 1) VEP sends a request for location to ISP LIS with IP Address over L7-LAP 2) ISP LIS recognizes the IP address as being in its realm and performs DB lookup to find L2TP info + ASP LIS URL (in this use case) 3) ISP LIS sends a request for location to ASP LIS with L2TP info over L7-LAP 4) ASP LIS recognizes L2TP info + ISP LIS credentials and performs DB lookup to find LO 5) ASP LIS responds to ISP LIS with LO over L7-LAP which forwards to VEP over L7-LAP Note: ASP stands for Access Service Provider, sometimes called Access Infrastructure Provider (AIP). It is the operator of the physical network (in this case, DSL). < What is the point of putting a requirement in a document if the intent is not to do anything with it?> If the above represents what you envision as well, and your position remains unchanged on this specific use case of LS-LS being already addressed by geopriv, therefore making it a requirement for all L2-LCPs and L7-LAPs to support it, then it may not be of value indeed. I would appreciate if you could confirm that is the case. Regards, Guy Caron -----Message d'origine----- De : Andrew Newton [mailto:andy@hxr.us] Envoyé : 14 février 2007 12:35 À : Caron, Guy (A162859) Cc : lendl@nic.at; Barbara.Stark@BellSouth.com; hgs@cs.columbia.edu; geopriv@ietf.org Objet : Re: [Geopriv] Geopriv L7 LCP: New Requirement On Feb 14, 2007, at 11:12 AM, g.caron@bell.ca wrote: > Is it your understanding that LIS to LIS and OBO within the context > of this thread are one of the same? > > I don't think they are. I don't think they are the same thing either, but that's not your requirement. Your requirement is that you need to communicate the location of a subscriber from the DSL provider to the ISP. What I'm stating is that you can already to that today. > If LIS to LIS is definitively covered by a geopriv document > somewhere then, can this requirement (L7 MUST support LS-LS) be > added to section 9? What is the point of putting a requirement in a document if the intent is not to do anything with it? -andy _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www1.ietf.org/mailman/listinfo/geopriv ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Wed, 14 Feb 2007 15:38:46 -0600

This archive was generated by hypermail 2.1.8 : Wed Feb 14 2007 - 16:38:17 EST