Hi Richard, Thank you for writing this document.
FWIW, please find some inputs to this draft: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-patterson-intarea-ipoe-health-02-rev%20Med.pdf (pdf version) https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-patterson-intarea-ipoe-health-02-rev%20Med.doc (.doc version) FYI, similar mechanisms are supported by our CPE (but also at the network side). It is worth to ACK that “some” means can be enabled at the network side (in addition to the CPE). I do see a value in the dynamic approach proposed in the draft (e.g., instruct the behavior). Some additional parameters can be included to tweak the mechanism and to align both CPE and network side. Cheers, Med > -----Message d'origine----- > De : Int-area [mailto:int-area-boun...@ietf.org] De la part de Richard > Patterson > Envoyé : mardi 19 juin 2018 18:17 > À : int-area@ietf.org > Objet : [Int-area] New Version Notification for draft-patterson-intarea-ipoe- > health-02.txt > > Thanks for the comments on and off the v6ops list, we've published a > new version of draft-patterson-intarea-ipoe-health. > > The major changes can summarised as: > - Emphasised preference for use of BFD echo as the health check mechanism. > - Removed lifetime expiration from Behaviour 2 and clarified usage. > - Updated Behaviour 3 with instructions for whilst mid-renew/rebind. > - Reworded multihoming section. > - Added Acknowledgements. > > Please continue providing feedback, and if anyone has a relationship > with DHCP client developers, or CPE vendors, we'd love to start a > dialogue there too. > > -Richard > > > On 19/06/2018, 17:07, "internet-dra...@ietf.org" > <internet-dra...@ietf.org> wrote: > > > A new version of I-D, draft-patterson-intarea-ipoe-health-02.txt > has been successfully submitted by Richard Patterson and posted to the > IETF repository. > > Name:draft-patterson-intarea-ipoe-health > Revision:02 > Title:IPoE Client Health Checking > Document date:2018-06-19 > Group:Individual Submission > Pages:13 > URL: > https://www.ietf.org/internet-drafts/draft-patterson-intarea-ipoe-health- > 02.txt > Status: > https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/ > Htmlized: > https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-02 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-patterson-intarea-ipoe-health > Diff: > https://www.ietf.org/rfcdiff?url2=draft-patterson-intarea-ipoe-health-02 > > 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's not specified 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 way 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 > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
