RFC 7241 on The IEEE 802/IETF Relationship

rfc-editor@rfc-editor.org Thu, 17 July 2014 19:17 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 E22A51A00B8 for <ietf-announce@ietfa.amsl.com>; Thu, 17 Jul 2014 12:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 QAZLsTJBioq0 for <ietf-announce@ietfa.amsl.com>; Thu, 17 Jul 2014 12:17:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id C61961A00AB for <ietf-announce@ietf.org>; Thu, 17 Jul 2014 12:17:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CB47B180095; Thu, 17 Jul 2014 12:16:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7241 on The IEEE 802/IETF Relationship
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140717191657.CB47B180095@rfc-editor.org>
Date: Thu, 17 Jul 2014 12:16:57 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/P1vrzJzdbUrzPIBgJjjSWoeWVNE
Cc: drafts-update-ref@iana.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, 17 Jul 2014 19:17:55 -0000

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

        
        RFC 7241

        Title:      The IEEE 802/IETF Relationship 
        Author:     S. Dawkins, P. Thaler, Ed.
        Status:     Informational
        Stream:     IAB
        Date:       July 2014
        Mailbox:    spencerdawkins.ietf@gmail.com, 
                    pthaler@broadcom.com, 
                    dromasca@avaya.com,
                    bernard_aboba@hotmail.com
        Pages:      35
        Characters: 80378
        Obsoletes:  RFC 4441

        I-D Tag:    draft-iab-rfc4441rev-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7241.txt

This document describes the standardization cooperation between
Project 802 of the Institute of Electrical and Electronics Engineers
(IEEE) and the Internet Engineering Task Force (IETF).  This document
obsoletes RFC 4441.

Note: This document was collaboratively developed by authors from
both the IEEE 802 and IETF leadership and was reviewed and
approved by the IEEE 802 Executive Committee prior to publication.

This document is a product of the Internet Architecture Board.


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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://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