RFC 7448 on MIB Transfer from the IETF to the IEEE 802.3 WG

rfc-editor@rfc-editor.org Thu, 12 February 2015 18:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A2A1A1B24; Thu, 12 Feb 2015 10:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 TrIMaWSuXzED; Thu, 12 Feb 2015 10:12:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id A5BC21A1B0B; Thu, 12 Feb 2015 10:12:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 217EE187E3B; Thu, 12 Feb 2015 10:11:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7448 on MIB Transfer from the IETF to the IEEE 802.3 WG
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150212181127.217EE187E3B@rfc-editor.org>
Date: Thu, 12 Feb 2015 10:11:27 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/t9M_-OJwcJgr7dy52xYVcEa_Xic>
Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 18:12:11 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7448

        Title:      MIB Transfer from the IETF 
                    to the IEEE 802.3 WG 
        Author:     T. Taylor, Ed.,
                    D. Romascanu
        Status:     Informational
        Stream:     IETF
        Date:       February 2015
        Mailbox:    tom.taylor.stds@gmail.com, 
                    dromasca@avaya.com
        Pages:      7
        Characters: 12501
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-mibs-to-ieee80231-01.txt

        URL:        https://www.rfc-editor.org/info/rfc7448

This document records the transfer of responsibility for the
Ethernet-related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB,
POWER-ETHERNET-MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB,
ETHER-WIS, and MAU-MIB from the IETF to the IEEE 802.3 Working Group
(WG).  This document also describes the procedures associated with the
transfer in a similar way to how RFC 4663 records the transfer of the
IETF Bridge MIB work to the IEEE 802.1 WG.

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC