[16NG] RFC 5948 on Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16
rfc-editor@rfc-editor.org Thu, 19 August 2010 23:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78D133A6A6A; Thu, 19 Aug 2010 16:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.058
X-Spam-Level:
X-Spam-Status: No, score=-102.058 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 uZpAW1Gh6Ot5; Thu, 19 Aug 2010 16:21:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id AB19D3A6A51; Thu, 19 Aug 2010 16:21:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C9A63E06E5; Thu, 19 Aug 2010 16:22:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100819232218.C9A63E06E5@rfc-editor.org>
Date: Thu, 19 Aug 2010 16:22:18 -0700
Cc: 16ng@ietf.org, rfc-editor@rfc-editor.org
Subject: [16NG] RFC 5948 on Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Aug 2010 23:21:44 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5948 Title: Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16 Author: S. Madanapalli, S. Park, S. Chakrabarti, G. Montenegro Status: Standards Track Stream: IETF Date: August 2010 Mailbox: smadanapalli@gmail.com, soohong.park@samsung.com, samitac@ipinfusion.com, gabriel.montenegro@microsoft.com Pages: 13 Characters: 26553 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt URL: http://www.rfc-editor.org/rfc/rfc5948.txt IEEE 802.16 is an air interface specification for wireless broadband access. IEEE 802.16 has specified multiple service-specific Convergence Sublayers for transmitting upper-layer protocols. The Packet CS (Packet Convergence Sublayer) is used for the transport of all packet-based protocols such as the Internet Protocol (IP) and IEEE 802.3 (Ethernet). The IP-specific part of the Packet CS enables the transport of IPv4 packets directly over the IEEE 802.16 Media Access Control (MAC) layer. This document specifies the frame format, the Maximum Transmission Unit (MTU), and the address assignment procedures for transmitting IPv4 packets over the IP-specific part of the Packet Convergence Sublayer of IEEE 802.16. [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 Association Management Solutions, LLC