Re: REMINDER: 6man w.g. last call for <draft-ietf-6man-maxra-01>

[Lorenzo Colitti <[e-mail]>]

I find section 3 (which provides guidance on how packet loss impacts
reliability, and how much redundancy to use) very useful.

Section 4 (which is the actual standards update) needs to be worded in more
detail. For example, it should ensure that 0 values continue to be valid
and have the same meaning as before the update. (At least to me, a literal
reading of the current text suggests that 0 is no longer a valid value
for AdvDefaultLifetime.) Perhaps a better approach would be to simply say
that the 1800 and 9000 values specified in section 6.2.1 or RFC4861 are
hereby replaced by 65535

Given that the text allows MaxRtrAdvInterval to be up to 65535, should
the MaxRtrAdvInterval be bounded to 65534 (not 65535) to ensure that the RA
arrives before the timer expires?

On Thu, Jan 5, 2017 at 1:39 AM, Bob Hinden <[e-mail]> wrote:

> FYI
>
> > Begin forwarded message:
> >
> > From: Bob Hinden <[e-mail]>
> > Subject: 6man w.g. last call for <draft-ietf-6man-maxra-01>
> > Date: December 21, 2016 at 7:15:23 AM PST
> > To: IPv6 List <[e-mail]>
> > Cc: Bob Hinden <[e-mail]>, Ole Trøan <[e-mail]>
> >
> > This message starts a two week 6MAN Working Group Last Call on advancing:
> >
> >     Title           : Support for adjustable maximum router lifetimes
> per-link
> >     Authors         : S. Krishnan
> >                       J. Korhonen
> >                       S. Chakrabarti
> >                       E. Nordmark
> >                       A. Yourtchenko
> >     Filename        : draft-ietf-6man-maxra-01
> >     Pages           : 6
> >     Date            : July 8, 2016
> >
> >     https://tools.ietf.org/html/draft-ietf-6man-maxra-01
> >
> >
> > as a Proposed Standard.  Substantive comments and statements of support
> > for publishing this document should be directed to the mailing list.
> > Editorial suggestions can be sent to the authors.  This last call will
> > end on 11 January 2017.
> >
> > We also need two people to volunteer to do a detailed reviews, and a
> > volunteer to be the document Shepard.
> >
> > Thanks,
> > Bob & Ole
> >
> >
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>