Re: [Int-area] [v6ops] New Version Notification for draft-patterson-intarea-ipoe-health-03.txt

Hi Richard, 

Thank you for addressing the comments. The -03 looks good to me. 

FWIW, I do have some additional comments that you may find at: 

* PDF: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-patterson-intarea-ipoe-health-03-rev%20Med.pdf 
* DOC: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-patterson-intarea-ipoe-health-03-rev%20Med.doc 

The main comments: 
* Use 3 as default retry interval value (consistent with BBF TR-124 and some existing implementations)
* Generalize the procedure to cover any dynamic configuration means (DHCP, as an example among others). 
* Add a guard to prevent loopback and multicast addresses as alternate target @
* Double check some part of the text to reflect that both interval and retry-interval are now used. 

I do support this effort to be adopted in dhcwg or int-area. 

Cheers,
Med

> -----Message d'origine-----
> De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Richard Patterson
> Envoyé : vendredi 29 juin 2018 18:22
> À : v6ops@ietf.org list; intarea-chairs@ietf.org; dhcwg@ietf.org
> Objet : [v6ops] New Version Notification for draft-patterson-intarea-ipoe-
> health-03.txt
> 
> Version -03 of draft-patterson-intarea-ipoe-health has now been uploaded.
> Thanks to Med, Jean-Yves and Dusan for their review and comments.
> 
> The noteworthy changes since -02 include:
>  - Added DHCP option flag to force ARP/ND for health checks.
>  - Populated IANA Considerations.
>  - Added Retry Interval distinct timer for between failed checks.
>  - Added default parameter values.
> 
> -Richard
> 
> 
> On 29/06/2018, 17:14, "internet-drafts@ietf.org"
> <internet-drafts@ietf.org> wrote:
> 
> 
>     A new version of I-D, draft-patterson-intarea-ipoe-health-03.txt
>     has been successfully submitted by Richard Patterson and posted to the
>     IETF repository.
> 
>     Name:           draft-patterson-intarea-ipoe-health
>     Revision:       03
>     Title:          IP over Ethernet (IPoE) Session Health Checking
>     Document date:  2018-06-29
>     Group:          Individual Submission
>     Pages:          15
>     URL:
> https://www.ietf.org/internet-drafts/draft-patterson-intarea-ipoe-health-
> 03.txt
>     Status:
> https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/
>     Htmlized:
> https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-03
>     Htmlized:
> https://datatracker.ietf.org/doc/html/draft-patterson-intarea-ipoe-health
>     Diff:
> https://www.ietf.org/rfcdiff?url2=draft-patterson-intarea-ipoe-health-03
> 
>     Abstract:
>        PPP over Ethernet clients have the functionality to detect path
>        unavailability by using PPP Keepalives.  IP over Ethernet does not
>        have this functionality, and it is not specified in the IETF when an
>        IP over Ethernet client should consider its WAN connectivity down,
>        unless there is a physical layer link down event.
> 
>        This document describes a mechanism for IP over Ethernet clients to
>        achieve connectivity validation, similar to that of PPP over
>        Ethernet, by using BFD Echo, or ARP and Neighbor Discovery functions.
> 
> 
> 
> 
>     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.
> 
>     The IETF Secretariat
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops