Re: Individual submission referred to a BoF that cannot adopt: what is the intended path?
Michael Richardson <[email protected]>
| Newsgroups | gmane.ietf.general |
|---|---|
| Message-ID | <[email protected]> |
Henri Sirkkavaara <[email protected]> wrote: > What is the intended path for an individual submission when the venue it is referred to does not exist yet? You wait :-) > draft-sirkkavaara-vaara-receipt-00 was posted on 21 June 2026. On 28 > June the Independent Submissions Editor moved it into the ISE stream, > set the intended status to Informational, and set the ISE state to > Submission Received. On 2 August the stream was changed from ISE to > none, with the document redirected to the agentproto discussion on the > grounds that the subject matter overlaps. The ISE will go through a deconflict process. This is to make sure that documents do not come to the ISE to try to get around WG process on the same topic. > agentproto is a BoF. It is not chartered. The datatracker states that > it is not accepting document adoption. Until agentproto is either a WG with a charter, or is rejected, the ISE can't finish the deconflict. Posting an I-D is never a guarantee that there is a path forward. .. > Second, is there a defined point at which the conflict is considered > resolved, either by the group chartering or by it not chartering, and > does the author need to do anything to restart the ISE process at that > point? If by the end of 127, there isn't word, then I'd just ask Eliot. I think it will likely resolve sooner, and it's AUGUST. It's always slow. > Third, is there a way for an author to tell the difference between a > hold that will resolve and one that will not? From the outside, the > datatracker shows the same thing in both cases. Ask. -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide ** My working hours and your working hours may be different. ** ** Please do not feel obligated to reply outside your normal working hours **
signature.asc
(application/pgp-signature, 487 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmqAuSgACgkQgItw+93Q 3WWr2wgAteoZFdvE4leNQ9ZIALQBWnYUF6jHlua4o5HUX8md6CvlWMvocfVBOlNG ARG1oTtplSiC2Y84fJq6tpZw7r5QNrg10dWcBQzISApp5ccDt7RepBpFnkka+g5o 2v79KCozWBo9G4OXKwF7NHMUKxMr3R1qY7l5G/PWskTzQsAUgOUWGijKrzgHzg0e vcMIwk05cQbFNW4cBZFS5qOBX+PWW/l6AVyMxnDZfgiwBH8PSvgg4bGZxebbL74s bLRdkoZRwyDw+era7m5Fl+NEu62+GwoYzexBcF2BPuBbR7DoyiWETKqQ9lzjs71i MqJudCkUno4tTU196SCbhp+P+Rz6Xw== =Z+ZB -----END PGP SIGNATURE-----