So sorry for the late response. I wasn't getting any alerts regarding these emails. Just changed the setting so that it doesn't happen again. I just responded to the "AUTH48: RFC-to-be 9627 <draft-ietf-avtext-lrr-07>" email thread with my new affiliation. Thank you!
On Thu, Feb 20, 2025 at 6:13 PM Mo Zanaty (mzanaty) <[email protected]> wrote: > The authors have no objection to changing the URN for 9626 from > "framemarkinginfo" to "framemarking". Normally such a change would be > undesirable for fear of breaking existing parsers, but that breakage > happened long ago when Chrome/webrtc used "framemarking" (with an HTTP > URI pointing to the draft rather than the IANA URN), so parsers became > agile to accept anything with the substring "framemarking". Therefore, I > agree with Justin's suggested change. > > Thanks, > Mo > > ------------------------------ > *From:* Justin Uberti <[email protected]> > *Sent:* Thursday, February 20, 2025 2:14 AM > *To:* Zaheduzzaman Sarker <[email protected]> > *Cc:* Jonathan Lennox <[email protected]>; Megan Ferguson < > [email protected]>; Murray S. Kucherawy <[email protected]>; > Jonathan Lennox <[email protected]>; Suhas > Nandakumar (snandaku) <[email protected]>; Espen Berger (espeberg) < > [email protected]>; Mo Zanaty (mzanaty) <[email protected]>; Bernard > Aboba <[email protected]>; [email protected] <[email protected]>; > [email protected] <[email protected]>; [email protected] < > [email protected]>; [email protected] <[email protected]>; > [email protected] <[email protected]>; Francesca Palombini < > [email protected]>; Orie Steele <[email protected]>; > RFC Editor <[email protected]>; [email protected] < > [email protected]> > *Subject:* Re: Cluster C324 questions: RFCs 9626 > <draft-ietf-avtext-framemarking>, 9627 <draft-ietf-avtext-lrr>, and 9628 > <draft-ietf-payload-vp9> > > Also, I noted that the IANA registration section in RFC 9626 appears to > have an incorrect URI, urn:ietf:params:rtp-hdrext:framemarkinginfo rather > than urn:ietf:params:rtp-hdrext:framemarking. > > > > On Wed, Feb 19, 2025 at 11:12 PM Justin Uberti <[email protected]> wrote: > >> Hi all, yes, my affiliation is now OpenAI but you can still use >> [email protected] as my contact email. >> >> On Wed, Feb 19, 2025 at 5:17 PM Zaheduzzaman Sarker < >> [email protected]> wrote: >> >>> I have pinged Justin and he has promised to respond. Lets give couple >>> days then I will remihim again. >>> >>> I will try to reach Danny via his google colleagues. However if we are >>> just missing only one approval the I will do an AD override. >>> >>> // Zahed >>> >>> On Wed, 19 Feb 2025 at 21:38, Jonathan Lennox < >>> [email protected]> wrote: >>> >>>> Danny is still at Google, according to his LinkedIn profile, so I >>>> believe the affiliation and e-mail address for him in 9628 should be >>>> correct (though his postal address may not be, since it lists New York as >>>> his location). The Vidyo contact information for him in 9627 is definitely >>>> out of date. Other Google folks, are you able to ping him internally? >>>> >>>> Justin is now at OpenAI according to his LinkedIn profile, but he still >>>> lists [email protected] as a valid e-mail address. >>>> >>>> >>>> >>>> On Wed, Feb 19, 2025 at 3:08 PM Megan Ferguson < >>>> [email protected]> wrote: >>>> >>>>> Greetings, >>>>> >>>>> A repeat of the request below for contact information for Justin and >>>>> Danny (and a note for AD awareness that we have not been able to reach >>>>> them). >>>>> >>>>> Thank you. >>>>> >>>>> RFC Editor/mf >>>>> >>>>> >>>>> > On Feb 14, 2025, at 9:49 AM, Mo Zanaty (mzanaty) <[email protected]> >>>>> wrote: >>>>> > >>>>> > 3) Further note: >>>>> > We have received bounce-message notifications for Justin Uberti and >>>>> Danny Hong on at least one email address listed. Could they each respond >>>>> confirming receipt and letting us know how their contact information >>>>> should >>>>> appear in the documents themselves? >>>>> > >>>>> > Mo: I don't know the current contact information for those authors, >>>>> but I know their affiliations have changed, so the original contact >>>>> information is stale. >>>>> > >>>>> >>>>>
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
