Thanks Ole, understood.
On Thu, 4 Oct 2018 at 14:33, Ole Troan wrote:
>
> Richard,
>
> > As a side-note, is it really that challenging or slow to get a new
> > DHCP option assigned? Perhaps I'm showing my naivety here.
>
> Getting the DHCP option itself isn’t hard. But then you need to get it
>
On Thu, 4 Oct 2018 at 11:33, Ole Troan wrote:
> Requiring the DHCP option makes a big difference in deployability.
> Without it, I can implement this feature today. With it, I have to wait until
> the DHCP option is standardised. And we would presumably get into a big
> debate about what CE
proactively
>with IPoE health checks, an IPoE client acting as a router, SHOULD
>withdraw itself as a default router on the LAN, following requirement
>G-5 of [RFC7084], Section 4.1."
> Since the referenced RFC7084 requirement is a "MUST", I would make it
Hi Barbara,
Thanks for the comments, my responses in-line, quoting snipped where
appropriate:
On Tue, 31 Jul 2018 at 19:50, STARK, BARBARA H wrote:
> The consensus view here is that BFD Echo, when implemented as described in
> RFC 5881 and BBF specs, works. I don't have anyone asking for
Following on from the Q and hallway chats at IETF102, I've captured
a few questions for further discussion on the lists.
For those yet to review the draft, it can be found here:
https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-04
- BFD Echo: Still requires a full BFD
Hi Juliusz,
The third bullet point of Section 2, Alternative Mitigations, already
mentions DHCPv4 Force Renew, and DHCPv6 Reconfigure.
In my personal experience, I'm yet to find a BNG or CPE that supports
them, but otherwise I do agree, they could be used to mitigate
downtime during planned
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
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.
On Mon, 2 Jul 2018 at 09:29, wrote:
> The main comments:
> * Use 3 as default retry interval value
hanism 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
>
.
-Richard
On 19/06/2018, 17:07, "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
R
Option to allow network administrators to signal
parameters dynamically to CEs.
On 12/06/2018, 10:11, "internet-dra...@ietf.org"
wrote:
A new version of I-D, draft-patterson-intarea-ipoe-health-01.txt
has been successfully submitted by Richard Patterson and posted to th
Hi All,
The above new draft has been posted to address an operational problem
that exists with current IPoE (non-PPPoE) fixed line broadband
services.
It can be found here:
https://datatracker.ietf.org/doc/draft-patterson-intarea-ipoe-health/
Hopefully the draft covers the problem statement
12 matches
Mail list logo
