[sidr] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC (fwd)

Sandra Murphy <Sandra.Murphy@sparta.com> Mon, 06 June 2011 16:48 UTC

Return-Path: <Sandra.Murphy@cobham.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4813911E8178 for <sidr@ietfa.amsl.com>; Mon, 6 Jun 2011 09:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqFm0FEWbuCm for <sidr@ietfa.amsl.com>; Mon, 6 Jun 2011 09:48:15 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9AB11E8177 for <sidr@ietf.org>; Mon, 6 Jun 2011 09:48:14 -0700 (PDT)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.13.5/8.13.5) with ESMTP id p56GmDfZ015856; Mon, 6 Jun 2011 11:48:13 -0500
Received: from nemo.columbia.ads.sparta.com (nemo.columbia.sparta.com [157.185.80.75]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id p56GmDiP031206; Mon, 6 Jun 2011 11:48:13 -0500
Received: from SMURPHY-LT.columbia.ads.sparta.com ([157.185.81.109]) by nemo.columbia.ads.sparta.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 6 Jun 2011 12:48:13 -0400
Date: Mon, 06 Jun 2011 12:48:13 -0400
From: Sandra Murphy <Sandra.Murphy@sparta.com>
To: draft-ietf-sidr-iana-objects@tools.ietf.org, sidr@ietf.org
Message-ID: <Pine.WNT.4.64.1106061239150.7792@SMURPHY-LT.columbia.ads.sparta.com>
X-X-Sender: sandy@nemo.columbia.sparta.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-OriginalArrivalTime: 06 Jun 2011 16:48:13.0790 (UTC) FILETIME=[86C18FE0:01CC2469]
Subject: [sidr] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC (fwd)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 16:48:16 -0000

I'm curious.

Could the authors of draft-ietf-sidr-iana-objects comment on whether the 
action mentioned below would have any effect on the rules for IANA issued 
objects wrt RFC3068 prefixes?

--Sandy, speaking as wg chair

---------- Forwarded message ----------
Date: Mon, 6 Jun 2011 09:23:26 -0700
From: The IESG <iesg-secretary@ietf.org>
Reply-To: ietf@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>
Cc: v6ops@ietf.org
Subject: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move
     Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to
     Informational RFC


The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document:
- 'Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to
    Historic status'
   <draft-ietf-v6ops-6to4-to-historic-04.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-06-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


    Experience with the "Connection of IPv6 Domains via IPv4 Clouds
    (6to4)" IPv6 transitioning mechanism has shown that the mechanism is
    unsuitable for widespread deployment and use in the Internet.  This
    document requests that RFC3056 and the companion document "An Anycast
    Prefix for 6to4 Relay Routers" RFC3068 are moved to historic status.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce