Protocol Action: Multiprotocol Encapsulation over ATM Adaptation Layer 5 to Proposed Standard
The IESG <iesg-secretary@ietf.org> Fri, 20 August 1999 11:27 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11022; Fri, 20 Aug 1999 07:27:19 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA14024 for ietf-123-outbound.10@ietf.org; Fri, 20 Aug 1999 07:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA13812 for <all-ietf@loki.ietf.org>; Fri, 20 Aug 1999 07:03:54 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09760; Fri, 20 Aug 1999 06:58:42 -0400 (EDT)
Message-Id: <199908201058.GAA09760@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ion@sunroof.eng.sun.com
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Multiprotocol Encapsulation over ATM Adaptation Layer 5 to Proposed Standard
Date: Fri, 20 Aug 1999 06:58:42 -0400
Sender: scoya@cnri.reston.va.us
The IESG has approved publication of the following documents as Proposed Standards: o Multiprotocol Encapsulation over ATM Adaptation Layer 5 <draft-ietf-ion-multiprotocol-atm-04.txt>. This document replaces RFC1483, currently a Proposed Standard. o Virtual Private Networks Identifier <draft-ietf-ion-vpn-id-02.txt> These documents are the product of the Internetworking Over NBMA Working Group. The IESG contact persons are Erik Nordmark and Thomas Narten. Technical Summary The first document updates and replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. The first method allows multiplexing of multiple protocols over a single ATM virtual connection whereas the second method assumes that each protocol is carried over a separate ATM virtual connection. The document also defines how to encapsulate packets being carried as part of a specific ATM VPN. The second document defines the format for the VPN identifier used in ATM networks. The same VPN identifier may be useful as a VPN identifier in other technologies providing VPN service, but there is no requirement that it be used in other contexts. Working Group Summary There was consensus in the WG for these documents. Protocol Quality These documents have been reviewed for the IESG by Thomas Narten. The multiprotocol clarifies RFC 1483 and is recyling at Proposed rather than advancing to Draft because of the addition of the VPN encapsulation.