From 54d94335ca6ee024192e2874d345ad4d9609a6f4 Mon Sep 17 00:00:00 2001 From: Othmar Gsenger Date: Wed, 23 Jan 2008 15:30:48 +0000 Subject: draft fixed version number --- draft-gsenger-secure-anycast-tunneling-protocol-01.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'draft-gsenger-secure-anycast-tunneling-protocol-01.html') diff --git a/draft-gsenger-secure-anycast-tunneling-protocol-01.html b/draft-gsenger-secure-anycast-tunneling-protocol-01.html index 72e0ad3..11a369e 100644 --- a/draft-gsenger-secure-anycast-tunneling-protocol-01.html +++ b/draft-gsenger-secure-anycast-tunneling-protocol-01.html @@ -146,7 +146,7 @@ Internet-DraftJanuary 23, 2008 Expires: July 26, 2008  -


secure anycast tunneling protocol (SATP)
draft-gsenger-secure-anycast-tunneling-protocol-00

+


secure anycast tunneling protocol (SATP)
draft-gsenger-secure-anycast-tunneling-protocol-01

Status of this Memo

@@ -608,7 +608,7 @@ References [2] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). [3] -Perkins, C., “IP Encapsulation within IP,” RFC 2003, October 1996 (TXT, XML). +Perkins, C., “IP Encapsulation within IP,” RFC 2003, October 1996 (TXT, HTML, XML).


-- cgit v1.2.3