Extended Deadline and Reminder OARC 39 - Call for Contribution

2022-08-31 Thread John Todd
OARC 39 will be a two-day hybrid meeting held on 22 & 23 October in Belgrade, Serbia at 10:00 AM (Local time - CEST (UTC+02:00)) The onsite part of the meeting will be colocated with RIPE 85. The Programme Committee is seeking contributions from the community. All DNS-related subjects and

[NANOG-announce] N86 Registration is Open + 2022 Election Cycle is Here!

2022-08-31 Thread Nanog News
*NANOG 86 Registration is Now Open! * *Our 86th community-wide gathering is 17-19 Oct 2022* Join us in person or virtually for our next meeting, NANOG 86! Don't miss your chance to experience hours of ground-breaking industry talks, legendary keynote speakers, opportunities for networking +

N86 Registration is Open + 2022 Election Cycle is Here!

2022-08-31 Thread Nanog News
*NANOG 86 Registration is Now Open! * *Our 86th community-wide gathering is 17-19 Oct 2022* Join us in person or virtually for our next meeting, NANOG 86! Don't miss your chance to experience hours of ground-breaking industry talks, legendary keynote speakers, opportunities for networking +

RE: ServiceNow

2022-08-31 Thread Chris Wright
I guess now's a good time to recommend this handy site for when you'd like a view from the outside: https://ping.pe No issues at this time reaching that address from pretty much anywhere. - Chris From: NANOG On Behalf Of Mann, Jason via NANOG Sent: Wednesday, August 31, 2022 1:59 AM To:

RE: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Vasilenko Eduard via NANOG
Such router behavior is completely legal by ND RFC. It does not matter that real routers implementations do not do this. We should think that they do because the standard permits it. And the RA in the chain may be lost. It is better to attach information about completeness to the information

Re: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Fernando Gont
Hi, On 31/8/22 09:43, Vasilenko Eduard wrote: Hi all, The router could split information between RAs (and send it at different intervals). It may be difficult to guess what is stale and what is just "not in this RA". You ask the router, and the router responds. If you want to consider the

RE: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Vasilenko Eduard via NANOG
Hi all, The router could split information between RAs (and send it at different intervals). It may be difficult to guess what is stale and what is just "not in this RA". Fernando proposing (not documented yet in draft-ietf-6man-slaac-renum-04) re-asking the router by RS and using timers (size

Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Fernando Gont
Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a while now -- one of the most common cases being ISPs rotating home prefixes, and your devices ending up with stale/invalid addresses. We have done quite a bit of work already: * Problem

Re: Disney+ Contact

2022-08-31 Thread Mark Tinka
On 8/31/22 11:03, Brian Turnbow wrote: Hi Mark Anyone from Disney who can help with a geo issue on-list? We have customers in South Africa mapping to India. Thanks. Did you try the emails in thebrotherswisp geo page? I have had some success though the Techops emails. Sometimes it does

RE: Disney+ Contact

2022-08-31 Thread Brian Turnbow via NANOG
Hi Mark >Anyone from Disney who can help with a geo issue on-list? We have customers in >South Africa mapping to India. Thanks. Did you try the emails in thebrotherswisp geo page? I have had some success though the Techops emails. Sometimes it does take a while for a response... Disney+:

Disney+ Contact

2022-08-31 Thread Mark Tinka
Hi all. Anyone from Disney who can help with a geo issue on-list? We have customers in South Africa mapping to India. Thanks. Mark.