[dhcwg] New Version Notification for draft-patterson-intarea-ipoe-health-03.txt

[Richard Patterson]

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-***@ietf.org"
<internet-***@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

[m***@orange.com]

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-----
Envoyé : vendredi 29 juin 2018 18:22
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.
- 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
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
https://www.ietf.org/internet-drafts/draft-patterson-intarea-ipoe-health-
03.txt
https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/
https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-03
https://datatracker.ietf.org/doc/html/draft-patterson-intarea-ipoe-health
https://www.ietf.org/rfcdiff?url2=draft-patterson-intarea-ipoe-health-03
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
https://www.ietf.org/mailman/listinfo/v6ops

[Richard Patterson]

Hi Med,

Thanks once again for your review, comments, and support.
I'll address your bullet points in-line below. I'll try to get a -04
out incorporating your feedback before the cut off.

* Use 3 as default retry interval value (consistent with BBF TR-124 and some existing implementations).

Have reworded the parameter definition to:
- Limit (Integer): The number of failed consecutive checks before an
action is taken. Default value: 3.

* Generalize the procedure to cover any dynamic configuration means (DHCP, as an example among others).

I agree for the most part, but I'm unsure about considering TR-69 as
dynamically signalled. I was treating TR-69 as a method for local
configuration (which we've now changed to static in -03).
I think the idea is the same though, so I'll work your suggested wording in.
Is saying that the field must be a unicast address sufficient, or do
you want to specifically call out loopbacks and multicast?

* 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

[Richard Patterson]

Med, I've just pushed -04 out before the cutoff deadline this
evening. Hopefully I've correctly integrated your comments.

A new version of I-D, draft-patterson-intarea-ipoe-health-04.txt
has been successfully submitted by Richard Patterson and posted to the
IETF repository.



Name: draft-patterson-intarea-ipoe-health
Revision: 04
Title: IP over Ethernet (IPoE) Session Health Checking
Document date: 2018-07-02
Group: Individual Submission
Pages: 16
URL:
https://www.ietf.org/internet-drafts/draft-patterson-intarea-ipoe-health-04.txt
Status:
https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/
Htmlized:
https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-04
Htmlized:
https://datatracker.ietf.org/doc/html/draft-patterson-intarea-ipoe-health
Diff:
https://www.ietf.org/rfcdiff?url2=draft-patterson-intarea-ipoe-health-04

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.

Post by Richard Patterson
Hi Med,
Thanks once again for your review, comments, and support.
I'll address your bullet points in-line below. I'll try to get a -04
out incorporating your feedback before the cut off.

* Use 3 as default retry interval value (consistent with BBF TR-124 and some existing implementations).

- Limit (Integer): The number of failed consecutive checks before an
action is taken. Default value: 3.

* Generalize the procedure to cover any dynamic configuration means (DHCP, as an example among others).

I agree for the most part, but I'm unsure about considering TR-69 as
dynamically signalled. I was treating TR-69 as a method for local
configuration (which we've now changed to static in -03).
I think the idea is the same though, so I'll work your suggested wording in.
Is saying that the field must be a unicast address sufficient, or do
you want to specifically call out loopbacks and multicast?

* 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

[m***@orange.com]

Hi Richard,

Thank you for promptly addressing the comments.

This version is stable enough and ready for a hopefully call for adoption.

Cheers,
Med

-----Message d'origine-----
Envoyé : lundi 2 juillet 2018 22:06
Objet : Re: [v6ops] New Version Notification for draft-patterson-intarea-
ipoe-health-03.txt
Med, I've just pushed -04 out before the cutoff deadline this
evening. Hopefully I've correctly integrated your comments.
A new version of I-D, draft-patterson-intarea-ipoe-health-04.txt
has been successfully submitted by Richard Patterson and posted to the
IETF repository.
Name: draft-patterson-intarea-ipoe-health
Revision: 04
Title: IP over Ethernet (IPoE) Session Health Checking
Document date: 2018-07-02
Group: Individual Submission
Pages: 16
https://www.ietf.org/internet-drafts/draft-patterson-intarea-ipoe-health-
04.txt
https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/
https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-04
https://datatracker.ietf.org/doc/html/draft-patterson-intarea-ipoe-health
https://www.ietf.org/rfcdiff?url2=draft-patterson-intarea-ipoe-health-04
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.

Post by Richard Patterson
Hi Med,
Thanks once again for your review, comments, and support.
I'll address your bullet points in-line below. I'll try to get a -04
out incorporating your feedback before the cut off.

Post by m***@orange.com
* Use 3 as default retry interval value (consistent with BBF TR-124 and

some existing implementations).

Post by Richard Patterson
- Limit (Integer): The number of failed consecutive checks before an
action is taken. Default value: 3.

Post by m***@orange.com
* Generalize the procedure to cover any dynamic configuration means

(DHCP, as an example among others).

Post by Richard Patterson
I agree for the most part, but I'm unsure about considering TR-69 as
dynamically signalled. I was treating TR-69 as a method for local
configuration (which we've now changed to static in -03).
I think the idea is the same though, so I'll work your suggested wording

in.

Post by Richard Patterson

Post by m***@orange.com
* Add a guard to prevent loopback and multicast addresses as alternate

Is saying that the field must be a unicast address sufficient, or do
you want to specifically call out loopbacks and multicast?

Post by m***@orange.com
* Double check some part of the text to reflect that both interval and

retry-interval are now used.

Post by Richard Patterson

Post by m***@orange.com
I do support this effort to be adopted in dhcwg or int-area.
Cheers,
Med