(ngtrans) I-D ACTION:draft-ietf-ngtrans-trans-scenes-00.txt
Internet-Drafts@ietf.org Fri, 16 April 1999 11:05 UTC
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29310
for <ngtrans-archive@odin.ietf.org>; Fri, 16 Apr 1999 07:05:43 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA06076;
Fri, 16 Apr 1999 04:05:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
by engmail4.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id
EAA09208; Fri, 16 Apr 1999 04:05:09 -0700 (PDT)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id EAA02662
for ngtrans-dist; Fri, 16 Apr 1999 04:03:55 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA02655
for <ngtrans@sunroof.eng.sun.com>; Fri, 16 Apr 1999 04:03:47 -0700 (PDT)
From: Internet-Drafts@ietf.org
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
by engmail3.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,
v%I%) with ESMTP id EAA28167
for <ngtrans@sunroof.eng.sun.com>; Fri, 16 Apr 1999 04:03:44 -0700 (PDT)
Received: from gatekeeper.era.co.uk (gatekeeper.era.co.uk [193.116.28.254])
by earth.sun.com (8.9.1/8.9.1) with ESMTP id EAA13042
for <ngtrans@sunroof.eng.sun.com>; Fri, 16 Apr 1999 04:03:17 -0700 (PDT)
Received: by gatekeeper.era.co.uk; id MAA22062;
Fri, 16 Apr 1999 12:02:15 +0100 (BST)
Received: from unknown(172.16.1.242) by gatekeeper via smap (V2.1)
id xma021897; Fri, 16 Apr 99 12:01:36 +0100
Received: from gatekeeper.era.co.uk (unverified [172.16.1.254]) by
vscan.era.co.uk
(Integralis SMTPRS 2.0.15) with SMTP id <B0000312132@vscan.era.co.uk> for
<s.ponnekanti@t-modus.co.uk>; Wed, 14 Apr 1999 19:23:13 +0100
Received: by gatekeeper.era.co.uk; id TAA17579;
Wed, 14 Apr 1999 19:21:33 +0100 (BST)
Received: from odin.ietf.org(132.151.1.176) by gatekeeper via smap (V2.1)
id xma017575; Wed, 14 Apr 99 19:21:29 +0100
Received: by ietf.org (8.9.1a/8.9.1a) id LAA20549
for ietf-123-outbound.10@ietf.org; Wed, 14 Apr 1999 11:05:03 -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 KAA19642;
Wed, 14 Apr 1999 10:43:24 -0400 (EDT)
Message-Id: <199904141443.KAA19642@ietf.org>
MIME-Version: 1.0
To: IETF-Announce:;;;;;;;;@era.co.uk@era.co.uk;;;;;;;;;;;;;;;;;;;;;
Cc: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-trans-scenes-00.txt
Date: Wed, 14 Apr 1999 10:43:23 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Transition Scenarios and Solutions Author(s) : T. Larder Filename : draft-ietf-ngtrans-trans-scenes-00.txt Pages : 22 Date : 13-Apr-99 The document details scenarios and proposed solutions using the current transition mechanisms. The first section categorises these mechanisms into 3 groups. The second section describes appropriate scenarios and demonstrates ow the mechanisms can be used and combined to form solutions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-trans-scenes-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-trans-scenes-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-trans-scenes-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
- (ngtrans) I-D ACTION:draft-ietf-ngtrans-trans-sce… Internet-Drafts