FOR REVIEW: ALAC Correspondence on IETF IPMC Bylaws Amendment Public Consultation
Dear CPWG members, Please find the link to draft ALAC correspondence for proposed amendment to IETF IPMC Bylaws: https://docs.google.com/document/d/18BN-ki3BpGKyfCTjKb1PZ-bSnYyN-yb9nyWpTOgq.... Kindly provide your comments by Tuesday, 25 November. As a reminder, this correspondence has been drafted based on the bullet points document on this topic. This is the link to the bullet points document: https://docs.google.com/document/d/1Zi8wuX1KvFhBZ2dQ1tCptlDF04eBL6357ZzZKhCc... Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN)
Dear All, At the outset, I must assert that, my commitments are for "open" methodologies and as such I have no claim on the expertise pertaining to the IPR. I wish the statement has a positive start. The IETF community develops the technical policies published in RFCs. To prevent ownership disputes over the content both IANA and the IETF have agreed to dedicate any applicable copyright rights to the public domain using the Creative Commons CC0 1.0 dedication. Reference: https://www.iana.org/help/licensing-terms Quick Notes for Point #3. IETF RFCs were not published "commercially" in the traditional sense of being sold as proprietary products. Instead, they were, and continue to be, freely available to the public. While individuals or companies can download, copy, and distribute unmodified RFCs for any purpose under the IETF Trust's TLP license, the IETF maintains strict control over modifications to preserve the integrity of the historical record and the standards process. How does the ICANN -> IETF Trust -> ICANN impact this ? Specifically: "Characterising the IETF Through the Lens of RFC Deployment" Please read the attached paper with the above title. My suggestion on this point is note in the Google Doc. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Retired Professor Department of Computer Science and Engineering & Retired Director, Centre for Applied Research in Indic Technologies [CARIT] College of Engineering, Guindy Campus Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ________________________________ From: Ozan Sahin via CPWG <cpwg@icann.org> Sent: 20 November 2025 19:33 To: cpwg@icann.org <cpwg@icann.org> Subject: [CPWG] FOR REVIEW: ALAC Correspondence on IETF IPMC Bylaws Amendment Public Consultation Dear CPWG members, Please find the link to draft ALAC correspondence for proposed amendment to IETF IPMC Bylaws: https://docs.google.com/document/d/18BN-ki3BpGKyfCTjKb1PZ-bSnYyN-yb9nyWpTOgq.... Kindly provide your comments by Tuesday, 25 November. As a reminder, this correspondence has been drafted based on the bullet points document on this topic. This is the link to the bullet points document: https://docs.google.com/document/d/1Zi8wuX1KvFhBZ2dQ1tCptlDF04eBL6357ZzZKhCc... Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN)
Dear Gopal, thank you for the points you are making and for sharing this interesting paper. I wonder if the text you are suggesting including in the ALAC correspondence that is quoted from the IANA.ORG licensing term is okay with including but since I am not a lawyer, I'll let Greg comment. As for the second point you are making in relation to the RFCs, I am not sure whether you have read recent exchanges in the IPR-WG ( archived at: https://mailarchive.ietf.org/arch/browse/ipr-wg/? ) I feel that digging into RFC IPRs at the moment is exploring a deep rabbit hole, you never know how far it goes. Probably better addressed directly by taking part as an individual in the IETF processes? Kindest regards, Olivier On 20/11/2025 17:15, gopal via CPWG wrote:
Dear All,
At the outset, I must assert that, my commitments are for "open" methodologies and as such I have no claim on the expertise pertaining to the IPR.
I wish the statement has a positive start.
The IETF community develops the technical policies published in RFCs. To prevent ownership disputes over the content both IANA and the IETF have agreed to dedicate any applicable copyright rights to the public domain using the Creative Commons CC0 1.0 dedication.
Reference: https://www.iana.org/help/licensing-terms <https://www.iana.org/help/licensing-terms>
Quick Notes for Point #3.
IETF RFCs were not published "commercially" in the traditional sense of being sold as proprietary products. Instead, they were, and continue to be, freely available to the public.
While individuals or companies can download, copy, and distribute unmodified RFCs for any purpose under the */IETF Trust's TLP license/*, the IETF maintains strict control over modifications to preserve the integrity of the historical record and the standards process.
How does the ICANN -> IETF Trust -> ICANN impact this ?
Specifically: "Characterising the IETF Through the Lens of RFC Deployment"
Please read the attached paper with the above title. *_ _* *_My suggestion on this point is note in the Google Doc._*
Sincerely,
Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 <https://vidwan.inflibnet.ac.in/profile/57545> https://www.facebook.com/gopal.tadepalli <https://www.facebook.com/gopal.tadepalli> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Retired Professor Department of Computer Science and Engineering & Retired Director, Centre for Applied Research in Indic Technologies [CARIT] College of Engineering, Guindy Campus Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------------------------------------------------ *From:* Ozan Sahin via CPWG <cpwg@icann.org> *Sent:* 20 November 2025 19:33 *To:* cpwg@icann.org <cpwg@icann.org> *Subject:* [CPWG] FOR REVIEW: ALAC Correspondence on IETF IPMC Bylaws Amendment Public Consultation
Dear CPWG members,
Please find the link to draft ALAC correspondence for proposed amendment to IETF IPMC Bylaws: https://docs.google.com/document/d/18BN-ki3BpGKyfCTjKb1PZ-bSnYyN-yb9nyWpTOgq.... Kindly provide your comments by *Tuesday, 25 November*.
As a reminder, this correspondence has been drafted based on the bullet points document on this topic. This is the link to the bullet points document: https://docs.google.com/document/d/1Zi8wuX1KvFhBZ2dQ1tCptlDF04eBL6357ZzZKhCc...
Best,
Ozan Sahin
Policy Development Support Senior Specialist
Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ CPWG mailing list --cpwg@icann.org To unsubscribe send an email tocpwg-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
Oliver, My responses in the trace. ________________________________ From: Olivier MJ Crépin-Leblond <ocl@gih.com> Sent: 21 November 2025 05:44 To: gopal <gopal@annauniv.edu>; cpwg@icann.org <cpwg@icann.org>; Ozan Sahin <ozan.sahin@icann.org> Subject: Re: [CPWG] Re: FOR REVIEW: ALAC Correspondence on IETF IPMC Bylaws Amendment Public Consultation Dear Gopal, thank you for the points you are making and for sharing this interesting paper. Gopal> Thank you for the opportunity to catch up from where I left in the previous CPWG Call. I wonder if the text you are suggesting including in the ALAC correspondence that is quoted from the IANA.ORG licensing term is okay with including but since I am not a lawyer, I'll let Greg comment. Gopal> I agree Greg Shatan is the best. My submission is to sound positive on CC BY 4.0 with the triad ICANN, IETF and IANA for a start. CC BY4.0 has its own nuances that are not so much necessary for me to study. As for the second point you are making in relation to the RFCs, I am not sure whether you have read recent exchanges in the IPR-WG ( archived at: https://mailarchive.ietf.org/arch/browse/ipr-wg/? ) Gopal> NO. Thank you for pointing at this. I am seeing no reason for ALAC to be disappointed at the way things have been progressing. I suggest that this tip of a potential iceberg may be cited positively in the ALAC statement in- review. I feel that digging into RFC IPRs at the moment is exploring a deep rabbit hole, you never know how far it goes. Probably better addressed directly by taking part as an individual in the IETF processes? Gopal> As above. As you would appreciate, work with technology is more valuable when things are potentially like this. "Skill" to my mind is just to sense this condition ASAP. And build expertise to resolve. Otherwise, it is just a "push" button. Gopal T V Kindest regards, Olivier On 20/11/2025 17:15, gopal via CPWG wrote: Dear All, At the outset, I must assert that, my commitments are for "open" methodologies and as such I have no claim on the expertise pertaining to the IPR. I wish the statement has a positive start. The IETF community develops the technical policies published in RFCs. To prevent ownership disputes over the content both IANA and the IETF have agreed to dedicate any applicable copyright rights to the public domain using the Creative Commons CC0 1.0 dedication. Reference: https://www.iana.org/help/licensing-terms Quick Notes for Point #3. IETF RFCs were not published "commercially" in the traditional sense of being sold as proprietary products. Instead, they were, and continue to be, freely available to the public. While individuals or companies can download, copy, and distribute unmodified RFCs for any purpose under the IETF Trust's TLP license, the IETF maintains strict control over modifications to preserve the integrity of the historical record and the standards process. How does the ICANN -> IETF Trust -> ICANN impact this ? Specifically: "Characterising the IETF Through the Lens of RFC Deployment" Please read the attached paper with the above title. My suggestion on this point is note in the Google Doc. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Retired Professor Department of Computer Science and Engineering & Retired Director, Centre for Applied Research in Indic Technologies [CARIT] College of Engineering, Guindy Campus Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ________________________________ From: Ozan Sahin via CPWG <cpwg@icann.org><mailto:cpwg@icann.org> Sent: 20 November 2025 19:33 To: cpwg@icann.org<mailto:cpwg@icann.org> <cpwg@icann.org><mailto:cpwg@icann.org> Subject: [CPWG] FOR REVIEW: ALAC Correspondence on IETF IPMC Bylaws Amendment Public Consultation Dear CPWG members, Please find the link to draft ALAC correspondence for proposed amendment to IETF IPMC Bylaws: https://docs.google.com/document/d/18BN-ki3BpGKyfCTjKb1PZ-bSnYyN-yb9nyWpTOgq.... Kindly provide your comments by Tuesday, 25 November. As a reminder, this correspondence has been drafted based on the bullet points document on this topic. This is the link to the bullet points document: https://docs.google.com/document/d/1Zi8wuX1KvFhBZ2dQ1tCptlDF04eBL6357ZzZKhCc... Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ CPWG mailing list -- cpwg@icann.org<mailto:cpwg@icann.org> To unsubscribe send an email to cpwg-leave@icann.org<mailto:cpwg-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
participants (3)
-
gopal -
Olivier MJ Crépin-Leblond -
Ozan Sahin