Updates to RFC6434

Timothy Winters <twinters@iol.unh.edu> Mon, 30 October 2017 13:43 UTC

Return-Path: <twinters@iol.unh.edu>
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 D327113F9EE for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 06:43:08 -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, 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 (1024-bit key) header.d=iol.unh.edu
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 kpWHtSgLi1hV for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 06:43:06 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 277EA13F9EC for <ipv6@ietf.org>; Mon, 30 Oct 2017 06:43:06 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id h4so16363019qtk.8 for <ipv6@ietf.org>; Mon, 30 Oct 2017 06:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:from:date:message-id:subject:to; bh=CXR46KxWvRPl42BuFv9qzSRxU5T4q534aGYtVI7USyQ=; b=FnZtasA8yyqXVgwB67R3izkSDV+PMkCY+/5NEcWTF7ZY9i90EnYhuhdRbzBNMwYKvZ ZOFuPEIXtEYaXiy3JEnhUmoIvzAgUan3+bM3OESaLMrtEpnBVgW+0d7h5AaXEbRTaNqc o/Msh+qkXFmcs4ik9L763mxjdn4+AHkNMtn9Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CXR46KxWvRPl42BuFv9qzSRxU5T4q534aGYtVI7USyQ=; b=eBXFBqpmi0dGihWHGDhlvoW9ACVTOlTrlYXr9YwcnfCNtoQo/XFJIRHjY7AP6eFx+C vDgbQFoSNQhp26Fm8lkNSr9EC8FKQikaLL7DX4hxtC2aiMasR9aqRAeeK11gPlz5xigk ey3xziQ7ids4GU7PHdYvN5LBaRI7TUPfdycgjg0ctH4w8D83TccZGo0MlS5rPRem+FJ+ X8wjwhbzK/HqUERtWnXdGBC6eV0JsWOeOp86p7EzQurpIlcVTFZ5aShbZ07tFD7xsY5q 6H5/6eC0LL4ONeUm6/BKjV5xCjPaspzYbQkagaBOq/E1hhqc6SOeqppLDt5gpNL9UP3G XqDQ==
X-Gm-Message-State: AMCzsaUHVi2xAg0+NLJxKcA4ANyh2yY/YESvaAOr7qT5Hsr9LaremCsz +2KaIiwNpY1dhEEWvW9C3COgr8Ov56FPVpO2Lx3FA7bO
X-Google-Smtp-Source: ABhQp+SM07XlvZ7KvJfxloNggRJKLGk19wnBPGGjkisr4L1melv9yJmKGP6ITiq4Ci+/tX+kRgXD9M6eI3Nwekn6DdY=
X-Received: by 10.237.34.201 with SMTP id q9mr14010530qtc.198.1509370984383; Mon, 30 Oct 2017 06:43:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.40.8 with HTTP; Mon, 30 Oct 2017 06:42:43 -0700 (PDT)
From: Timothy Winters <twinters@iol.unh.edu>
Date: Mon, 30 Oct 2017 09:42:43 -0400
Message-ID: <CAOSSMjUVCSBjbYu3bc7DU+edz2+0+RvU_AMi4FNn2n2075kk9g@mail.gmail.com>
Subject: Updates to RFC6434
To: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a1137b67a5c0ae2055cc3d14d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qwryPlYsZB8L-zcAiunySaL62fY>
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: Mon, 30 Oct 2017 13:43:09 -0000

We have posted an updated version of 6434bis, with the following changes
since Prague:

   - Text on EH processing
   - Noted that RFC4191 is a MUST, but a SHOULD for Type C node
   - Updated RFC references (8200, 8201, 8221, 8247)
   - Added note on RFC 7772 for power consumption
   - Added ‘Why /64?’ reference; RFC 7421
   - Removed jumbogram text
   - Added reference to draft-ietf-v6ops-unique-ipv6-prefix-per-host
   - For 3GPP, added ‘snapshot’ comment on RFC7066
   - Added RFC8028 as a SHOULD (for Section 5.5 from RFC 6724)
   - Removed ATM over IPv6
   - Added reference to RFC8064
   - Added MUST for BCP 198, and ref to draft-ietf-v6ops-ipv6rtr-reqs
   - Added text on avoiding 1280 MTU for UDP (inc. DNS) traffic

We'll be sending some additional questions to the list later this week to
hopefully get this document ready for working group last call.

~Tim, Tim and John



---------- Forwarded message ----------
From: <internet-drafts@ietf.org>;
Date: Mon, Oct 30, 2017 at 9:36 AM
Subject: I-D Action: draft-ietf-6man-rfc6434-bis-02.txt
To: i-d-announce@ietf.org
Cc: ipv6@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IPv6 Maintenance WG of the IETF.

        Title           : IPv6 Node Requirements
        Authors         : Tim Chown
                          John Loughney
                          Timothy Winters
        Filename        : draft-ietf-6man-rfc6434-bis-02.txt
        Pages           : 40
        Date            : 2017-10-30

Abstract:
   This document defines requirements for IPv6 nodes.  It is expected
   that IPv6 will be deployed in a wide range of devices and situations.
   Specifying the requirements for IPv6 nodes allows IPv6 to function
   well and interoperate in a large number of situations and
   deployments.

   This document obsoletes RFC 6434, and in turn RFC 4294.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6434-bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bis-02
https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc6434-bis-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-rfc6434-bis-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR