RFC 5692 on Transmission of IP over Ethernet over IEEE 802.16 Networks
rfc-editor@rfc-editor.org Wed, 28 October 2009 19:22 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92E7628C21E; Wed, 28 Oct 2009 12:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.932
X-Spam-Level:
X-Spam-Status: No, score=-16.932 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5MV8ayqKuqp; Wed, 28 Oct 2009 12:22:19 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id C321628C21B; Wed, 28 Oct 2009 12:22:19 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id ABE7C356BC5; Wed, 28 Oct 2009 12:19:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5692 on Transmission of IP over Ethernet over IEEE 802.16 Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20091028191929.ABE7C356BC5@bosco.isi.edu>
Date: Wed, 28 Oct 2009 12:19:29 -0700
Cc: 16ng@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 28 Oct 2009 19:22:20 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5692 Title: Transmission of IP over Ethernet over IEEE 802.16 Networks Author: H. Jeon, S. Jeong, M. Riegel Status: Standards Track Date: October 2009 Mailbox: hongseok.jeon@gmail.com, sjjeong@etri.re.kr, maximilian.riegel@nsn.com Pages: 21 Characters: 44724 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-12.txt URL: http://www.rfc-editor.org/rfc/rfc5692.txt This document describes the transmission of IPv4 over Ethernet, as well as IPv6 over Ethernet, in an access network deploying the IEEE 802.16 cellular radio transmission technology. The Ethernet on top of IEEE 802.16 is realized by bridging connections that IEEE 802.16 provides between a base station and its associated subscriber stations. Due to the resource constraints of radio transmission systems and the limitations of the IEEE 802.16 Media Access Control (MAC) functionality for the realization of an Ethernet, the transmission of IP over Ethernet over IEEE 802.16 may considerably benefit by adding IP-specific support functions in the Ethernet over IEEE 802.16 while maintaining full compatibility with standard IP over Ethernet behavior. [STANDARDS TRACK] This document is a product of the IP over IEEE 802.16 Networks Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. 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/rfcsearch.html. 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 USC/Information Sciences Institute