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) <mzan...@cisco.com> 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 <jus...@uberti.name> > *Sent:* Thursday, February 20, 2025 2:14 AM > *To:* Zaheduzzaman Sarker <zahed.sarker.i...@gmail.com> > *Cc:* Jonathan Lennox <jonathan.lenno...@gmail.com>; Megan Ferguson < > mfergu...@staff.rfc-editor.org>; Murray S. Kucherawy <superu...@gmail.com>; > Jonathan Lennox <jonathan.lennox=408x8....@dmarc.ietf.org>; Suhas > Nandakumar (snandaku) <snand...@cisco.com>; Espen Berger (espeberg) < > espeb...@cisco.com>; Mo Zanaty (mzanaty) <mzan...@cisco.com>; Bernard > Aboba <bernard.ab...@gmail.com>; da...@vidyo.com <da...@vidyo.com>; > dannyh...@google.com <dannyh...@google.com>; mflod...@google.com < > mflod...@google.com>; hol...@google.com <hol...@google.com>; > rachel.hu...@huawei.com <rachel.hu...@huawei.com>; Francesca Palombini < > francesca.palomb...@ericsson.com>; Orie Steele <orie@transmute.industries>; > RFC Editor <rfc-edi...@rfc-editor.org>; auth48archive@rfc-editor.org < > auth48archive@rfc-editor.org> > *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 <jus...@uberti.name> wrote: > >> Hi all, yes, my affiliation is now OpenAI but you can still use >> jus...@uberti.name as my contact email. >> >> On Wed, Feb 19, 2025 at 5:17 PM Zaheduzzaman Sarker < >> zahed.sarker.i...@gmail.com> 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 < >>> jonathan.lenno...@gmail.com> 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 jus...@uberti.name as a valid e-mail address. >>>> >>>> >>>> >>>> On Wed, Feb 19, 2025 at 3:08 PM Megan Ferguson < >>>> mfergu...@staff.rfc-editor.org> 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) <mzan...@cisco.com> >>>>> 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 -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
