Re: [Community-Discuss] [Ext] Re: Community-Discuss Digest, Vol 547, Issue 1
On 12/8/19, 3:33 PM, "Ronald F. Guilmette" wrote: [...] > Mr. Vegoda appears to be arguing that No, I am not making an argument, I am observing that there is a difference in the way these two RIRs perform this function. Kind regards, Leo Vegoda ___ Community-Discuss mailing list Community-Discuss@afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss
Re: [Community-Discuss] [Ext] Re: Community-Discuss Digest, Vol 547, Issue 1
Owen DeLong wrote: [...] > Whois is data that is published generally, so your comments here > about DPR don’t really apply. > > Such WHOIS dumps are available from RIPE, so I don’t think it is a > GDPR issue at all. Both AFRINIC and RIPE NCC public database dumps on their FTP sites but the RIPE NCC data is cleaned to remove more person data than the AFRINIC data dumps. The AFRINIC data includes the unique nic-hdl of contacts for resources but the dumps published by the RIPE NCC replace the unique nic-hdl with DUMY-RIPE: person: Placeholder Person Object address: RIPE Network Coordination Centre address: P.O. Box 10096 address: 1001 EB Amsterdam address: The Netherlands phone: +31 20 535 nic-hdl: DUMY-RIPE mnt-by: RIPE-DBM-MNT remarks: ** remarks: * This is a placeholder object to protect personal data. remarks: * To view the original object, please query the RIPE remarks: * Database at: remarks: * http://www.ripe.net/whois remarks: ** created: 2009-11-11T16:36:07Z last-modified: 2009-11-11T16:36:07Z source: RIPE Kind regards, Leo ___ Community-Discuss mailing list Community-Discuss@afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss
Re: [Community-Discuss] IPv6 Chapter 254
Andrew Alston wrote: [...] > There is one problem with your argument here - and I agree with you in > one sense. In the home user market the users don't need to know - and > that’s what we did in our rollout in the home user market. > > The corporate side is NOT like that - you HAVE to communicate with them > for simple reasons: > > A.) In many corporates you don't control the CPE - unless you're doing fully > managed service. This means they have to change things on their CPE to > route the v6 through. > > B.) Corporates run firewalls - firewalls have to have v6 rulesets and have > to be configured > > C.) Corporates run internal network infrastructure - often with multiple > vlans etc - this requires configuration. I think the only thing we disagree on is where the transition happens. In my experience, the overwhelming proportion of businesses are genuinely tiny, ranging from an individual to a dozen people. And even when businesses grow larger they can often buy packaged hosted services and tie everything together with the cheapest Internet access they can buy. Lots of businesses buy and use services designed for the residential market instead of higher quality "corporate" services. Regards, Leo Vegoda smime.p7s Description: S/MIME cryptographic signature ___ Community-Discuss mailing list Community-Discuss@afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss
Re: [Community-Discuss] IPv6 Chapter 254
Andrew Alston wrote: [...] > If we truly want v6 adoption, I’d argue we are going about it the wrong way, > we have to promote it into the corporate and home user market. Only when > these markets start demanding IPv6 will we get true movement from the > majority of providers I disagree. If the home user market needs to know or care about which version of the Internet Protocol is being used, or even know what the Internet Protocol is, things have gone wrong. Some parts of the corporate market do need to know but not most small and medium sized businesses. They just buy packaged services and can legitimately expect them to work as expected. The providers on the list at http://www.worldipv6launch.org/measurements/ with the big IPv6 deployments didn't survey their residential customers and ask them which version of IP they'd prefer. They made IPv6 an integral component of their systematic network upgrade. Regards, Leo Vegoda smime.p7s Description: S/MIME cryptographic signature ___ Community-Discuss mailing list Community-Discuss@afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss
