Re: Updates to RFC6434

Tim Chown <Tim.Chown@jisc.ac.uk> Mon, 30 October 2017 20:27 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 8124013F5C8 for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 13:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=jisc.ac.uk
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 ayeLZjoNBFAC for <ipv6@ietfa.amsl.com>; Mon, 30 Oct 2017 13:27:47 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D28D13F5AC for <ipv6@ietf.org>; Mon, 30 Oct 2017 13:27:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1509395265; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=44g7VvQpWBZnZcKh1HyPK7NaVJcESTDC9+1IVUwrLXM=; b=BAOJpCfnxMYXSbywD+qKW7pYY6j1p5gVXJxK0mLue8G3hdHp/wUQu8V8Az3Bl7PzevxRVGbr7ucxYMMc9OmSISrf/R6RTdNdRbDVufk9jzegJNHul2M3XRclhDiVaZJzJUmMG9IvzVrjQ+2RuP9I7QnhP2m91taIFXyhe8ZPlgs=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0243.outbound.protection.outlook.com [213.199.154.243]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-20-afgKiG18OFSXw6aUQ5d25Q-1; Mon, 30 Oct 2017 20:27:42 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.4; Mon, 30 Oct 2017 20:27:40 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23%14]) with mapi id 15.20.0197.011; Mon, 30 Oct 2017 20:27:40 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
CC: Timothy Winters <twinters@iol.unh.edu>, 6man WG <ipv6@ietf.org>
Subject: Re: Updates to RFC6434
Thread-Topic: Updates to RFC6434
Thread-Index: AQHTUYUUiFTgLcDqT0uoRJU+iPmMB6L8yeuAgAACfgCAAAWuAIAABeuA
Date: Mon, 30 Oct 2017 20:27:40 +0000
Message-ID: <F606F642-2DF5-4D82-B55F-77549A8E8770@jisc.ac.uk>
References: <CAOSSMjUVCSBjbYu3bc7DU+edz2+0+RvU_AMi4FNn2n2075kk9g@mail.gmail.com> <647efa67a24f4511ab1968ec6c9227ac@XCH15-06-08.nw.nos.boeing.com> <CAOSSMjUZcNwk2_UhBfD63Dz2Er9qrNmK9Qb-+z0mRtEPgs+9Gw@mail.gmail.com> <27453115328b4e4f88c79bc3c989ad55@XCH15-06-08.nw.nos.boeing.com>
In-Reply-To: <27453115328b4e4f88c79bc3c989ad55@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:718e:a4e1:1d41:6dad]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 20:+jrfnh8B6HAxYRFiBegDnJLg6HRm45P11myxb24OrZBQZQ9rSoX5oedfeeoRUFemYtP8s3/+k5/xKmgo8KnCqvuRtbJpo81M/J9c6WuPlz3IOU29MntB0561GbljKUOD+CQHFk7+jBXsYt2cXPhf0sdxu2iSrPFCyhmIcm9RJeI=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: fbe2e5c2-5c87-4ecd-4459-08d51fd4ab42
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603238); SRVR:AM3PR07MB1138;
x-ms-traffictypediagnostic: AM3PR07MB1138:
x-exchange-antispam-report-test: UriScan:(278428928389397)(120809045254105)(39337521807258);
x-microsoft-antispam-prvs: <AM3PR07MB1138AF60DD891F9DF8329A00D6590@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231020)(100000703101)(100105400095)(6041248)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123564025)(20161123555025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1138;
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(346002)(376002)(199003)(377424004)(189002)(24454002)(54906003)(72206003)(966005)(478600001)(4001150100001)(97736004)(25786009)(2906002)(10710500007)(316002)(786003)(14454004)(8666007)(53366004)(6306002)(53936002)(99286003)(1720100001)(4326008)(53546010)(53376002)(6246003)(57306001)(93886005)(102836003)(6116002)(6512007)(5660300001)(81156014)(81166006)(86362001)(101416001)(76176999)(8936002)(50986999)(50226002)(305945005)(6916009)(68736007)(83716003)(7116003)(561944003)(6506006)(3660700001)(105586002)(7736002)(82746002)(6486002)(6436002)(7110500001)(42882006)(189998001)(229853002)(74482002)(5250100002)(2420400007)(8676002)(2950100002)(2900100001)(33656002)(106356001)(15650500001)(3280700002)(36756003)(493534005); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <E49AB77514883446B93EBC1E6EE9C130@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: fbe2e5c2-5c87-4ecd-4459-08d51fd4ab42
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2017 20:27:40.8786 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: afgKiG18OFSXw6aUQ5d25Q-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QWJzD4Pev15dZUZNZEUpDOiL2WU>
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 20:27:50 -0000

That was a ‘could’; I think we subsequently agreed it wasn’t necessary, for the reason Tim mentioned?

Tim

> On 30 Oct 2017, at 20:06, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> Hi Tim,
>  
> I am referring to Tim Chown’s proposed resolution to my original comment:
>  
> https://www.ietf.org/mail-archive/web/ipv6/current/msg28394.html
>  
> Tim’s proposal was to cite RFC1122 in the intro, which I agree would be
> appropriate.
>  
> Thanks - Fred
>  
> From: Timothy Winters [mailto:twinters@iol.unh.edu] 
> Sent: Monday, October 30, 2017 12:46 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: 6man WG <ipv6@ietf.org>
> Subject: Re: Updates to RFC6434
>  
> 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
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------