Hi, Alexander and all Thanks for the info and comments for LI. After reading RFC 3924 and "LI from ETSI", my feeling is that the scope of LI for satellite networking will be pretty big and easy to be confusing, so I would think there should have a sperate draft talking about it. The current draft will add reference to it.
Comments? Lin From: Alexander Vainshtein <[email protected]> Sent: Friday, July 9, 2021 8:02 AM To: Brian Carpenter <[email protected]>; Stewart Bryant <[email protected]> Cc: Lin Han <[email protected]>; [email protected]; INT Area <[email protected]>; [email protected]; UTTARO, JAMES <[email protected]>; [email protected] Subject: Re: [EXTERNAL] Re: [Int-area] New Version Notification for draft-lhan-problems-requirements-satellite-net-00.txt Brian, Stewart and all, RFC 2804 notwithstanding, IETF has published RFC 3924<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3924&data=04%7C01%7Clin.han%40futurewei.com%7C33a7fde993294a82e37f08d942ea8b2f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637614397424639764%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CeckOIzWQoHoi3AAQamkMr1hPHRgOU5Jjvvqsxg%2B3Dk%3D&reserved=0> 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7Clin.han%40futurewei.com%7C33a7fde993294a82e37f08d942ea8b2f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637614397424649756%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6p8IBI%2F9PCrbIs%2B7mVx547Ni%2Fr5ogB7bnknj4x2ZVnA%3D&reserved=0> ________________________________ From: rtgwg <[email protected]<mailto:[email protected]>> on behalf of Brian Carpenter <[email protected]<mailto:[email protected]>> Sent: Friday, July 9, 2021, 10:25 To: Stewart Bryant Cc: Lin Han; [email protected]<mailto:[email protected]>; INT Area; [email protected]<mailto:[email protected]>; UTTARO, JAMES; [email protected]<mailto:[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
