Re: [ieee-ietf-coord] Updated shared list of IETF - IEEE 802 coordination items
Benoit Claise <bclaise@cisco.com> Sun, 28 September 2014 20:47 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E5F1A2130 for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 28 Sep 2014 13:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level:
X-Spam-Status: No, score=-15.286 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szcbJjG2JWMd for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 28 Sep 2014 13:47:44 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9D91A1BE6 for <ieee-ietf-coord@ietf.org>; Sun, 28 Sep 2014 13:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17320; q=dns/txt; s=iport; t=1411937265; x=1413146865; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=IhKV03xmR+1BC2OztePz+i8RwZ1scUgbXpIWDoFonFE=; b=WG1I/BRSh1CYY9xl9u8puopEhFOcDGTSsUvdYdo/sCpQjWja3yBI4X8H 0AP+xhQhf4wmWf7n7Bf1/OpDH8SYHU+K3L0YzjmVepSXGiOWgZldjSwzh 65oDcear2GWSLsBHzGnrQSsbT0OMnRM1eaw6sG+8Dv9hB9JTbrJ4y7P2C E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As0FAFlzKFStJV2P/2dsb2JhbABfgkhGU4kzsGOOa4FjAQuHTAJ7FgF7hAQBAQMBAQEBKj4DAggGCwshFg8JAwIBAgEVMAYBDAYCAQGHXFYIDb5wAReMYYJQCxACAQFJAQuESwEEkHOFLIcJgWKFcI4LgXqCBSEvAQGCSAEBAQ
X-IronPort-AV: E=Sophos; i="5.04,615,1406592000"; d="scan'208,217"; a="82080511"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-3.cisco.com with ESMTP; 28 Sep 2014 20:47:43 +0000
Received: from [10.82.234.186] (rtp-vpn5-696.cisco.com [10.82.234.186]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s8SKlfD0015380; Sun, 28 Sep 2014 20:47:41 GMT
Message-ID: <542873ED.6020803@cisco.com>
Date: Sun, 28 Sep 2014 16:47:41 -0400
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C8ACDCF@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C8ACDCF@AZ-FFEXMB04.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------030908030707030001090903"
Archived-At: http://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/0Z6bEo_qsUCGwKbWRnHpiQibPK0
Subject: Re: [ieee-ietf-coord] Updated shared list of IETF - IEEE 802 coordination items
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Sep 2014 20:47:49 -0000
Dear all, Here is my status update on my 3 OPS issues. Regards, Benoit ================================================ 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 6/18/14 Benoit Claise): draft-ietf-opsawg-rfc5066bis has been published as RFC 7124 but that the initial transition document has not been completed. They have identified a new editor (Tom Taylor) for the proposed document. The current draft of the transition document has been posted as draft-taylor-opsawg-mibs-to-ieee80231. - Status 9/23/14 (Dan):https://datatracker.ietf.org/doc/draft-ietf-opsawg-mibs-to-ieee80231/ was sent to WGLC, and the announcement was forwarded to the ietf-ieee coordination mail list 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/ -http://datatracker.ietf.org/doc/draft-ietf-opsawg-mibs-to-ieee80231/ 7.3. Owners - Benoit Claise 7.4. Action Items Thank you Dan for updating this one. ================================================ 22. CAPWAP extensions in OPSAWG 22.1. Description: Extensions to the CAPWAP protocol are being defined in the IETF OPSAWG. The OPSAWG will send the documents that relate to IEEE 802.11 technology to the IEEE 802.11 WG for expert review. Status 1/27/14 (Benoit Claise) - there are two relevant drafts in Working Group Last Call. He sent out via email an updated description of this item, to be added to the next iteration of the shared work items list. Dan Romascanu will edit the shared work items list accordingly. Status 9/23/14 (Dorothy Stanley): Liaison requests have been made from the opsawg ?to IEEE 802.11 for review and comment on each of these documents. The IEEE 802.11 responded with the liaisons below. There are no open liaison requests from opsawg to IEEE 802.11 at this time. 22.2. Relevant Documents -http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/ -http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac -http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/ -https://datatracker.ietf.org/liaison/1312/ -https://mentor.ieee.org/802.11/dcn/14/11-14-0913-01-0000-liaison-response-opsawg-capwap-extension.docx -https://mentor.ieee.org/802.11/dcn/14/11-14-0684-01-0000-capwap-hybridmac-liaison-response.docx - Tunnel encapsulation response: slide 5 inhttps://mentor.ieee.org/802.11/dcn/14/11-14-0500-00-0000-may-2014-liaison-to-ietf-report.pptx 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 HERE IS OUR STATUS 1.http <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/>://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/ <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/> Received review from Adrian.P.Stephens@intel.com 2.http:// <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac>datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac> Status: AD review 3.http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/>/ <http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/> Status: AD Review Liaison requests have been made from the opsawg to IEEE 802.11 for review and comment on each of these documents. The IEEE 802.11 liaison response documents are here: -- https://mentor.ieee.org/802.11/dcn/14/11-14-0913-01-0000-liaison-response-opsawg-capwap-extension.docx -- https://mentor.ieee.org/802.11/dcn/14/11-14-0684-01-0000-capwap-hybridmac-liaison-response.docx -- Tunnel encapsulation response: slide 5 in https://mentor.ieee.org/802.11/dcn/14/11-14-0500-00-0000-may-2014-liaison-to-ietf-report.pptx There are no open liaison requests from opsawg to IEEE 802.11 at this time. Regards, Dorothy and Benoit > Please find attached a new version of the IETF -- IEEE 802 > coordination items, updated with information received in the last > week. Please use this in the preparation of the meeting on Monday. > > Cindy -- please upload the list on the Web page. > > Thanks and Regards, > > Dan > > > > _______________________________________________ > ieee-ietf-coord mailing list > ieee-ietf-coord@ietf.org > https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
- [ieee-ietf-coord] Updated shared list of IETF - I… Romascanu, Dan (Dan)
- Re: [ieee-ietf-coord] Updated shared list of IETF… Benoit Claise