IETF Logo Mail Archive

Re: RFC6434bis open issue - RFC4191 text

Tim Chown <Tim.Chown@jisc.ac.uk> Tue, 07 November 2017 19:25 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 D0C0E126BF3 for <ipv6@ietfa.amsl.com>; Tue, 7 Nov 2017 11:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 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] 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 M_QOzKp_hbrO for <ipv6@ietfa.amsl.com>; Tue, 7 Nov 2017 11:25:51 -0800 (PST)
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 AFDCD12421A for <ipv6@ietf.org>; Tue, 7 Nov 2017 11:25:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1510082749; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=oihLE3fzrBLfzo3KwLj2IQeY2q2O8vLpj7wjpT+2bDY=; b=LUbHayiN2x/wPaA5xtI9Ej1IDtwnthIUoEk6+MQv65h5u5AnQOQ/ZVTXfgBVlEJgETo/tTgPD8p4gjNkQheMU4ggErQyO0PeGTSH/blwAdWFUkcPgTC70xeZPsy82n7axeeVOa+bYHZkXBVhAugqjX9wKkxMMQR63lHFti54B6I=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0184.outbound.protection.outlook.com [213.199.154.184]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-134-06uSDWwzPvGhJx6cBPNEBg-1; Tue, 07 Nov 2017 19:25:46 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Tue, 7 Nov 2017 19:25:45 +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.0218.005; Tue, 7 Nov 2017 19:25:45 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: 6man WG <ipv6@ietf.org>
Subject: Re: RFC6434bis open issue - RFC4191 text
Thread-Topic: RFC6434bis open issue - RFC4191 text
Thread-Index: AQHTV75EJ9Vd3jxnpkmfKsh/gF+IgqMJSsKAgAACKgA=
Date: Tue, 07 Nov 2017 19:25:45 +0000
Message-ID: <FFD39517-1330-4CAD-856B-78F3CCE234A9@jisc.ac.uk>
References: <4FF47B5B-247F-4361-838C-2E50BD642ED3@jisc.ac.uk> <27940d72-293a-0486-ab23-ae816566adb2@gmail.com>
In-Reply-To: <27940d72-293a-0486-ab23-ae816566adb2@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.4.7)
x-originating-ip: [2001:a88:d510:1101:edda:61ec:7313:b139]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 20:K1/5uPdtBl9m6PbBERgYz7DYPWT97io0IDKEtwjAcBLTc3DgoDPCFJO2P41fr0zMRccdeOCeTTkR0jr+fWUQjxiJxmaJ876q9j8w1STz2t5x4xT0HsZghJaCboX25uSAjgOcnichChNdHOlPlIvko/yb0WOz2a502vZMJ1g6QKQ=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 620a16f5-a7ba-4fac-e54b-08d5261557f5
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:AM3PR07MB1140;
x-ms-traffictypediagnostic: AM3PR07MB1140:
x-exchange-antispam-report-test: UriScan:;
x-microsoft-antispam-prvs: <AM3PR07MB11403973F093ABD63684B8B8D6510@AM3PR07MB1140.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)(3231021)(3002001)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(6041248)(20161123560025)(20161123555025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123562025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1140;
x-forefront-prvs: 0484063412
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(376002)(346002)(24454002)(189002)(199003)(53546010)(6246003)(42882006)(3280700002)(316002)(97736004)(86362001)(81166006)(81156014)(36756003)(8936002)(8676002)(5660300001)(39060400002)(6916009)(83716003)(2950100002)(5250100002)(14454004)(57306001)(3660700001)(82746002)(786003)(2906002)(6436002)(2900100001)(50226002)(305945005)(106356001)(6506006)(68736007)(229853002)(99286004)(5890100001)(6486002)(74482002)(6512007)(101416001)(50986999)(4326008)(25786009)(72206003)(6116002)(102836003)(189998001)(53936002)(478600001)(33656002)(76176999)(105586002)(7736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <BCFE57F7A564F94796C60E71FE1A90EF@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 620a16f5-a7ba-4fac-e54b-08d5261557f5
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Nov 2017 19:25:45.4225 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1140
X-MC-Unique: 06uSDWwzPvGhJx6cBPNEBg-1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1g9V5Q0wcOBt8Rx-w5jUAM9VLVc>
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: Tue, 07 Nov 2017 19:25:53 -0000

> On 7 Nov 2017, at 19:17, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 08/11/2017 00:48, Tim Chown wrote:
>> Hi,
>> 
>> TimW and I would like to get some list feedback on some open issues in the draft in advance of the Singapore WG session.
>> 
>> The first topic is whether the text on RFC4191 is now acceptable, i.e.:
>> 
>> — snip —
>> 
>> 5.9.  Default Router Preferences and More-Specific Routes - RFC 4191
>> 
>>   "Default Router Preferences and More-Specific Routes" [RFC4191]
>>   provides support for nodes attached to multiple (different) networks,
>>   each providing routers that advertise themselves as default routers
>>   via Router Advertisements.  In some scenarios, one router may provide
>>   connectivity to destinations the other router does not, and choosing
>>   the "wrong" default router can result in reachability failures.  In
>>   order to resolve this scenario IPv6 Nodes MUST implement [RFC4191]
>>   and SHOULD implement Type C host role.
>> 
>> — snip —
>> 
>> Any comments welcomed.  
>> 
>> (As a nit, I can see we should add "the" before "Type C”.)
> 
> I already mentioned this in my comments a couple of weeks ago,
> and Tim W replied:
> 
>>> I suggest that the last phrase should clarify that "Type C" is defined
>>> in RFC 4191, because as written that is not obvious.
>>> 
>> We can clarify that in the next revision.

Agreed Brian, sorry we missed it last time round.

Tim

v2.23.0 | Report a Bug | By Email