IETF Logo Mail Archive

Re: control protocols

Ned Freed <NED@innosoft.com> Thu, 05 October 1995 05:36 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06077; 5 Oct 95 1:36 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06073; 5 Oct 95 1:36 EDT
Received: from [192.94.214.96] by CNRI.Reston.VA.US id aa02594; 5 Oct 95 1:36 EDT
Received: from neptune.tis.com by neptune.TIS.COM id aa28298; 5 Oct 95 1:26 EDT
Received: from relay.tis.com by neptune.TIS.COM id aa28293; 5 Oct 95 1:22 EDT
Received: from thor.innosoft.com(192.160.253.66) by relay.tis.com via smap (g3.0.1) id xma027600; Thu, 5 Oct 95 01:05:35 -0400
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V5.0-5 #2001) id <01HW23J533PC8Y5OBE@INNOSOFT.COM>; Wed, 04 Oct 1995 22:22:55 -0700 (PDT)
Date: Wed, 04 Oct 1995 22:21:45 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <NED@innosoft.com>
Subject: Re: control protocols
In-reply-to: "Your message dated Wed, 04 Oct 1995 16:30:25 -0400" <199510042030.QAA14302@black-ice.cc.vt.edu>
To: Valdis.Kletnieks@vt.edu
Cc: Peter Williams <peter@verisign.com>, pem-dev@tis.com
Message-id: <01HW243P72OA8Y5OBE@INNOSOFT.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit
References: <199510041855.LAA20713@dustin.verisign.com>

> Something that is sorely needed is an RFC draft for new external body parts -
> in particular, for SSL-secured HTTP connections and the like.. Or did I miss
> a draft someplace?

You missed a draft -- draft-ietf-mailext-acc-url-00.txt, to be specific.
This specifies a URL access type for message/external-body.

			Ned

v2.23.0 | Report a Bug | By Email