1 / 13

IEEE 802.1 OmniRAN TG May 2014 F2F Meeting

IEEE 802.1 OmniRAN TG May 2014 F2F Meeting. 2014-05-14 Max Riegel, NSN ( OmniRAN TG Chair). Schedule: May 14th, 2014, 2pm - 5pm Greenway Room (4th floor) May 15th, 2014, 9am - 5pm Greenway Room (4th floor) Attendence: https://imat.ieee.org/attendance Session Access Code: Wisconsin.

samara
Télécharger la présentation

IEEE 802.1 OmniRAN TG May 2014 F2F Meeting

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. IEEE 802.1 OmniRAN TGMay 2014 F2F Meeting 2014-05-14 Max Riegel, NSN (OmniRAN TG Chair)

  2. Schedule: May 14th, 2014, 2pm - 5pm Greenway Room (4th floor) May 15th, 2014, 9am - 5pm Greenway Room (4th floor) Attendence: https://imat.ieee.org/attendance Session Access Code: Wisconsin May 2014 F2F Meeting

  3. All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]: “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search Participants, Patents, and Duty to Inform

  4. All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/develop/policies/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/about/sasb/patcom/materials.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/about/sasb/patcom/index.html This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt Patent Related Links

  5. If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: Either speak up now or Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or Cause an LOA to be submitted Call for Potentially Essential Patents

  6. Other Guidelines for IEEE WG Meetings All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • Technical considerations remain primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.

  7. Link to IEEE Disclosure of Affiliation http://standards.ieee.org/faqs/affiliationFAQ.html Links to IEEE Antitrust Guidelines http://standards.ieee.org/resources/antitrust-guidelines.pdf Link to IEEE Code of Ethics http://www.ieee.org/web/membership/ethics/code_ethics.html Link to IEEE Patent Policy http://standards.ieee.org/board/pat/pat-slideset.ppt Resources – URLs

  8. Approval of minutes Reports TG Organization Example contributions to the intended specification Outline of the intended specification Organization of the work Alignment within IEEE 802.1 Cooperation with the other IEEE 802 WGs at July plenary Conference call until July 2014 session Liaison report to IEEE 802 WGs ITU-T Liaison on SDN AOB Agenda

  9. May 2014 Agenda Graphics

  10. Business#1 • Call Meeting to Order • Meeting called to order by chair at 2pm • Appointment of recording secretary: • Juan Carlos volunteered to take notes • Roll Call

  11. Business#2 • Approval of minutes • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0035-00-00TG-apr-29th-meeting-minutes.docx • Approved without any comments • Reports • OmniRAN presentation to Joint IWK/TSN Mtg • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0037-00-00TG-omniran-p802-1cf-cooperations.pptx • Recommendation to add IEEE 802.17 as further access technology • Discussions about the appropriate choice of IEEE 802.15 technology • TG Organization • 802.1 Membership Rights • 802.1 membership rights provided to OmniRAN TG participants, when • Attending initial OmniRAN TG meeting in Norfolk, VA • Gaining attendence credit for the 802.1 interim meeting in Norfolk, VA • Sending email to the 802.1 chair applying for membership rights • 802.1 membership rights are not required for active participation in OmniRAN TG • Everybody can participate; straw polls instead of voting • OmniRAN TG wiki • https://mentor.ieee.org/omniran/bp/StartPage • One-stop place for latest status and announcements • Announcements distributed as well on the STDS-802-1-L@LISTSERV.IEEE.ORG • Likely a combination of mentor and 802.1 file space will be used • Mentor for contributions, 802.1 file space for the agreed material going into 802.1CF • Further thinking after introduction into the 802.1 web environment on grouper

  12. Business#3 • Example contributions to the intended specification • R3 Considerations • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0038-00-CF00-802-1cf-r3-considerations.pptx • Agreement that proposed split of R3 makes sense but requires further evaluation • PtP Links by PBB-TE and SDN • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0040-00-CF00-ethernet-connection-service.pdf • Paul will deliver textual description of the main idea presented in the slides. • ITU-T Liaison on SDN • http://www.ieee802.org/1/files/public/docs2014/liaison-ITUTSG15-LS114_229P-AnnN-0414.DOCX • ITU-T SG15 makes OmniRAN aware of their Stage 2 specification work and likes to align its SDN related architectural work with the SDN specification work in 802.1CF • IEEE 802 reponse not due before July plenary meeting. • Referenced ITU-T specifications will be reviewed in the upcoming OmniRAN conference call • Outline of the intended specification • SDN use cases and requirements • Tbd

  13. Business#4 • Outline of the intended specification • Backhaul in 802.1CF • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0030-00-0000-backhaul-in-omniran.pptx • ToC Refinements • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0039-00-CF00-802-1cf-toc-refinements.pptx • Organization of the work • Alignment within IEEE 802.1 • Cooperation with the other IEEE 802 WGs at July plenary • Conference call until July 2014 session • Next IEEE 802 plenary session on July 14-18 in San Diego, CA • Schedule: • Agenda • Liaison report to IEEE 802 WGs • AOB

More Related