From nobody Mon Oct 27 19:00:57 2014 Return-Path: X-Original-To: sunset4@ietfa.amsl.com Delivered-To: sunset4@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD5B1A034F for ; Mon, 27 Oct 2014 19:00:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ctLPhXRLY0S for ; Mon, 27 Oct 2014 19:00:54 -0700 (PDT) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E887B1A0373 for ; Mon, 27 Oct 2014 19:00:53 -0700 (PDT) Received: by mail-qg0-f47.google.com with SMTP id i50so4907957qgf.20 for ; Mon, 27 Oct 2014 19:00:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0fA8Ua33k1yZFeituzkYdruiebazWk5mLkiIWinBsag=; b=WHfhVaM9+d5swXc0uxxM5giWf2qkdT3Q1Yv8Klr30ksQK/xiHdYti2mzBr6wEcxTCy zTY0W0Ctd7G5xCusRpeWGCP5fLlASENW4RnCfxWfEbR3o4gbuCpF/s6rIwHqGluwJdjK ytCMdUu9DY5LGYMIoJMvwtwtZy8lvYerGOcgANT/cSPZG8w5OGFli/ZDGPO6mivSbp+t 4aayOmszQ0lZrYmHAm7CDG8aylmDo4oCh8S25VESl2lAbAN7cD62CHEBfMIjlwc8VXq9 DvMDnnWLr/0D7YBiFlAqLqAQrLLZJ1UWzSKdEu90IfU3jxfJLgU5l3I/UamYaxD7Rs7A KGlw== MIME-Version: 1.0 X-Received: by 10.224.13.2 with SMTP id z2mr504607qaz.18.1414461653022; Mon, 27 Oct 2014 19:00:53 -0700 (PDT) Received: by 10.140.41.228 with HTTP; Mon, 27 Oct 2014 19:00:52 -0700 (PDT) In-Reply-To: <20141027230057.30516.93071.idtracker@ietfa.amsl.com> References: <20141027230057.30516.93071.idtracker@ietfa.amsl.com> Date: Tue, 28 Oct 2014 10:00:52 +0800 Message-ID: From: Davey Song To: "sunset4@ietf.org" Content-Type: multipart/alternative; boundary=089e0115ef4c608183050672045c Archived-At: http://mailarchive.ietf.org/arch/msg/sunset4/P9s3LL1rv_w5YA3IHVNeKAEKQCo Subject: [sunset4] Fwd: New Version Notification for draft-song-sunset4-ipv6only-dns-00.txt X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 02:00:55 -0000 --089e0115ef4c608183050672045c Content-Type: text/plain; charset=UTF-8 Hi folks, I have just post a new draft on IPv6-only DNS development. Comments are welcome!! A new version of I-D, draft-song-sunset4-ipv6only-dns-00.txt has been successfully submitted by Linjian Song and posted to the IETF repository. Name: draft-song-sunset4-ipv6only-dns Revision: 00 Title: Considerations on IPv6-only DNS Development Document date: 2014-10-27 Group: Individual Submission Pages: 8 URL: http://www.ietf.org/internet-drafts/draft-song-sunset4-ipv6only-dns-00.txt Status: https://datatracker.ietf.org/doc/draft-song-sunset4-ipv6only-dns/ Htmlized: http://tools.ietf.org/html/draft-song-sunset4-ipv6only-dns-00 Abstract: Deployment of IPv6-only networks are impacted by assumptions of IPv4-only or dual-stack transition scenarios. For example, these assumptions are in the operations of DNS. This memo is problem statement and hopes to eventually propose a mitigation technique. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --089e0115ef4c608183050672045c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi folks, I have just post a new draft on IPv6-only DNS de= velopment. Comments are welcome!!=C2=A0

=
A new version of I-D, draft-song-sunset4-i= pv6only-dns-00.txt
has been successfully submitted by Linjian Song and posted to the
IETF repository.

Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-song-sunset4-ipv6only-d= ns
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Considerations on IPv6-only DNS De= velopment
Document date:=C2=A0 2014-10-27
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://www.ietf.org/internet-drafts/draft-song-sunset4-ipv6only-dns-00.txt=
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datat= racker.ietf.org/doc/draft-song-sunset4-ipv6only-dns/
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0http://tools.ietf.org/= html/draft-song-sunset4-ipv6only-dns-00


Abstract:
=C2=A0 =C2=A0Deployment of IPv6-only networks are impacted by assumptions o= f
=C2=A0 =C2=A0IPv4-only or dual-stack transition scenarios.=C2=A0 For exampl= e, these
=C2=A0 =C2=A0assumptions are in the operations of DNS.=C2=A0 This memo is p= roblem
=C2=A0 =C2=A0statement and hopes to eventually propose a mitigation techniq= ue.




Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--089e0115ef4c608183050672045c--