[happy] Re: previous work on reporting

["[e-mail]" <[e-mail]>]

Right, however, the work of the main HEv3 document can't be advanced for publication until the reporting is also advanced. Otherwise, we will repeat the previous situation.

In other words: To be useful, the reporting must be done by the “same” code as is doing the fall-back. They are closely tied. If the HEv3 is implemented without the reporting, the reporting will never be done, and we will be hiding failures for ever.

Regards,
Jordi

@jordipalet


> El 26 mar 2025, a las 16:52, Tim Chown <Tim.Chown=[e-mail]> escribió:
> 
> Hi Jordi,
>  
> These are all fair questions.
>  
> As emphasised in Bangkok, the reporting topic is outside the scope of the main HEv3 draft.
>  
> I would suggest some discussion is held on the list building on what was presented in the meeting and Bangkok, your points, and any others that people wish to raise, and we as a WG propose the bare bones of a solution/mechanism via a separate draft, as per the charter milestone.  We should then ensure that draft has very early review by SAAG and/or appropriate experts before it’s developed in detail.
>  
> Tim
>  
> On 26/03/2025, 15:39, "[e-mail] <mailto:[e-mail]>" <jordi.palet=[e-mail] <mailto:jordi.palet=[e-mail]>> wrote:
> 
> Hi Tim,
>  
> Yes, privacy is key, but as I mention in the mic, this can be achieved in different ways.
>  
> We need to understand/decide who is the best target for the reporting (the ISP, the end destination or both). This depends basically on who generate the problem: the ISP or their transits, or the end-destination (for example a service with AAAA configured but not working).
>  
> Also depending on who is getting the reporting, what tools they already use? What is very clear is that, in general, ISPs and content providers will not implement anything new. That’s why originally I targeted to syslog. Not saying now is the only solution.
>  
> We also need to understand that HE may be implemented somewhere else the browser, so the detection of failures is not only in web sites.
>  
> Should the reporting be done for every single failure? I don’t think is needed. For example, if a web browser of app detects a failure could cache it before reporting, so it can report every “n” failures. This also provides helpful information, such as “all the destinations fail” (so probably is the ISP network or upstreams), only this web site is failing. True that this also be donde at the reporting collector, but may be we want to minimize the data being sent and non-persistent failures.
>  
> Regarding privacy, in general we only need to know the destination address that fails, not “who” is the user that is asking for that content. This will basically make the reporting anonymous to the ISP or content provider.
>  
> Just a few initial points to consider …
>  
> Regards,
> Jordi
> 
> @jordipalet
> 
> 
> 
> El 26 mar 2025, a las 16:14, Tim Chown <Tim.Chown=[e-mail] <mailto:Tim.Chown=[e-mail]>> escribió:
>  
> Hi Jordi,
>  
> On 25/03/2025, 13:39, "[e-mail] <mailto:[e-mail]>" <jordi.palet=[e-mail] <mailto:jordi.palet=[e-mail]>> wrote:
>  
> I forgot to send this to the list before as previous work regarding the reporting:
> 
> https://datatracker.ietf.org/doc/draft-palet-ietf-v6ops-he-reporting/00/
> https://datatracker.ietf.org/doc/draft-palet-v6ops-he-reporting/00/
> https://datatracker.ietf.org/doc/draft-xie-v6ops-network-happyeyeballs/01/
> 
> 
> I’m actually surprised, that there was no a slot in the meeting for at least a summary of all that.
>  
> The 90-minute agenda for Bangkok focused on the main HEv3 draft, but we also gave time to both an implementation report and the reporting issue.
>  
> Eric and I will discuss the best way forward with the reporting work, and potential draft as per the charter milestones, such that we go into it eyes wide open about the privacy aspects.
>  
> You’re obviously very free to discuss the topic on the list.
>  
> Best wishes,
> Tim
>  
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com <http://www.theipv6company.com/>
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.