G'day Nate, Thanks for the reply.
Actually, this is an important issue. Back in ~2010, I actually I remember running into a challenge deploying some MPEG streaming via multicast, and I just couldn't get the video to work. Ultimately, the STB vendor already had port :12345 open, which is why the video multicast stream on port 12345 failed. I remember writing to the IANA to ask about assigning a port, and they basically told me to go away and write an RFC. So here we are over a decade later! Nice work! Thanks, Dave On Wed, Jan 14, 2026 at 10:14 AM Karstens, Nate <[email protected]> wrote: > Dave, > > > > Thanks for reading the document! > > > > I’d like to better understand your comment. This documents a port > assignment, so it describes the port that a given service can be reached, > which is also the value used as the destination port in the initial message. > > > > Most port assignments are unconcerned with the source port used to contact > the service. This document provides the option to use the port as the > source port multicast messages. > > > > Does that clear things up? > > > > Cheers, > > > > Nate > > > > *From:* dave seddon <[email protected]> > *Sent:* Tuesday, January 13, 2026 19:01 > *To:* [email protected] > *Cc:* [email protected] > *Subject:* [Int-area] Re: I-D Action: > draft-ietf-intarea-multicast-application-port-02.txt > > > > Friendly feedback It's unclear, at least to me, until section 2 that the > document's primary focus is the "source port. " Adding the word "source" > to the draft name "The Multicast Application [Source] Port," > > Friendly feedback > > > > It's unclear, at least to me, until section 2 that the document's primary > focus is the "source port." Adding the word "source" to the draft name > "The Multicast Application [Source] Port," and to the "Abstract" and > "Introduction" sections, would make the document more clear. > > > > First mention of "destination port" and "source port": > > " > > 2. Assignment > The Multicast Application Port SHALL NOT be used as a destination port > for any non-multicast messages. It MAY be used as a source port by an > application that exclusively uses multicast messages. > > " > > > > On Tue, Jan 13, 2026 at 3:46 PM <[email protected]> wrote: > > Internet-Draft draft-ietf-intarea-multicast-application-port-02.txt is now > available. It is a work item of the Internet Area Working Group (INTAREA) > WG > of the IETF. > > Title: The Multicast Application Port > Authors: Nate Karstens > Stuart Cheshire > Mike McBride > Name: draft-ietf-intarea-multicast-application-port-02.txt > Pages: 7 > Dates: 2026-01-13 > > Abstract: > > This document discusses the drawbacks of the current practice of > assigning a UDP port to each multicast application. Such assignments > are redundant because the multicast address already uniquely > identifies the data. The document proposes assigning a UDP port > specifically for use with multicast applications and lists > requirements for using this port. This method does not require > modification to existing protocol stacks, though recommended updates > to make the port easier to use are included. > > The IETF datatracker status page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-ietf-intarea-multicast-application-port/ > <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-intarea-multicast-application-port/__;!!EJc4YC3iFmQ!TDyqZvLhVP8rY27Q2rSzz2srF9G_0ZPL17GY2wMWodxOznZucF8lA2_ucBqND5OZhw3t-PBB2TK-gKuUM4MNMFEpb-8$> > > There is also an HTMLized version available at: > > https://datatracker.ietf.org/doc/html/draft-ietf-intarea-multicast-application-port-02 > <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-intarea-multicast-application-port-02__;!!EJc4YC3iFmQ!TDyqZvLhVP8rY27Q2rSzz2srF9G_0ZPL17GY2wMWodxOznZucF8lA2_ucBqND5OZhw3t-PBB2TK-gKuUM4MNqJIBLWQ$> > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-intarea-multicast-application-port-02 > <https://urldefense.com/v3/__https:/author-tools.ietf.org/iddiff?url2=draft-ietf-intarea-multicast-application-port-02__;!!EJc4YC3iFmQ!TDyqZvLhVP8rY27Q2rSzz2srF9G_0ZPL17GY2wMWodxOznZucF8lA2_ucBqND5OZhw3t-PBB2TK-gKuUM4MNbqNZ3no$> > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > Int-area mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > > -- > > Regards, > > Dave Seddon > +1 415 857 5102 > > ------------------------------ > > CONFIDENTIALITY NOTICE: This email and any attachments are for the sole > use of the intended recipient(s) and contain information that may be Garmin > confidential and/or Garmin legally privileged. If you have received this > email in error, please notify the sender by reply email and delete the > message. Any disclosure, copying, distribution or use of this communication > (including attachments) by someone other than the intended recipient is > prohibited. Thank you. > -- Regards, Dave Seddon +1 415 857 5102
_______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
