PMFJI (and also for top-posting on a random email in the thread) If your intention is to have an IANA registry, then please note that the Independent Stream has a strong aversion to publishing documents that create registries (see RFC 8726).
I leave it to the WG to decide whether a registry is needed if the sole purpose of the document is to describe an existing implementation (wide or otherwise). Cheers, Adrian (as ISE) Michael Richardson wrote: > > <#secure method=pgpmime mode=sign> > > Qin Wu <bill...@huawei.com> wrote: > cabo> One way to do this would be to jump-start the process by a short > cabo> document establishing this registry, with a defined registration > cabo> policy. > > > [Qin] Good proposal, agree with this. > > So the proposal, in order to avoid having to adopt pcap as an Information > document, is to adopt a third document, which is a subset of the current > pcap > document. > > > -- > Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IΓΒΈT consulting > ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg > _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
