Hello, Thanks for contacting BitBay! Your ticket was forwarded to IT, when we receive new information we will contact you. Should you have any questions, please do not hesitate to contact us. Pozdrawiam / Kind Regards, Jerzy Kila BitBay Team ZASTRZE?ENIE POUFNO?CI/ZASTRZE?ENIE DOTYCZ?CE RODO Niniejsza korespondencja jest przeznaczona wy??cznie do u?ytku wymienionego odbiorcy. Tre?? tej wiadomo?ci jest poufna i prawnie chroniona. Odbiorc? mo?e by? jedynie jej adresat z wy??czeniem dost?pu osób trzecich. Je?eli nie jeste?cie Pa?stwo jej adresatem, b?d? otrzymali?cie j? przez pomy?k?, prosimy o powiadomienie o tym nadawcy oraz trwa?e jej usuni?cie. Jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dzia?anie o podobnym charakterze mo?e by? karalne i jest prawnie zabronione zgodnie z Rozporz?dzeniem Parlamentu Europejskiego i Rady (UE) 2016/679 z dnia 27 kwietnia 2016 r. w sprawie ochrony osób fizycznych w zwi?zku z przetwarzaniem danych osobowych i w sprawie swobodnego przep?ywu takich danych oraz uchylenia dyrektywy 95/46/WE. CONFIDENTIALITY CLAUSE/STIPULATION ACCORDING THE GDPR LAW This correspondence is intended only for use by the recipient. The content of this message is confidential and legally protected. The recipient can only be its addressee with the exclusion of access by third parties. If you are not the addressee or you have received it by mistake, please inform the sender and permanently delete it. Its dissemination, copying, distribution or other activity of a similar nature may be punishable and is prohibited by law according to Directive of the European Parliament and EU Council (EU) 2016/679 of 27 April 2016 on the protection of individuals with regard to the processing of personal data and the free flow of such data, as well as repealing directive 95/46/EC -------------------- Ticket ID: 130536
Dnia
?r, 23 Pa? at 4:26 PM
, Michael Sturtz <michael.sturtz@paccar.com> napisa?(-a):
I have found more problems with the DHCPv6-PD. The issue is on many home networks where people are using server type hardware such as Windows(TM) networks where DNS is used to locate and secure the network the renumbering event creates major problems as the on premises DHCPv6 server has no way to understand that a renumber event has occurred. People are very used to the IPv4 RFC 1918 static addressing where nothing on their local internal network will change without notice. The fact that ISPs can randomly change the internal delegated address without notice is a major problem. That will confuse people and cause problems especially where a customer has equipment such as Windows or Linux servers or other equipment that requires static addressing or DHCPv6. I understand that for certain operational reasons ISPs need to renumber addresses however I suggest we discourage the practice. We also could modify the RFC to require a message to be sent by CPE to all downstream network devices that a network renumber event is being scheduled. This can be sent as a multicast message that encodes the date that the renumbering will occur. I realize that we need to understand the security implications of this. This is just one idea that could smooth the renumbering events when then have to happen for some operational reason. -----Original Message----- From: ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de <ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de> On Behalf Of ipv6-ops-request@lists.cluenet.de Sent: Wednesday, October 23, 2019 3:00 AM To: ipv6-ops@lists.cluenet.de Subject: ipv6-ops Digest, Vol 159, Issue 1 Send ipv6-ops mailing list submissions to ipv6-ops@lists.cluenet.de To subscribe or unsubscribe via the World Wide Web, visit https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.cluenet.de%2Fmailman%2Flistinfo%2Fipv6-ops&data=02%7C01%7Cmichael.sturtz%40paccar.com%7Ce0b1f347a5cf432a761e08d7579fc9b3%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C1%7C637074216137461832&sdata=jmfELsU1SabFN%2BnPssOkByWoExIqjKfLhJCotAe40FA%3D&reserved=0 or, via email, send a message with subject or body 'help' to ipv6-ops-request@lists.cluenet.de You can reach the person managing the list at ipv6-ops-owner@lists.cluenet.de When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-ops digest..."
Dnia
?r, 23 Pa? at 4:26 PM
, Michael Sturtz <michael.sturtz@paccar.com> napisa?(-a):
I have found more problems with the DHCPv6-PD. The issue is on many home networks where people are using server type hardware such as Windows(TM) networks where DNS is used to locate and secure the network the renumbering event creates major problems as the on premises DHCPv6 server has no way to understand that a renumber event has occurred. People are very used to the IPv4 RFC 1918 static addressing where nothing on their local internal network will change without notice. The fact that ISPs can randomly change the internal delegated address without notice is a major problem. That will confuse people and cause problems especially where a customer has equipment such as Windows or Linux servers or other equipment that requires static addressing or DHCPv6. I understand that for certain operational reasons ISPs need to renumber addresses however I suggest we discourage the practice. We also could modify the RFC to require a message to be sent by CPE to all downstream network devices that a network renumber event is being scheduled. This can be sent as a multicast message that encodes the date that the renumbering will occur. I realize that we need to understand the security implications of this. This is just one idea that could smooth the renumbering events when then have to happen for some operational reason. -----Original Message----- From: ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de <ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de> On Behalf Of ipv6-ops-request@lists.cluenet.de Sent: Wednesday, October 23, 2019 3:00 AM To: ipv6-ops@lists.cluenet.de Subject: ipv6-ops Digest, Vol 159, Issue 1 Send ipv6-ops mailing list submissions to ipv6-ops@lists.cluenet.de To subscribe or unsubscribe via the World Wide Web, visit https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.cluenet.de%2Fmailman%2Flistinfo%2Fipv6-ops&data=02%7C01%7Cmichael.sturtz%40paccar.com%7Ce0b1f347a5cf432a761e08d7579fc9b3%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C1%7C637074216137461832&sdata=jmfELsU1SabFN%2BnPssOkByWoExIqjKfLhJCotAe40FA%3D&reserved=0 or, via email, send a message with subject or body 'help' to ipv6-ops-request@lists.cluenet.de You can reach the person managing the list at ipv6-ops-owner@lists.cluenet.de When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-ops digest..."