RFC 5579 on Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Interfaces

rfc-editor@rfc-editor.org Sat, 27 February 2010 03:50 UTC

Return-Path: <wwwrun@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 15FDB28C342 for <ietf-announce@core3.amsl.com>; Fri, 26 Feb 2010 19:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level:
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
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 PWx7TSGUNL1E for <ietf-announce@core3.amsl.com>; Fri, 26 Feb 2010 19:50:22 -0800 (PST)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 4477F28C2B4 for <ietf-announce@ietf.org>; Fri, 26 Feb 2010 19:50:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B72B8130014; Fri, 26 Feb 2010 19:52:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5579 on Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Interfaces
From: rfc-editor@rfc-editor.org
Message-Id: <20100227035239.B72B8130014@rfc-editor.org>
Date: Fri, 26 Feb 2010 19:52:39 -0800
Cc: 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: Sat, 27 Feb 2010 03:50:23 -0000

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

        
        RFC 5579

        Title:      Transmission of IPv4 Packets over 
                    Intra-Site Automatic Tunnel Addressing Protocol 
                    (ISATAP) Interfaces 
        Author:     F. Templin, Ed.
        Status:     Informational
        Date:       February 2010
        Mailbox:    fltemplin@acm.org
        Pages:      9
        Characters: 18998
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-templin-isatapv4-02.txt

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

The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
specifies a Non-Broadcast, Multiple Access (NBMA) interface type for
the transmission of IPv6 packets over IPv4 networks using automatic
IPv6-in-IPv4 encapsulation.  The original specifications make no
provisions for the encapsulation and transmission of IPv4 packets,
however.  This document specifies a method for transmitting IPv4
packets over ISATAP interfaces.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

This document is an Independent Submission.

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