Alexander, As the tracker shows, that RFC was published in the Independent Submission stream, not the IETF stream. There are indeed many cases of non-IETF protocols being published as Informational RFCs, but today that would always be in the Independent stream. The "status of this memo" section is then quite explicit, e.g.: https://www.rfc-editor.org/rfc/rfc8799.html#name-status-of-this-memo
That is of course a precedent. Regards Brian Carpenter On 10-Jul-21 03:02, Alexander Vainshtein wrote: > Brian, Stewart and all, > RFC 2804 notwithstanding, IETF has published RFC 3924 > <https://datatracker.ietf.org/doc/html/rfc3924> on Cisco LI Architecture. > This is not a formal contradiction, since 3924 has been published as > Informational. > Can this be used as a precedent? > > > > > Get Outlook for Android <https://aka.ms/AAb9ysg> > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > *From:* rtgwg <[email protected]> on behalf of Brian Carpenter > <[email protected]> > *Sent:* Friday, July 9, 2021, 10:25 > *To:* Stewart Bryant > *Cc:* Lin Han; [email protected]; INT Area; [email protected]; UTTARO, JAMES; > [email protected] > *Subject:* [EXTERNAL] Re: [Int-area] New Version Notification for > draft-lhan-problems-requirements-satellite-net-00.txt > > The IETF position on LI is not exactly that it's anathema, but that we will not standardise *any* intercept techniques, legal or otherwise. RFC 2804. > > > Regards, > Brian Carpenter > (via tiny screen & keyboard) > > On Fri, 9 Jul 2021, 18:33 Stewart Bryant, <[email protected] <mailto:[email protected]>> wrote: > > Unfortunately LI is not our call. > > I know the IETF finds it an anathema but it is an unspoken (in IETF) > reality of the telecommunications industry. > > The concept of a huge number of highly portable, highly directional, > microwave links that are then relayed opaquely to a foreign country is going to delight some agencies and give heartburn to their colleagues in other parts of the same agency cluster. > > I think that we can all postulate how this would (will) be solved in > a mega-cluster owned by a large ITU region 2 country, or a particularly large > Asian country but I assume we want to design a global / universal system > rather than one that will otherwise inevitably be partitioned due to > geo-political security concerns. > > Stewart > > Sent from my iPad > > > > > Notice: This e-mail together with any attachments may contain information of > Ribbon Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without express > permission is strictly prohibited. If you are not the intended recipient, > please notify the sender immediately and then delete all copies, including > any attachments. > > > Notice: This e-mail together with any attachments may contain information of > Ribbon Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without express > permission is strictly prohibited. If you are not the intended recipient, > please notify the sender immediately and then delete all copies, including > any attachments. _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
