[16NG] RFC 5154 on IP over IEEE 802.16 Problem Statement and Goals
rfc-editor@rfc-editor.org Wed, 09 April 2008 21:46 UTC
Return-Path: <16ng-bounces@ietf.org>
X-Original-To: 16ng-archive@optimus.ietf.org
Delivered-To: ietfarch-16ng-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 593A228C251; Wed, 9 Apr 2008 14:46:09 -0700 (PDT)
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 04AAB28C265; Wed, 9 Apr 2008 14:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.127
X-Spam-Level:
X-Spam-Status: No, score=-17.127 tagged_above=-999 required=5 tests=[AWL=0.472, BAYES_00=-2.599, 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 flB2QHOwOoOf; Wed, 9 Apr 2008 14:46:07 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id B89A828C251; Wed, 9 Apr 2008 14:46:06 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 3342912368D; Wed, 9 Apr 2008 14:46:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080409214626.3342912368D@bosco.isi.edu>
Date: Wed, 09 Apr 2008 14:46:26 -0700
Cc: 16ng@ietf.org, rfc-editor@rfc-editor.org
Subject: [16NG] RFC 5154 on IP over IEEE 802.16 Problem Statement and Goals
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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 16ng-bounces@ietf.org
Errors-To: 16ng-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 5154 Title: IP over IEEE 802.16 Problem Statement and Goals Author: J. Jee, Ed., S. Madanapalli, J. Mandin Status: Informational Date: April 2008 Mailbox: jhjee@etri.re.kr, smadanapalli@gmail.com, j_mandin@yahoo.com Pages: 14 Characters: 29853 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-16ng-ps-goals-04.txt URL: http://www.rfc-editor.org/rfc/rfc5154.txt This document specifies problems in running IP over IEEE 802.16 networks by identifying specific gaps in the IEEE 802.16 Media Access Control (MAC) for IPv4 and IPv6 support. This document also provides an overview of IEEE 802.16 network characteristics and convergence sublayers. Common terminology used for the base guideline while defining the solution framework is also presented. This memo provides information for the Internet community. This document is a product of the IP over IEEE 802.16 Networks 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ 16NG mailing list 16NG@ietf.org https://www.ietf.org/mailman/listinfo/16ng