Fwd: Protocol Action: DNS Extensions to Support IP Version 6 to Internet Standard

Bob Hinden <bob.hinden@gmail.com> Fri, 26 May 2017 16:51 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5CA128DF6 for <ipv6@ietfa.amsl.com>; Fri, 26 May 2017 09:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nC_IW6vaTS8f for <ipv6@ietfa.amsl.com>; Fri, 26 May 2017 09:51:11 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE9B9129576 for <ipv6@ietf.org>; Fri, 26 May 2017 09:51:09 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id z52so5072065wrc.2 for <ipv6@ietf.org>; Fri, 26 May 2017 09:51:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:cc:to:message-id; bh=2ZXZSAPtRdNb8QouswV1NEjzrdYadXJ2ZsVil5WJVoE=; b=QlrvnUWa31HkiE3GLlJifRmVeBLdNETh2z0cUcj28lMe1i1D+2njCDIBs9hWl9CUoE qHQ8N699KNHRfPQWs7virCr/BtZL12eFWN43F3jkGcc468vRz4XD/vW05PYMuCW9f5NR qmxRmntQz4aM40hiogZbLKHJxDC1fSgSclr2SWX6V9LtjHgIICSJ0buBGC/od04COraV 429m8T0zBjeKqLuk7tWdAnZ9zfoYhxba4HyBsNj3txqsKSvxoQnGd4R4301Hka1AY2o9 BtSDI6xkvXG2d7vriSfpFKUPHhisM38qjN3Q5OfY4LM2NbaD/pW01tHU/0SZkFQ0WqrD KZUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:cc:to :message-id; bh=2ZXZSAPtRdNb8QouswV1NEjzrdYadXJ2ZsVil5WJVoE=; b=bsDq1b/2Nb2AougBAoWxSY0XhfS8nLka/U3/JsOw25qRZwtg8hDwtlfbrTu2CVpMq8 xYa+64AJNdW6I4ZKlEp0OIlaTBueghmlixlEU73N+2eMyK+7XTZ1MR1fiU5B80DNWVGQ cz/lrZh6ix72vpOXCU4+K8QAqJPiJDxiMOV5t+20r67Htg9+nWPwDAnVQni/9BANVark N7dz8upkF2rbBztsAC+DAuy7BWCvgaPTdurqvdpfcj05Z8+suEeWtQ483nJnfDPJeASg QOCtHox06R3Ydzsne+8SaMbOs4Q52ArhnFRAoFus/hVa5OOc6JkyMzIZ49ZXl4lj0FN0 4bOQ==
X-Gm-Message-State: AODbwcCr1qfJeSmM0dDSRm8v1MDb0oLMGo9R/T+HsoWXy1kaj01CRkT6 p3Hs8LQTJM/KMo6JPQ4=
X-Received: by 10.223.157.29 with SMTP id k29mr2392985wre.156.1495817465310; Fri, 26 May 2017 09:51:05 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:e1e6:d5d8:3c54:56da? ([2601:647:4d01:db10:e1e6:d5d8:3c54:56da]) by smtp.gmail.com with ESMTPSA id e23sm1736293wre.54.2017.05.26.09.51.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 May 2017 09:51:03 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_FC20867C-9302-4012-9788-360E3119B09C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Fwd: Protocol Action: DNS Extensions to Support IP Version 6 to Internet Standard
Date: Fri, 26 May 2017 09:51:02 -0700
References: <149581532913.8648.1739323272734672777.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Message-Id: <BDD054CD-E38E-42C7-AB87-7BDBCBD5D77F@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lc1ZVe06lefeDdOU8w3XsOFRf_U>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2017 16:51:13 -0000

FYI

> Begin forwarded message:
> 
> From: The IESG <iesg-secretary@ietf.org>
> Subject: Protocol Action: DNS Extensions to Support IP Version 6 to Internet Standard
> Date: May 26, 2017 at 9:15:29 AM PDT
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: ipv6-chairs@ietf.org, okolkman@ripe.net, margaret@thingmagic.com, draft-ietf-ipngwg-icmp-v3@ietf.org, The IESG <iesg@ietf.org>, dnsext-chairs@ietf.org, draft-ietf-dnsext-rfc1886bis@ietf.org, rfc-editor@rfc-editor.org
> Reply-To: ietf@ietf.org
> 
> The IESG has approved changing the status of the following document:
> - DNS Extensions to Support IP Version 6
>  (rfc3596) to Internet Standard
> 
> This protocol action is documented at:
> https://datatracker.ietf.org/doc/status-change-icmpv6-dns-ipv6-to-internet-standard/
> 
> A URL of the affected document is:
> https://datatracker.ietf.org/doc/rfc3596/
> 
> Status Change Details:
> 
> RFC4443 "Internet Control Message Protocol (ICMPv6) for the Internet
> Protocol Version 6 (IPv6) Specification" currently has an IETF standards
> status of Draft Standard, which is now an obsolete status. This status
> change requests reclassifying it to Internet Standard.
> 
> (1) There are at least two independent interoperating implementations
>       with widespread deployment and successful operational experience.
> 
> RFC4443 has been widely implemented:
>          https://www.ipv6ready.org/db/index.php/public/?o=4
> 
> (2) There are no errata against the specification that would cause a
>       new implementation to fail to interoperate with deployed ones.
> RFC4443 has 4 errata, none of which would cause new interoperability
>      problems.
> 
> (3) There are no unused features in the specification that greatly
>       increase implementation complexity.
> 
> There are no unused features.
> 
> (4) If the technology required to implement the specification
>       requires patented or otherwise controlled technology, then the
>       set of implementations must demonstrate at least two independent,
>       separate and successful uses of the licensing process.
> 
> N/A
> 
> RFC3596 "DNS Extensions to Support IP Version 6" currently has an IETF
> standards status of Draft Standard, which is now an obsolete status. This
> status change requests reclassifying it to Internet Standard.
> 
> (1) There are at least two independent interoperating implementations
>       with widespread deployment and successful operational experience.
> 
> RFC3596 has been widely implemented:
>          https://www.ipv6ready.org/db/index.php/public/?o=4
> 
> (2) There are no errata against the specification that would cause a
>       new implementation to fail to interoperate with deployed ones.
> 
> There are no errata filed against RFC3596
> 
> (3) There are no unused features in the specification that greatly
>       increase implementation complexity.
> 
> There are no unused features.
> 
> (4) If the technology required to implement the specification
>       requires patented or otherwise controlled technology, then the
>       set of implementations must demonstrate at least two independent,
>       separate and successful uses of the licensing process.
> 
> N/A
> 
> Personnel
> 
>   Suresh Krishnan is the responsible Area Director.
> 
> 
>