Impending publication: draft-iab-link-encaps-02.txt

Leslie Daigle <leslie@thinkingcat.com> Tue, 12 September 2006 22:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNH40-0003b7-2n; Tue, 12 Sep 2006 18:49:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNH3y-0003YA-TL; Tue, 12 Sep 2006 18:49:06 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNH3y-00040b-Re; Tue, 12 Sep 2006 18:49:06 -0400
Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GNH3w-0002Si-3M; Tue, 12 Sep 2006 18:49:06 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id CBCC61758E; Tue, 12 Sep 2006 22:48:33 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43) id 1GNH3R-0004c3-E1; Tue, 12 Sep 2006 18:48:33 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: Leslie Daigle <leslie@thinkingcat.com>
Message-Id: <E1GNH3R-0004c3-E1@ietf.org>
Date: Tue, 12 Sep 2006 18:48:33 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: iab@ietf.org
Subject: Impending publication: draft-iab-link-encaps-02.txt
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iab@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

The IAB is ready to ask the RFC-Editor to publish

     Multiple Encapsulation Methods Considered Harmful
                draft-iab-link-encaps-02.txt


as an Informational RFC. While typically a link layer protocol
supports only a single Internet Protocol (IP) encapsulation 
method, this is not always the case. Recently new link types 
have been defined that support multiple encapsulation methods.  
This document describes architectural and operational issues 
arising from use of multiple ways of encapsulating IP packets 
on the same link.  Multiple encapsulation methods are not, 
themselves, new -- previous considerations of the approach
are considered, as well as a review of potential issues related 
to the current proposals.


The IAB solicits comments by September 27, 2006. Please send
comments to the IAB (iab@iab.org) or to ietf@ietf.org.

The document can be found at

           
http://www.ietf.org/internet-drafts/draft-iab-link-encaps-02.txt


 From the Abstract:

   This document describes architectural and operational issues that
   arise from link layer protocols supporting multiple Internet Protocol
   encapsulation methods.



Leslie Daigle,
      For the IAB.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce