DoH Support for Chrome Browsers with AT&T

[PETKOPOULOS, MARKOS N]

Hello,

 

Good afternoon. Our team at AT&T is interested in adding new DoH options for our customers utilizing the Chrome browser. What is needed to get this process started, and what requirements are necessary? We would be more than happy to meet to discuss this if needed.

 

Best,

Markos Petkopoulos

 

[Javier Garcia Visiedo]

Hi Markos,

My suggestion would be to file a feature bug under the Internals>Network>DoH component, explaining your request in detail. That's the best way to track the requirements and the discussion with the team.

Best regards,

Javier

--
You received this message because you are subscribed to the Google Groups "net-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/IA0PR02MB99003FFC3C50A995A97255AFC24D2%40IA0PR02MB9900.namprd02.prod.outlook.com.

[Andrew Williams]

To add to what Javier said, we have the following document that lists the requirements for either having Chrome automatically use DoH when the user's operating system is using your DNS servers (Auto-upgradeable DoH) or for including your DoH service in the list of providers that users can choose from on the Chrome settings page: https://docs.google.com/document/d/128i2YTV2C7T6Gr3I-81zlQ-_Lprnsp24qzy_20Z1Psw/edit?usp=sharing That document links to issue templates you can use when creating the feature bug that Javier mentioned.

Let us know if you have any follow-up questions. Thank you!

-Andrew

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/CAFM5ELW5t4FNYzUMTB7Xc7T%2Bw4OFbJtnnnwWALcNhyTruiKTgw%40mail.gmail.com.

[PETKOPOULOS, MARKOS N]

Hi Javier and Andrew,

 

Good morning! Thank you for the quick response. My team will review the document and requirements you provided and get back to you with any questions we have shortly.

 

Best,

Markos Petkopoulos

[PETKOPOULOS, MARKOS N]

Hey Javier and Andrew,

 

Good afternoon! I hope you are both doing well. I submitted a ticket a while back following the process outlined in the document under Internals>Network>DoH Component. However, my request was denied, and they sent the same document previously sent in this email (Please see the link to the issue below). When clicking the links in the document, it takes me to the default https://issues.chromium.org/issues/wizard. Was this the correct approach or is there something I’m missing?

https://issues.chromium.org/issues/377342840 -> Link to Issue

 

Thank you in advance!

Markos Petkopoulos

[Matt Menke]

Not my area, but looks like that issue was closed with a request that you follow the process described in https://docs.google.com/document/d/128i2YTV2C7T6Gr3I-81zlQ-_Lprnsp24qzy_20Z1Psw/edit?tab=t.0 and use the links in that document to file a bug.  That issue you linked doesn't look to have followed either the "auto-upgrade" or "appear in settings" templates linked in the doc, both of which appear in the "Process" section.  Have you filed a different bug using either of those templates?

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/MW6PR02MB9910E3AECC9209C864C9FD87C23E2%40MW6PR02MB9910.namprd02.prod.outlook.com.

[Eric Orth]

I just checked the links (bit.ly/3P0YaMr and bit.ly/3u7dwqC) now, and they both seem to still be working correctly to open issues with a specific template to be filled out.  Did you follow the instruction in the document to ensure you are signed in to the issue tracker before accessing the link? I think we've seen issues in the past with the login flow messing up the use-a-template url.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/MW6PR02MB9910E3AECC9209C864C9FD87C23E2%40MW6PR02MB9910.namprd02.prod.outlook.com.

[PETKOPOULOS, MARKOS N]

Hello,

 

I made sure I clicked the link to sign in before navigating to both of those links (bit.ly/3P0YaMr and bit.ly/3u7dwqC). They both directed me to the same page (I attached a screenshot below). I tried logging out and back in, as well as in a different browser and am getting the same results.

 

What I originally did was from the page shown below, I navigated to the Chromium Contributor option and then opened a ticket under Internals>Network>DoH which was suggested earlier in this email chain.

 

Any other thoughts?

 

Thanks!

Markos Petkopoulos

 

 

From: Eric Orth <eric...@chromium.org>
Date: Wednesday, December 11, 2024 at 3:09 PM
To: PETKOPOULOS, MARKOS N <mp5...@att.com>
Cc: Andrew Williams <awi...@chromium.org>, Javier Garcia Visiedo <vis...@google.com>, net...@chromium.org <net...@chromium.org>, FAHMY, HANY <hf1...@att.com>, KARASARIDIS, ANESTIS <ak1...@att.com>, CHOU, STEPHEN <sc6...@att.com>, JAIN, MUKESH <mj2...@att.com>, O'HARA, WAYNE <wo1...@att.com>, CUSHMAN, CHRIS <cc0...@att.com>, MURTARI, JOHN <jm5...@att.com>
Subject: Re: DoH Support for Chrome Browsers with AT&T

I just checked the links (bit. ly/3P0YaMr and bit. ly/3u7dwqC) now, and they both seem to still be working correctly to open issues with a specific template to be filled out. Did you follow the instruction in the document to ensure you are signed

[Andrew Williams]

Hi Markos,

Sorry for the difficulty with the links. I've opened https://crbug.com/383572673 to see if we can get these working as intended.

In the meantime, and based on your earlier bug, would you mind starting a new bug report in the Internals>Network>DoH component with title "Inclusion for AT&T DoH provider (settings)", check the Markdown option for the bug description text box, and then paste in the following (everything between the "========" lines):

========

Info
1) Name, DoH endpoints with GET/POST preference:
 - ACME, https://dns.acme/dns-query, GET
2) Privacy policy: link
3) ToS: link
4) "I am officially [representing]/[acting on behalf of] the DoH provider."
5) Bootstrap (bit.ly/eb-doh)

Requirements
= Ownership
DoH endpoints owned by service provider: Y/N

= Transparency
1) Mean to contact the service provider? Y[How]/N

2) Is the service clearly described? Y/N
 - Collected PII, how long, purposes: Y/N
 - Aggregated data, purposes: Y/N
 - Privacy enhancements, e.g. RFC7816: Y/N
 - Jurisdiction: Y/N
 - Categories of content being filtered: [Y] [N] [N/A]
   -  Details about user control, means to contest: Y/N
 - Transparency reports: Y/N

= Conformance
Compliance with RFC:
1) 8484? Y/N
2) 3597? Y/N

Will your service keep up with:
3) related standards, improvements, best practices? Y/N

= Behavior
1) Responds with the appropriate error code[1] for blocked/filtered domains? Y/N
[1]: recommendation of REFUSED over NXDOMAIN.

2) Uses and respects NXDOMAIN when a domain doesn’t exist? Y/N

= Availability
The service is made publicly available at no cost: Y/N

Due diligence
 - Compliance with relevant regulations (e.g. GDPR): Y/N

========

From there, modify the template above to provide the requested information and answers to the questions. When you are done, submit the bug report. If you have any further questions about the process please let us know.

My apologies again for the inconvenience!

-Andrew

[PETKOPOULOS, MARKOS N]

Hi Andrew,

 

Good morning. No worries at all, thank you for the assistance throughout this process. My team and I will work towards submitting the new form. We will let you know if we have any further difficulties or questions.

 

Thanks again!

Markos Petkopoulos

 

From: Andrew Williams <awi...@chromium.org>
Date: Thursday, December 12, 2024 at 12:05 AM
To: PETKOPOULOS, MARKOS N <mp5...@att.com>
Cc: Eric Orth <eric...@chromium.org>, Javier Garcia Visiedo <vis...@google.com>, net...@chromium.org <net...@chromium.org>, FAHMY, HANY <hf1...@att.com>, KARASARIDIS, ANESTIS <ak1...@att.com>, CHOU, STEPHEN <sc6...@att.com>, JAIN, MUKESH <mj2...@att.com>, O'HARA, WAYNE <wo1...@att.com>, CUSHMAN, CHRIS <cc0...@att.com>, MURTARI, JOHN <jm5...@att.com>
Subject: Re: DoH Support for Chrome Browsers with AT&T

Hi Markos, Sorry for the difficulty with the links. I've opened https: //crbug. com/383572673 to see if we can get these working as intended. In the meantime, and based on your earlier bug, would you mind starting a new bug report in the Internals>Network>DoH