Re: Updates to RFC6434

Timothy Winters <twinters@iol.unh.edu> Mon, 30 October 2017 19:46 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 7DD1413F988 for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 12:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 bgGBp4gyb1yQ for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 12:46:40 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 CAD5013FAEB for <ipv6@ietf.org>; Mon, 30 Oct 2017 12:46:28 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id q83so17659611qke.6 for <ipv6@ietf.org>; Mon, 30 Oct 2017 12:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MaDfbuMwMidCdolofvFiO9zo9f0/09y7EK1BPDGk+Aw=; b=gkhNRMBlXXyW9Bn92kjeyZ2OLYLuUGbS0jcO/BBwza1vORyqr7s5e8OwzZ4juz1WD8 wuzS3ivNZQH20nqqKWTR/kuv1OZjB8xG1IcUmfkQLDdRzGGIsRVM4sbMUikelmu5BG7X JPmb2Qt0dYAC6Vmz5YplXz0AFVXmjpskoP6+0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MaDfbuMwMidCdolofvFiO9zo9f0/09y7EK1BPDGk+Aw=; b=LQyBWQSXWzCzNzOdPyu1ArX5s+V0iGkJuIaxbgofHbB65bGLOFNk56Ffa8qIdRG7bE DfWuBfqgN0FB4UAzWt6Ws5OgyW+g88wRRRJFL2GacR+ZhhGqn+sUr/ykAgZJEivCwG7x aN8pCD0k9Edsc49h55akDtRF9CGETldwG6REll1jWkchIIWv2V8TYY0H9K8nf0flV38p IJSeWmZgC4xGYBp2MCqich08jdWLf/OC3NbR9BzcDoTDDIHrZNH4W7LOH94T7fHPcrpW Mg/jDwUgfnkP/bcKtyhTOApm/Dw7VkEjI3pNBYqNqBb16Yj+GKAzCIGHjJKVIN+qdCLe qsMg==
X-Gm-Message-State: AMCzsaWcoLbhzYd5OJuhQYSLcnm5hJO1Ifx0ftNmTsS7NXSsZOA34T9u X3Tby9EC/8Tk8/NQ7FpdbVKZhp9F1fF4t0tykhviqQ==
X-Google-Smtp-Source: ABhQp+T5Xw+AX3AfUGX3+9JR5bA0YRT8A+JFm73Ko8FG1Y2ycEGR30EsCbhY68ZpYS9G3+8lYXv0Z/45QJWBeD8EvWE=
X-Received: by 10.233.220.196 with SMTP id q187mr14840041qkf.344.1509392787878; Mon, 30 Oct 2017 12:46:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.40.8 with HTTP; Mon, 30 Oct 2017 12:46:06 -0700 (PDT)
In-Reply-To: <647efa67a24f4511ab1968ec6c9227ac@XCH15-06-08.nw.nos.boeing.com>
References: <CAOSSMjUVCSBjbYu3bc7DU+edz2+0+RvU_AMi4FNn2n2075kk9g@mail.gmail.com> <647efa67a24f4511ab1968ec6c9227ac@XCH15-06-08.nw.nos.boeing.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Mon, 30 Oct 2017 15:46:06 -0400
Message-ID: <CAOSSMjUZcNwk2_UhBfD63Dz2Er9qrNmK9Qb-+z0mRtEPgs+9Gw@mail.gmail.com>
Subject: Re: Updates to RFC6434
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c044a6ef2d613055cc8e4b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZaTwNW3wmRAhmIaCUFHi0gmiSto>
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 19:46:43 -0000

Hi Fred,

I thought we decided we didn't want to point to the historic IPv4 text in
that.  Can you remind me were you wanted that text?

~Tim

On Mon, Oct 30, 2017 at 3:37 PM, Templin, Fred L <Fred.L.Templin@boeing.com>;
wrote:

> We talked about adding an informative reference to RFC1122. Can
>
> you please add that?
>
>
>
> Fred
>
>
>
> *From:* ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *Timothy Winters
> *Sent:* Monday, October 30, 2017 6:43 AM
> *To:* 6man WG <ipv6@ietf.org>;
> *Subject:* Updates to RFC6434
>
>
>
> 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
>



-- 

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