1 / 6

draft-melia-mipshop-mobility-services-ps-01.txt

draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66. Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts related to mobility services were presented )

starr
Download Presentation

draft-melia-mipshop-mobility-services-ps-01.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-melia-mipshop-mobility-services-ps-01.txt

  2. From IETF #66 • Discuss MIH PS (as expressed by the WG chair) • Need a single PS at WG level (several drafts related to mobility services were presented ) • Strongly suggest interested parties to work offline and produce common PS by last week of August • Target is to have PS draft in WG last call by end of September

  3. PS -00 version • Document submitted beginning of September • Main body • how to transport signaling messages for media independent handovers. • It nicely maps to 802.21 while being readable from non .21 folks • Appendixes for different mobility services support • Some approaches were 802.21 based, some not

  4. Comments to ID -00 • Text too long not focusing on a problem statement recommendation make it shorter • Make the ID 802.21 related (in contrast with what agreed in IETF #66?) not covering mobility services as a whole • 802.21 specific drafts were presented IETF #64 together with some specific Mobopts work • James: “The current document could potentially be changed into an architectural document that describes the MIS architecture and how 802.21 protocol implements it, and where an IETF transport solution fits in.” • Daniel: "MIPSHOP will define the delivery of information for MIH services for this latter case. Obviously, MIH means IEEE 802.21 not *mobility service*. No doubt.”

  5. Version -01 • Removed appendixes • Updated main body still giving a broad overview

  6. Way forward? • So far no technical objections on the content • Three possible options: • Main body only (version -01) • Main body plus all appendixes (version -00) • Main body plus one .21 specific appendix (version -02 ??)

More Related