Hi Tony The I-D we submitted exclusively focuses on LI Architecture models for Service Provider Wi-Fi deployments and covers SP Wi-Fi deployments with Inter-Operator Roaming scenarios & without Inter-Operator Roaming scenarios. Intent is to provide the Wi-Fi Operators with a comprehensive reference document which covers the LI specific interactions between the key SP Wi-Fi components and LI Functional Elements . High level description of the control plane interactions between these entities are included as well in the document . Also the document explores how some of the existing mobility protocols can be leveraged for the implementation of LI for scenarios with and without Inter-Operator roaming, how to handle the local breakout traffic in Inter-Operator Roaming Scenarios etc. We do not think these aspects are covered in the documents you have referenced.
Also wanted to point out, capturing the requirements is not the focus of this I-D since it has been captured already in several LI related documents." Thanks & Regards Byju On 2/19/13 5:57 PM, "Tony Rutkowski" <[email protected]> wrote: >Hi Byju, > >Why don't the present official specifications >for this purpose suffice? > >TS102232-3 provides for the capability and >operates in conjunction with TS102232-1 >which provides for trusted transport, and >interoperable with the new eWarrant spec. >The standard is current as of December >2012 and used worldwide. > >TR102519 which is now six years old and >preceded the development of 102232-3, >states the generic requirements similar to >your draft. > >All the specs here are non-proprietary, >well versioned, publicly available, and >provide for structured exchange of the >information. What purpose would an >ID in the IETF on the same subject >serve? > >--tony > _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
