RFC 6250 on Evolution of the IP Model

rfc-editor@rfc-editor.org Fri, 20 May 2011 01:14 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BED3E0776 for <ietf-announce@ietfa.amsl.com>; Thu, 19 May 2011 18:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.345
X-Spam-Level:
X-Spam-Status: No, score=-102.345 tagged_above=-999 required=5 tests=[AWL=0.255, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUZU9MsThIiK for <ietf-announce@ietfa.amsl.com>; Thu, 19 May 2011 18:14:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 55320E0774 for <ietf-announce@ietf.org>; Thu, 19 May 2011 18:14:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 015B3E077E; Thu, 19 May 2011 18:13:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6250 on Evolution of the IP Model
From: rfc-editor@rfc-editor.org
Message-Id: <20110520011400.015B3E077E@rfc-editor.org>
Date: Thu, 19 May 2011 18:13:59 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 20 May 2011 01:14:01 -0000

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

        
        RFC 6250

        Title:      Evolution of the IP Model 
        Author:     D. Thaler
        Status:     Informational
        Stream:     IAB
        Date:       May 2011
        Mailbox:    dthaler@microsoft.com
        Pages:      25
        Characters: 60778
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-ip-model-evolution-04.txt

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

This RFC attempts to document various aspects of the IP service model
and how it has evolved over time.  In particular, it attempts to
document the properties of the IP layer as they are seen by upper-
layer protocols and applications, especially properties that were
(and, at times, still are) incorrectly perceived to exist as well as
properties that would cause problems if changed.  The discussion of
these properties is organized around evaluating a set of claims, or
misconceptions.  Finally, this document provides some guidance to
protocol designers and implementers.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

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/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