At IESG's recommendation and with the support of the authors of 3627 and 6164, 
I put together a quick one-pager making 3627 historic. I think this one can 
move through quickly, but since the other documents went through 6man, I 
thought it made sense to ask for WG adoption of this document.

http://tools.ietf.org/html/draft-george-6man-3627-historic-00

Thanks,

Wes George

-----Original Message-----
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org]
Sent: Monday, October 03, 2011 3:15 PM
To: George, Wes
Cc: George, Wes
Subject: New Version Notification for draft-george-6man-3627-historic-00.txt

A new version of I-D, draft-george-6man-3627-historic-00.txt has been 
successfully submitted by Wesley George and posted to the IETF repository.

Filename:        draft-george-6man-3627-historic
Revision:        00
Title:           RFC3627 to Historic status
Creation date:   2011-10-03
WG ID:           Individual Submission
Number of pages: 4

Abstract:
   This document moves RFC3627 to HISTORIC status, as it has been
   superseded by RFC6164.




The IETF Secretariat

This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to