IETF Logo Mail Archive

Re: AUTH48 changes to draft-ietf-6man-rfc6434-bis-09

Bob Hinden <bob.hinden@gmail.com> Thu, 20 December 2018 16:25 UTC

Return-Path: <bob.hinden@gmail.com>
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 D5574130EED; Thu, 20 Dec 2018 08:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OlSPtKb7wZhj; Thu, 20 Dec 2018 08:25:20 -0800 (PST)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 7D3F8130E81; Thu, 20 Dec 2018 08:25:20 -0800 (PST)
Received: by mail-wr1-x429.google.com with SMTP id t27so2386379wra.6; Thu, 20 Dec 2018 08:25:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XheGxH5a2FS31NQWaEkGc4Wo+IoFYQ3QEiugvB773L8=; b=Ovox4P0J3X0lI4mrzTicAVlJ4jBy+Rd4/TurBOjp6rtKVA2bmZw4qTWCt0ER6UCYnc 7iUOKnq+tKOVvObPrI/3GJVmkIMoff/cbI1jHLtyiOutrltVVCxt0LRZdvgrnLb/AULU uVRF+X1GUmLIxF+7vNx6kYCcb3DLig+y3wLVJ8UdKr2aA2CaXp56W+T3dfc6GZBTPnMV 2CDIn4MBIll7ZhHeIQ+vsfLuAgOEt8V3QZfa5fLHSkUOPcSSMDY9YC7qPfsinEvuQuKh Hv4Dm9h5v8UUf0GUgzeVNFKnB4T63TWMyghTKkSgnI95iYb1jz1h7AjM2BcHYAwJbzFI GObQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XheGxH5a2FS31NQWaEkGc4Wo+IoFYQ3QEiugvB773L8=; b=BS3jSS6hjK2u6O2xJm9ni5ghbaFvKpoRVE8tQfN8khWGV+o3c6OEgc+aEXvkQ77Vgy h5rExaXDNEWe9n9K3YAXtiC5yERJ8/zvIGVW9okBA9+FHiYdQ5/QwU5gMhyb1zjwRWM9 84xxeukPKjmag2Ym8O47DoeSaVzwZHXK+bE8VUHDom1Q5fLbTX8/CCpqAaDHQ+43wHmi SyCRYEOQK5r5f0WkJIc8xRq6lGP+FIPiH6EJU1NKBILgj+tOzt2t1Iht73jYlmOJahb4 bntY6b6U2KwFA+4VrjGvz/C9Wu3bFWTzM28OpxAG9XNZXGuGOpNmxrx0nwoJtNEEQZEx 1V5g==
X-Gm-Message-State: AA+aEWYg8YDv/Y6dx5aGEhvCiOfsZzAEhw0Ujb+t13yzN6FheWhXkxgw +8bVHs1xtV037ah/mqJZ3PciLRGy
X-Google-Smtp-Source: AFSGD/Ww7Bt69oraNeR8dC4huH/L90GAzi9eV1pqlts1QaCymyn79DPDETQn1UpxGfEwt6ploE0vIg==
X-Received: by 2002:a5d:65ce:: with SMTP id e14mr22415716wrw.150.1545323118959; Thu, 20 Dec 2018 08:25:18 -0800 (PST)
Received: from [10.0.0.50] (c-76-21-112-100.hsd1.ca.comcast.net. [76.21.112.100]) by smtp.gmail.com with ESMTPSA id g129sm7611919wmf.39.2018.12.20.08.25.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Dec 2018 08:25:17 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <34AFB9BE-4FF3-4116-BBE9-D3ED49912ABA@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4F4ADD23-8B5B-4AB3-A416-DE67CE670BCE"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: AUTH48 changes to draft-ietf-6man-rfc6434-bis-09
Date: Thu, 20 Dec 2018 08:25:16 -0800
In-Reply-To: <8A9ACE0F-8EF7-48D7-AB1A-309D05A350CC@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org>, draft-ietf-6man-rfc6434-bis@ietf.org
To: Suresh Krishnan <suresh.krishnan@gmail.com>
References: <8A9ACE0F-8EF7-48D7-AB1A-309D05A350CC@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/uQYT-V_vwnButUpLjFOdGy_lN6o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Dec 2018 16:25:31 -0000

Suresh,

> On Dec 19, 2018, at 10:20 PM, Suresh Krishnan <suresh.krishnan@gmail.com> wrote:
> 
> Hi all,
>  There are two proposed (non-editorial) changes to be made to draft-ietf-6man-rfc6434-bis-09 during the AUTH48 period and I would like to check with the WG if anyone has objections to these changes. I personally think that these are reasonable changes to make.  If I do not hear any objections by end of day December 27th 2018 (AOE), I will approve these changes and send this along the RFC publication path.
> 
> Change 1) Text change in Section 5.4.
> 
> Old:
> Neighbor Discovery SHOULD be supported. RFC 4861 states:
> 
> New:
> Neighbor Discovery MUST be supported with the noted exceptions below.
> RFC 4861 states:
> 
> Change 2) New text in Section 5.4.
> 
> OLD:
> 
> <blank>
> 
> NEW:
> 
> As per RFC 6980, hosts MUST NOT employ IPv6 fragmentation for sending any of the following Neighbor Discovery and SEcure Neighbor Discovery messages: Neighbor Solicitation, Neighbor Advertisement, Router Solicitation, Router Advertisement, Redirect, or Certification Path Solicitation.

I think we should make both changes.

Regarding the fragmentation of ND messages, RFC6980 say it applies to all nodes, not just Hosts.   This text should be consistent with that.  Might also add something like “See RFC 6980 for details and motivation”.

Thanks,
Bob

v2.23.0 | Report a Bug | By Email