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

[David Farmer <[e-mail]>]

On Thu, Dec 20, 2018 at 10:25 AM Bob Hinden <[e-mail]> wrote:

> Suresh,
>
> > On Dec 19, 2018, at 10:20 PM, Suresh Krishnan <[e-mail]>
> 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”.
>

+1

-- 
===============================================
David Farmer               Email:[e-mail]
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: [phone]
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================