Subject: [Hipsec] [Fwd: I-D ACTION:draft-eggert-hip-rendezvous-00.txt]

From: [email-masked] (Lars Eggert)
Date: Tue Feb 10 12:32:04 2004

This is a cryptographically signed message in MIME format.

--------------ms000800080601010504030205
Content-Type: multipart/mixed;
 boundary="------------000702020403060205060002"

This is a multi-part message in MIME format.
--------------000702020403060205060002
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I've put together an ID that discusses different alternatives for HIP 
rendezvous mechanisms, and would appreciate WG feedback.

Thanks,
Lars
-- 
Lars Eggert                                     NEC Network Laboratories

--------------000702020403060205060002
Content-Type: message/rfc822;
 name="I-D ACTION:draft-eggert-hip-rendezvous-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="I-D ACTION:draft-eggert-hip-rendezvous-00.txt"

To: IETF-Announce: ;
From: [email-masked]
Reply-To: [email-masked]
Subject: I-D ACTION:draft-eggert-hip-rendezvous-00.txt
Date: Mon, 09 Feb 2004 16:11:12 -0500
Sender: [email-masked]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: Host Identity Protocol (HIP) Rendezvous Mechanisms
	Author(s)	: L. Eggert
	Filename	: draft-eggert-hip-rendezvous-00.txt
	Pages		: 27
	Date		: 2004-2-9
	
This document discusses rendezvous mechanisms for the Host Identity
   Protocol (HIP). Rendezvous mechanisms, such as HIP Rendezvous
   Servers, improve operation when HIP nodes are multi-homed or mobile.
   They can also facilitate communication between HIP and non-HIP nodes.
   Possible rendezvous mechanisms differ in performance, compatibility,
   and impact on the HIP and Internet architectures.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-eggert-hip-rendezvous-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-eggert-hip-rendezvous-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:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-eggert-hip-rendezvous-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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-eggert-hip-rendezvous-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-eggert-hip-rendezvous-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

--------------000702020403060205060002--

--------------ms000800080601010504030205
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

--------------ms000800080601010504030205--