Potential Areas for IETF/IEEE802 Coordination 0. Revision History 0.0 Initial Revision - 9/4/2012 0.1 revised for the period between 9/5 and 10/29 0.2 revised according to input received on 01, still reflects the 9/5-10/29 time interval 0.3 revised after the 10/29/12 meeting 0.4 revised for the period between 10/29 and 12/12 0.5 revised after the 12/17/12 meeting 0.6 revised for the period between 12/17/12 and 2/5/13 0.7 revised for the period between 2/5/13 and 4/30/13 0.8 revised after the 5/2/13 meeting 0.9 revised for the period between 5/2/13 and 9/22/13 0.10 revised after the 9/30 meeting 0.11 revised for the period between 9/30/13 and 1/22/14 1. IETF TRILL Fine-grained labeling and IEEE 802.1 tags 1.1 Description - CLOSED ------------------------------------------------------------------------- 2. IETF BFD and IEEE 802.1AX 2.1 Description - CLOSED (Note: draft-ietf-bfd-on-lags was approved by the IESG on 12/19/2013) ------------------------------------------------------------------------- 3. IETF NVO3 and IEEE 802.1 DCB 3.1. Description IEEE 802.1Qbg VDP might be used as the basis for the communication that NVO may need between an end system and an external box (e.g. bridge or router) doing the NVO encapsulation. Coordination will help determine if VDP is a suitable candidate and possibly to make any amendment needed in VDP for NVO usage. Status 10/26 - not much progress. The NVO3 working group continues to work on architecture and requirements. It remains unclear whether a "new" encapsulation will be required. Many people consider that there are enough encapsulations in the world already. In the 10/29 meeting - concerns from the IEEE that some of the NVO requirement drafts say things about 802.1 and its capabilities that don't take all the capabilities into account. There are some above layer 2 reasons to do NVO, and we think the requirements doc would portray that more accurately going forward. Concerns with the way 802.1Q capabilities are being portrayed. Also there's an 802.1 protocol called DCB that may be useful and we want it to get fair consideration if it's a fit. Status 12/17 (Pat, Adrian): Things are going fine, but we'll need to keep this open as things go along. Status 4/30: draft-ietf-nvo3-overlay-problem-statement-02 is in WGLC, several comments from participants in both IEEE 802.1 and IETF 6/5/13: draft-ietf-nvo3-overlay-problem-statement-03.txt in IETF LC, announcement shared on list Status 9/30/13 (Adrian): The problem statement document (draft-ietf- nvo3-overlay-problem-statement) has been approved for publication as an RFC and is currently with the RFC Editor. A number of I-Ds that have been adopted for work by the working group may be of interest to the IEEE since they discuss the data plane: - draft-ietf-nvo3-framework provides a framework for the NVO3 solutions - draft-ietf-nvo3-use-case tries to pick out the most common use cases - draft-ietf-nvo3-dataplane-requirements attempts to list the requirements on an NVO3 data plane - draft-ietf-nvo3-gap-analysis considers existing protocols against the requirements. The solutions it currently examines are: NVGRE, VxLAN, VPLS, EVPN, and L3VPN. Status 1/14/14 (Adrian): NVO3 progresses steadily with notifications of progress being sent to this list from time to time 3.2. Relevant Documents https://datatracker.ietf.org/liaison/1219/ http://datatracker.ietf.org/doc/draft-ietf-nvo3-overlay-problem-statement http://datatracker.ietf.org/doc/draft-ietf-nvo3-framework http://datatracker.ietf.org/doc/draft-ietf-nvo3-use-case http://datatracker.ietf.org/doc/draft draft-ietf-nvo3-dataplane-requirements http://datatracker.ietf.org/doc/draft-ietf-nvo3-gap-analysis 3.3. Owners - Adrian Farrel, Pat Thaler 3.4. Action Items - follow-up and send documents for review as they are adopted as WG items, WGLC and IETF LC. ------------------------------------------------------------------------- 4. IETF awareness of IEEE 802.1Q-2011 4.1. Description - CLOSED ------------------------------------------------------------------------- 5. Effect of virtualization on IEEE 802 architecture 5.1. Description At the 7/25 f2f meeting Glenn Parsons presented a brief overview of the IEEE Registration Authority Committee (RAC) mission, highlighting the current RAC policy on virtualization and asking what virtualization policy would reduce the consumption of EUI-48 addresses. Norman Finn suggested this could be an area of collaboration between the IETF and the IEEE 802. At the 9/5 virtual meeting Glenn Parsons reported that the action item from the last meeting on updating the IETF on virtualization at the Vancouver IETF Meeting (July/August, 2012) was completed. Status 4/30 - Glenn Parsons submitted an I-D and gave presentations at IETF-86 in the Technical Plenary, OPS and INT area meetings. The IEEE RAC will finalize and approve the proposal by June. 9/9/13: draft-ieee-rac-oui-restructuring-01.txt submitted Status 1/14/14 (Bob Grow):?Right now that would just be a RAC document, but the RAC is open to considering an RFC or IEEE Recommended Practice as appropriate. ?General consensus from the RAC has been to proceed with the RAC document before progressing to either of the standard documents. 5.2. Relevant Documents http://www.iab.org/2012/12/13/proposed-ieee-registration-authority-committee-oui-tier-restructuring/ http://www.ietf.org/proceedings/86/slides/slides-86-iab-techplenary-5.pdf https://datatracker.ietf.org/doc/draft-ieee-rac-oui-restructuring/ 5.3. Owners - Bob Grow 5.4. Action Items - Bernard (as IAB chair) sent on 12/12/12 a message to ietf-announce asking for feedback on the Proposed IEEE Registration Authority Committee OUI Tier Restructuring - Glenn to prepare the presentation for the technical plenary, and to submit companion I-D by end of January/early February - Done - Follow approval in IEEE, and then close the item, of no work is further required in the IETF ------------------------------------------------------------------------- 6. IETF EMU and IEEE 802.1X, 802.11 and 802.16 security based on EAP 6.1. Description - CLOSED ------------------------------------------------------------------------- 7. IETF Ethernet MIB, ADSL MIB and IEEE 802.3 7.1. Description In the transition process between the IETF and the IEEE the following documents were taken over by IEEE 802.3: RFC 2108 - Ethernet Repeater Devices RFC 3621 - Power Ethernet MIB RFC 3635 - Ethernet-like Interface Types RFC 3637 - Ethernet WAN Interface Sublayer RFC 4836 - Ethernet Medium Attachment Units (MAUs) RFC 4837 - Ethernet Passive Optical Networks (EPON) RFC 4878 - Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces RFC 5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces MIB The IF-CAP-STACK-MIB in RFC 5066 is generic and the IETF proposed to continue to be maintained by the IETF in a separate new document The IEEE 802.3 proposed to create an RFC that documents the issues related to the transition of the Ethernet MIB work to IEEE 802.3 similar to RFC 4663 which documents the transition of the Bridge MIB work to IEEE 802.1 - The OPSAWG was rechartered in October 2012 to include the two relevant documents - Status 4/30/13: draft-ietf-opsawg-rfc5066bis received a number of substantial comments in the OPSAWG review which resulted in the need for substantial edits, revised version is still in progress. The second I-D was not submitted yet. The IEEE 802.3.1 completes Recirculation Sponsor Ballot on 4/30. Dan submitted an Approve ballot, the document is expected to be released in June, probably with reference to the Internet-Draft. - Status 5/6/13: revised I-D draft-ietf-opsawg-rfc5066bis-02 was submitted, second Recirculation Ballot in IEEE 802.3.1 completed - Status 6/19/13: IEEE standard approved - Status 6/25/13: revised I-D draft-ietf-opsawg-rfc5066bis-03.txt submitted - Status 8/13/13: IEEE standard published as IEEE 802.3.1-2013 - Status 9/30/13 (Benoit): draft-ietf-opsawg-rfc5066bis entered Working Group Last Call on 27 July 2013. Editorial changes are expected, and the next version will progress to IETF Last Call. - draft-ietf-opsawg-rfc5066bis-07.txt approved by the IESG on 12/23/13 ? now in RFC Editor Queue - Ed Beili to prepare initial I-D for MIB work transition before the IETF-89 submission cut-out date (2/14/14) 7.2. Relevant Documents - IEEE 802.3.1-2013 - http://datatracker.ietf.org/wg/opsawg/charter/ - https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5066bis/ 7.3. Owners - Benoit Claise, Dan Romascanu, Ed Beili (IETF), Howard Frazier (IEEE 802.3) 7.4. Action Items - Dan Romascanu will enter the Sponsor Ballot pool and enter a comment suggesting that the IEEE 802.3 take out the IEEE8023-IF-CAP-STACK-MIB from their document and refer the IF-CAP-STACK-MIB instead - in progress, Sponsor Ballot started, comments need to be submitted until 1/13 - Done - Ed Beili will write an I-D targeting standards track that obsoletes RFC 5066 and extract IF-CAP-STACK-MIB from RFC5056, with wording emphasizing the generic nature of this module - now on the OPSAWG charter, CRITICAL TIMING issue initial I-D to be submitted by 12/28, to become an OPSAWG document before 1/25 - done - Ed Beili will write an I-D targeting informational RFC, similar to RFC 4663, with: a) Listing of all the RFCs obsoleted by the IEEE 802.3.1-2011 b) A table mapping the old IETF MIB names with the corresponding new IEEE ones c) Clarifications/rules on the IETF-IEEE interactions, mailing lists, reviews d) Clarifications on the intellectual property considerations The first version will be posted by Ed. Then Dan Romascanu and Howard Frazier will add IETF-IEEE interactions chapter. - Now on OPSAWG charter - Howard Frazier to add an EDITOR'S NOTE in the current IEEE MIB document, to explain the situation - Done - Dan Romascanu will submit an Approve Ballot in the Recirculation Sponsor Ballot (if all related issues are addressed) - Done - Benoit to forward I-D for review when it reaches IETF LC - Done - Ed Beili to submit initial transition I-D for IETF-89 ------------------------------------------------------------------------- 8. IETF 6LOWPAN and IEEE 802.15 8.1. Description - CLOSED ------------------------------------------------------------------------- 9. IETF PAWS WG and 802.11, 802.19, 802.22 9.1 Description - At the 9/5 virtual meeting Bruce Kraemer volunteered that one of the IETF PAWS WG Chairs (Gabor Bajko) is active in 802.11. Dan Romascanu took an action item to clarify with Gabor Bajko and Pete Resnick if there are any action items that need to be taken immediately regarding coordination. Gabors answer was that the coordination between IETF PAWS and IEEE 802.11af, 802.19 and 802.22 was so far handled by him; Gabor presented periodic updates of PAWS to these IEEE 802 groups, and took their input back to PAWS. So far this type of coordination did the job, although in the future some of this interaction may need to be handled via the official channels. - At the 10/29 meeting we confirmed the decision to take out IEEE 802.15 and IEEE 802.16 from the list. Coordination continues by now via participation of Gabor Bajko in both SDOs. Need confirmation this is OK with IEEE 802 - Status 4/30/13: draft-ietf-paws-problem-stmt-usecases-rqmts-15 was last-called and approved by the IESG, draft-ietf-paws-protocol is still in pre-WGLC state - Status 5/2/13: reasonable progress with draft-ietf-paws-protocol, no worries about progress - 6/20/13: Last Call issued on http://tools.ietf.org/html/draft-ietf- paws-protocol-06, sent to the coordination list - Status 9/30/13 (Pete): The use cases document was published as RFC 6953. The protocol document (draft-ietf-paws-protocol) remains under discussion in the Working Group, but will likely go to Working Group Last Call sometime around the Vancouver IETF meeting. Status 1/20/14 (Dorothy, Gabor): Version 8 of the paws protocol document was uploaded - no significant changes are expected, good time to send to IEEE 802.11 for review 9.2 Relevant Documents - http://datatracker.ietf.org/wg/paws/charter/ - http://www.rfc-editor.org/rfc/rfc6953.txt - https://datatracker.ietf.org/doc/draft-ietf-paws-protocol/ - http://www.ietf.org/mail-archive/web/paws/current/msg01535.html 9.3 Owners: Pete Resnick 9.4 Action Items - clarify whether IEEE 802.11af, 802.19 and 802.22 are all the relevant groups within IEEE 802 that need coordination with PAWS, modify item title accordingly - Done - Bruce to confirm the list and clarify at the IEEE plenary whether the current level of coordination is sufficient - Done - PAWS WG chairs to notify the IEEE 802 WGs when documents reach Last Call - Done - Dorothy Stanley to send draft-ietf-paws-protocol-08 to IEEE 802.11 collect and return comments ------------------------------------------------------------------------- 10. IETF IPPM and LMAP, and IEEE 802.16 Metrology Study Group- CLOSED, will reopen if/when it becomes clear that interaction is needed ------------------------------------------------------------------------- 11. IETF Mobile IP and EC OmniRAN Study Group 11.1. Description At the 7/25 f2f meeting Roger Marks presented a proposal for a new IEEE 802 WG to specify access network abstraction layer above IEEE 802 access technologies, noting that the work is related to some IETF WGs (e.g. DMM, MIF, NETEXT), and made the following recommendations: - IEEE 802 OmniRAN can close the gap and tie 802 devices into a family of standards within a heterogeneous IP network supporting evolving IETF standards - IEEE 802 and IETF should: * leverage each other's expertise * plan communications * identify commonalities * link solutions * organize a team to coordinate milestones and progress At the 9/5 virtual meeting Roger Marks indicated he would be the owner of this item. An action item was identified: Roger Marks to form a team to discuss coordination with possible input from Brian Haberman and Charlie Perkins. Roger reported in the 10/29 meeting that discussions are expected to be hold at the plenary meeting and he expects to have information to report after the plenary Roger reported in a mail sent on 11/26 that the IEEE 802 Executive Committee (EC) initiated the EC OmniRAN Study Group. It is chartered through the March 802 Plenary, with an expectation of extension through July. Max Riegel is the chair. Max Riegel sent a mail to the IESG on 12/11 including information on the Study Group 12/17 Status (Roger): Next Study Group meeting in January, will discuss requesting time in the INT Area meeting for a presentation and discussion Status 4/30/13: OmniRAN presentation was given at the 3/6/13 face2face meeting followed by Q&A and discussions Status 5/2: There is concern in 802 about what part of the problem belongs in 802 and if so in an existing group like .1 or .21, or a new group. Not expecting the group to settle on this until we're approaching the November meeting. Still working on the problem statement. 5/13: OmniRAN report presented at IEEE interim meeting - presentation pointer sent to the list Status 9/30/13 (Max Riegel): The IEEE Study Group is working on a PAR to submit for consideration at the IEEE 802 November meeting. He noted that the PAR is written for the lower layers, but that during the project there will be some interaction with IETF work on the higher layers. OmniRAN PAR approved at the November plenary 11.2. Relevant Documents http://www.ieee802.org/OmniRANsg/ http://www.iab.org/wp-content/IAB-uploads/2013/01/omniran-13-0011-01-ecsg-omniran-introduction-and-way-forward.pptx https://mentor.ieee.org/omniran/dcn/13/omniran-13-0030-04-ecsg-may-2013-waikoloa-agenda.pptx https://mentor.ieee.org/omniran/dcn/13/omniran-13-0086-00-ecsg-proposed-par-and-5c.docx 11.3. Owners - Max Riegel 11.4. Action Items - Discuss communication and coordination level in the 12/17 meeting - Done - IEEE will communicate after the January Interim whether to request presentation and discussion time in the INT Area meeting in Orlando. Done - planning for a 30 min presentation on the OmniRAN SG at the face-to-face leadership meeting by Max Riegel - Done - IEEE 802 will update about outcome of the SG work - probably after the November Plenary meeting  update to be provided in the 1/27/14 virtual meeting ------------------------------------------------------------------------- 12. IETF HOKEY and IEEE 802.21 12.1. Description CLOSED ------------------------------------------------------------------------- 13. IETF MIF and IEEE 802.21 - CLOSED, a new shared work item on naming in layer 2 networks will be open. Ted and Juan Carlos Zuniga to draft a description for the new shared work item. ------------------------------------------------------------------------- 14. IETF IPFIX Information Elements for Data Link monitoring  CLOSED (Note: draft-ietf-ipfix-data-link-layer-monitoring was approved by the IESG, the announcement was sent on 1/2/14) ------------------------------------------------------------------------- 15. IETF RADIUS attributes for IEEE 802 networks 15.1 Description The RADEXT WG specifies RADIUS attributes related to IEEE 802 network. Feedback from the IEEE on the attributes specifications would be appreciated. RADIUS Attributes for IEEE 802 Networks draft-ietf-radext-ieee802ext-02.txt Abstract RFC 3580 provides guidelines for the use of the Remote Authentication Dialin User Service (RADIUS) within IEEE 802 local area networks (LANs). This document proposes additional attributes for use within IEEE 802 networks, as well as clarifications on the usage of the EAP- Key-Name attribute, updating RFC 4072. The attributes defined in this document are usable both within RADIUS and Diameter. Status 12/17: comments received from 802.11, but not from 802.1. I-D forwarded for comments to participants in the Security TF Status 1/31: message from Mick Seaman - no comments from the Security TF Status 4/30/13: second WGLC was distributed, comments received from Max Riegel need to be addressed Status 5/2/13 (Benoit): One new revision of this was posted today. Not sure if this is final, a third WGLC until May 9th. Status 7/13: draft-ietf-radext-ieee802ext-08.txt submitted and discussed at IETF-87 with remote participation from Mick Seaman Status 9/30/13 (Benoit, Bernard): draft-ietf-radext-ieee802ext has gone through a third Working Group Last Call. There is one major issue, the authors will post a proposed resolution to the issue shortly. Status 1/22/14  the document is in IETF Last Call, the announcement was forwarded to the shared list 15.2. Relevant Documents: http://datatracker.ietf.org/doc/draft-ietf-radext-ieee802ext/ 15.3. Owners Bernard Adoba, the RADEXT chairs (Jouni Korhonen and Mauricio Sanchez ), and Benoit Claise 15.4. Action Items - address issues raised by Max Riegel in draft-03 - done - send again document for comments when it reaches IETF Last Call  Done - IEEE 802.1 to provide IETF Last Call comments if any ------------------------------------------------------------------------- 16. IEEE802.1Q SRP (and Gen2 updates) and RSVP/SIP - CLOSED ------------------------------------------------------------------------- 17. IEEE 802.1AS/1588 and NTP 17.1 Description IEEE 1588 and its primary L2-only profile, IEEE 802.1AS, define protocols and procedures for very precise and fast-responding synchronization. These procedures require some hardware-level time stamping services, and, in some cases, on-the-fly modification of packets as they are transmitted. 1588 is heavily used within the telecom and test/measurement community, and has been proposed for various smart grid applications as well. The L2-only 802.1AS is used in professional A/V networks, and is also in other environments where multiple L2 technologies are needed (the other 1588 profiles are Ethernet-only, even though they use IPv4 or IPv6 packet formats). The time format chosen by 1588 is a 64-bit seconds/nanoseconds composite instead of a seconds/fractions of a second composite as used by NTP. (Hey, don't blame me! I wanted the NTP format, myself.) Right now there are no specified procedures for NTP to use 1588/802.1AS when available, nor is there a router spec to define how 1588 can be used in the wider internet. There *are* a few papers that show that a "universal" time router/bridge could be built, and that if it were properly specified, the performance would be equivalent to any particularly 1588 profile. IEEE 1588 is about to be opened for revision, and the IEEE 802.1AS revision has already started as project 802.1ASbt. - Status (4/30/13 - Brian): The action item to form a small design team is on hold from the IETF perspective. After some discussion, it was decided to hold off on the formation of any design team until the IEEE 1588 PAR is approved and the 1558/TICTOC liaison is in place. Once those actions happen, we can revisit the topic. - Status (2/5/13 - Jon): Waiting for formality of 10-day letter ballot to close - Status (6/17/13 - Brian): Waiting for decision in the IEEE before coordinating with the IETF (TICTOC & NTP) - Status (9/30/13 - Michael): This item depends on coordination between IEEE 802.1 and 1588, before involving the IETF - Status (9/30/13  Brian): the work item is on hold until the 1588 and 802.1AS get synced within the IEEE. The kick-off of any DT would be with the establishment of a liaison between 1588 and the IETF (per Doug Arnold). - Open issue: IETF TICTOC/MPLS and IEEE-1588 (raised by Adrian) belongs here? Brian: I don't think it does. This is about 1588 transport over MPLS, it has anything to do with NTP or trying to synchronize NTP and 1588. 17.2 Relevant Documents IEEE Std 1588-2008 - "Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE Std 802.1AS-2011 - "Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks", NTP -"Network Time Protocol Version 4: Protocol and Algorithms Specification",RFC 5905, June 2010 http://ieee802.org/1/files/public/docs2013/as-mjt-ISPCS-39-11-next-gen-PTP-0113.pdf 17.3 Owners - Michael Johas Teener, Brian Haberman 17.4 Action Items - need one or more IETF experts to work with the 1588 and 802 communities, particularly since the relevant parts of those standards are (or soon will be) open for revision. Dan to approach the Transport and RAI ADs about how to proceed, copy Michael. - no response from the IETF ADs, need more information, proposal for a presentation by Michael and discussion at the face-to-face meeting on a possible unification of 1588, 802.1AS, and any number of "protocol specific" time synch methods -(at the f2f meeting): Brian Haberman will work with Michael Johas Teener to form a small design team to clarify the issues going on in the study group on Time Protocols Unification. - (2/5/13 meeting): The coordination team will follow up with the design team that will be formed to work on this item. - (9/30/13): Keep open, follow the IEEE developments as the item at this phase is more dependent on the coordination between IEEE 802.1 and 1588 than it is with IETF. ------------------------------------------------------------------------- 18. 802.1AS/1588, 802.1Q time aware shaper(s) and RTP - CLOSED ------------------------------------------------------------------------- 19. Common OAM proposal 19.1. Description - proposal made by Tissa Senevirathne and a group of TRILL contributors at the IEEE 802.1 meetings in July and September to reuse the IEEE 802.1ag frame format for TRILL OAM. Needs coordination and architectural consistency with the IEEE 802.1 architecture and OAM practice. - discussion at the 10/29 meeting: The requirements doc is going through WGLC so will come to IESG fairly soon. The framework doc being considered as a WG doc, so it has some time before it will be published by the WG. - Status 12/17 (Ralph): Had a conversation with the TRILL WG, they're going to progress the work for OAM for TRILL by progressing a requirements doc then a framework doc. If at that point they decided to go with an 802.1 base, they will go back to 802.1 and make sure that it doesn't infringe on the 802.1 OAM. But have to get the requirements and framework done first. - Status 4/20/13: https://datatracker.ietf.org/doc/draft-ietf-trill-oam- req/ was published as RFC 6905, draft-ietf-trill-oam-framework is discussed by the WG (pre-LC), draft-tissa-trill-oam-fm was not yet adopted as WG item - Status 2/5/13 (Donald): Framework draft had a lot of comments, expecting to be WGLC soon. Fault management doc needs to be reviewed, and then there will be an effort to move that to WG doc. The performance management doc is not as far along. - 8/20/13: The TRILL WG re-chartered, new charter includes OAM. Rechartering was communicated on the mail list. - 9/25/13: Liaison Statement sent by the TRILL chairs to the IEEE 802 informing on the status of the work. - 12/9/13: draft-ietf-trill-oam-framework approved by the IESG - 1/22/14: new liaison statement sent by TRILL to IEEE 802.1 19.2. Relevant Documents https://datatracker.ietf.org/doc/draft-ietf-trill-oam-req http://www.ieee802.org/1/files/public/docs2012/liaison-tissa-oam-ieee-trill-0912-v02.pptx https://datatracker.ietf.org/doc/draft-ietf-trill-oam-framework/ https://datatracker.ietf.org/doc/draft-tissa-trill-oam-fm/ http://datatracker.ietf.org/wg/trill/charter/ http://ieee802.org/1/files/public/docs2014/new-senevirathne-trill-oam-liaison-0114-v01.pptx 19.3. Owners - Ted Lemon, Norm Finn, Ben Mack-Crane 19.4. Action Items Ralph will send the TRILL OAM requirements document to IEEE 802.1 expert review (Pat, Norm, possibly other) - Done Follow the TRILL OAM documents progress in the WG and send them for review to IEEE 802.1 when they reach milestones (WGLC, IETF LC) ------------------------------------------------------------------------- 20. Area Name - use of TRILL as an alternative path selection protocol for use in 802.11 mesh networks 20.1. Description - CLOSED ------------------------------------------------------------------------- 21. 6tsch 21.1. Description: Enable communication and cross-review between the 6tisch WG and IEEE 802 - In IEEE 802.15: (Bob): Go to the 802.15 website and look for L2R under public docs. The group formed in March with a goal to spend 6 months to end up at a project point. - Status 9/22 - 6tisch charter in external review, on IESG agenda for 9/26, external review message distributed - Status 9/30/13 (Ted): WG was chartered - Presentation by Pascal Hubert at the IEEE 802 plenary - https://mentor.ieee.org/802.15/dcn/13/15-13-0685-00-wng0-6tisch-802-1-for-a-new-ipv6-multilink-subnet.pptx 21.2. Relevant Documents - Mail list https://www.ietf.org/mailman/listinfo/6tsch - https://datatracker.ietf.org/wg/6tisch/charter/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-architecture/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-terminology/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-tsch/ 21.3. Owners: Ted Lemon, Bob Heile 21.4. Action Items - follow the activities in the IETF and IEEE 802.15, share information informally until activities are chartered - Follow the activities, send relevant documents from the 6tisch WG as they reach Last Call stages. ------------------------------------------------------------------------- 22. CAPWAP extensions in OPSAWG 22.1. Description 22.2. Relevant Documents - https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac/ - https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/ 22.3. Owners: Benoit Claise and Dorothy Stanley 22.4. Action Items - Benoit to fill in the DESCRIPTION - Benoit to ensure that OPSAWG chairs send documents at Last Call to IEEE 802.11 - Dorothy Stanley to channel requests for reviews and responses between the OPSAWG and IEEE 802.11 ------------------------------------------------------------------------- 23. Area Name 23.1. Description 23.2. Relevant Documents 23.3. Owners 23.4. Action Items ------------------------------------------------------------------------- 24. Area Name 24.1. Description 24.2. Relevant Documents 24.3. Owners 24.4. Action Items