Re: Updates to RFC6434

Timothy Winters <twinters@iol.unh.edu> Mon, 30 October 2017 14:06 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 B379413F9F3 for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 07:06:40 -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 yX16ipNrT_pl for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 07:06:38 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 4589513F444 for <ipv6@ietf.org>; Mon, 30 Oct 2017 07:06:38 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id o187so16246078qke.7 for <ipv6@ietf.org>; Mon, 30 Oct 2017 07:06:38 -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=xySWxliY1sxB9EAtDWwncRdCxapI1dZ82joIiHw8094=; b=EWjHv1fSk62ZZuJXtrommhy9gnELrZxGnRq1nHNxS6RxYBe3+TcgjEiSMZxSMD0xYH lSZpnhuusxrneu0mis+B2XDIVQEldxq6EDYCDJ/xT+obTt/iY6hgYZP7nhs9H0bih+Av BA+Xpo45rBERxG9A5ggNdDCokdCf9ATC5DhRU=
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=xySWxliY1sxB9EAtDWwncRdCxapI1dZ82joIiHw8094=; b=ClZbiBWPVIeFgOpcLXsoc3Dkgz7T4NN3KihV9oUNZlhOzlStqjkkuvNzxElIMlwIZz 65W2ExP5cYP4pK4/zRNvut7v5xinQvUzxa/Gy/mD7RXmLe/FALMB2N7E8fjrKCgrTmuK HogOijfSBzfBLPlog7nbHR24ay29tFuOt+b0UnAsHhBgrzdNx4v2pDb4isxbH5iNAcGq ir0bALwNzbYpnv61c5AuwnoqRxWgIWU1RepUShI/eR8cwj8R/V+qyPVMG5oOep9Yb2qf NQBjdbVJeUguRwckkKTWTqkatWluEvaRyW16q1HsEubuDLictEcnu2ufb/Uirw4bwHSK SY0A==
X-Gm-Message-State: AMCzsaWuV5A69QpbQpjnr5bfI20uAR/GZnUlL4TGbn9fQ2qLA1lFbfsU UssTyiys6KPTjwQwRjRl1b3YVg4ApfbYpkkMVShbEg==
X-Google-Smtp-Source: ABhQp+TcxGcDwkul5a8Dy7hvjkftetQH3rpGzYx4voOB69kPiDX80Y7KPLTEzeSWY6Lfxg/1UQSwoRGf/gBibF7+UyQ=
X-Received: by 10.55.60.129 with SMTP id j123mr14026923qka.121.1509372397297; Mon, 30 Oct 2017 07:06:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.40.8 with HTTP; Mon, 30 Oct 2017 07:06:16 -0700 (PDT)
In-Reply-To: <AM0PR0102MB3298C9D72FE78B297A2264A280590@AM0PR0102MB3298.eurprd01.prod.exchangelabs.com>
References: <CAOSSMjUVCSBjbYu3bc7DU+edz2+0+RvU_AMi4FNn2n2075kk9g@mail.gmail.com> <AM0PR0102MB3298C9D72FE78B297A2264A280590@AM0PR0102MB3298.eurprd01.prod.exchangelabs.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Mon, 30 Oct 2017 10:06:16 -0400
Message-ID: <CAOSSMjXUe2nFPJJ1v0SXtpjEjFCdq0dJG122g3REgxemE-3xPw@mail.gmail.com>
Subject: Re: Updates to RFC6434
To: "Turner, Randy" <Randy.Turner@landisgyr.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a114a207a934389055cc42578"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QCqmD3OTmdOH_CKglBS6qk6x7V4>
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 14:06:40 -0000

Hi Randy,

The original RFC 6434 has this same text.   In this case it's calling out
for the purpose of DAD that you have to support sending NA and NS as
defined in RFC 4861.   The rest of the 4861 (Router Discovery, Address
Resolution, etc...) are covered under the SHOULD at the top of the Section
5.4.

~Tim

On Mon, Oct 30, 2017 at 9:58 AM, Turner, Randy <Randy.Turner@landisgyr.com>;
wrote:

> Hi Guys,
>
>
>
>    How should readers of 6434bis reconcile the following two statements
> from section 5.4 ?
>
>
>
>    Neighbor Discovery is defined in [RFC4861]; the definition was
>
>    updated by [RFC5942].  Neighbor Discovery SHOULD be supported.
>
>
>
> --
>
>    All nodes MUST support the sending and receiving of Neighbor
>
>    Solicitation (NS) and Neighbor Advertisement (NA) messages.  NS and
>
>    NA messages are required for Duplicate Address Detection (DAD).
>
>
>
> Thanks,
>
> Randy
>
>
>
>
>
> *From:* ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *Timothy Winters
> *Sent:* Monday, October 30, 2017 9: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
>
> --------------------------------------------------------------------
> 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