[IPsec] Re: Comments on draft-pwouters-ipsecme-delete-info

Valery Smyslov <smyslov.ietf@gmail.com> Wed, 31 July 2024 16:02 UTC

Return-Path: <smyslov.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 094DEC14F6AB for <ipsec@ietfa.amsl.com>; Wed, 31 Jul 2024 09:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2QWVBTthyJ1 for <ipsec@ietfa.amsl.com>; Wed, 31 Jul 2024 09:02:06 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34C27C14F6F0 for <ipsec@ietf.org>; Wed, 31 Jul 2024 09:02:01 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2f035ae0fe0so69904911fa.3 for <ipsec@ietf.org>; Wed, 31 Jul 2024 09:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722441719; x=1723046519; darn=ietf.org; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=FV+GEXMBE4GrVXyZ0DWIAv47lR/pqw9h9IJmHAWzoKs=; b=D5Vd/nZDpV85dzMxmT+rEOUou+L7TzzS3kvo0dO6xNufb3Lv3l1+MFOJfQYPAc+Sns fdlNNAb5FJ9+BKYEVHVSpQ+N61mixDq3PihBLYEy+wF7Q/MtNvNByjANN2dFM0G0c9o0 njEKPfFqfdRr0BDkPA4UQBVTSZOfmNBWGwOBM33uXW23Cteljkqr9k5UKRPNe34ZJiZK grCINR27vQiOpxdhktbrqcg9IznaH7TKNxiDydI6VKRGHrgki7msHzXe4564qU9ZxDtL y4gHUHb1ErDUkkWE61/uJ/6I0rJQqmPUYL7vPTOvExMmj9MOmGEhKjwdfAh7uOvjeZ1m Q1UQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722441719; x=1723046519; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FV+GEXMBE4GrVXyZ0DWIAv47lR/pqw9h9IJmHAWzoKs=; b=MmhoFjDUM46evccaZnVGecg4CXr1cThmYBB5utKpRb3XGrMEJktwjleh+w6ZIFN+Pa uqnD84reZhCd4ToGGssjq7Qh3orr/UEMUTQ12hThRCYqJ/qCBGrMjPfQNdOmvHr2NjGE NPDAV4Yl7q1UqUq29/sPNyFvZmzHYBaJkaq26iJuYcTW4mHm+/JrtDLTm2lFz0/SBMwx ddYqWtetx0gVeimmZkAXLydf3efbacJTlklEAR1vZw8j7NrqRW2c1Cs0x8XufBwXnCL6 rEH9AJGC7lsiWb7eOUa1XHwA+GUo06mpejL7AKg5swgGiTit3pC2vp/v5i4P9ISLJqL+ YUgA==
X-Forwarded-Encrypted: i=1; AJvYcCX3CM9uN/NDQ7n57TFnrhNKGEdFunQQDpggdkO7zT/MvG4KIG9jb2Sl0YutB9KOpR2IATmRhVhxMmfk48KF/A==
X-Gm-Message-State: AOJu0YzLRrlr2MKzQ5qEDjMutJBvm1PfKXsbqCzToiEjrxVurABaK2w3 suueJO0tVPN/Psz6rpesp3cxoGX9/HcW/osRt9zsaqCsj0gxqx91
X-Google-Smtp-Source: AGHT+IG0cBP+CK65lhSU2AqAZNOUhmWqZzUU+iyGccx5kcrRSepTYkFYlaeTf5fGajNMmNzB/0F01A==
X-Received: by 2002:a05:651c:b0a:b0:2ef:26b4:298 with SMTP id 38308e7fff4ca-2f12ee1bd47mr114646701fa.36.1722441718763; Wed, 31 Jul 2024 09:01:58 -0700 (PDT)
Received: from BuildPC ([93.188.44.204]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-2f03cf4f790sm20254411fa.55.2024.07.31.09.01.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jul 2024 09:01:58 -0700 (PDT)
From: Valery Smyslov <smyslov.ietf@gmail.com>
To: 'Christian Hopps' <chopps@chopps.org>
References: <020701dae1b9$b6741070$235c3150$@gmail.com> <CAGL5yWY4NktSfjyEs_kGEjWAyRFtd0kncDam4YMtGwfrtbDMEg@mail.gmail.com> <02b901dae28f$9c17ff30$d447fd90$@gmail.com> <CAGL5yWZ15kkXN3zB+U4L1TwakU82wTX7-kC697_06N8msofJ2g@mail.gmail.com> <29e213fa51ce41da882e1379b3db2067@huawei.com> <030601dae31c$7427dd50$5c7797f0$@gmail.com> <dee1eccdee334237bffca03d4a7388ea@huawei.com> <032101dae341$09505550$1bf0fff0$@gmail.com> <m21q39a8ou.fsf@ja.int.chopps.org>
In-Reply-To: <m21q39a8ou.fsf@ja.int.chopps.org>
Date: Wed, 31 Jul 2024 19:01:57 +0300
Message-ID: <03e901dae362$f8c04020$ea40c060$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKTXxMcsL+OEoqUquj1O3JZgb5E3gFcW1jiAZzcA6wC1ygAWAG7lGoCASlTfnQB8HEZSgGLy1XlAj1LudmwLI0TcA==
Content-Language: ru
Message-ID-Hash: VTH6DPVVUDSGYHM7M2HCJXD3NJ6JJUOQ
X-Message-ID-Hash: VTH6DPVVUDSGYHM7M2HCJXD3NJ6JJUOQ
X-MailFrom: smyslov.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipsec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "'Panwei (William)'" <william.panwei@huawei.com>, 'Paul Wouters' <paul.wouters@aiven.io>, ipsec@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPsec] Re: Comments on draft-pwouters-ipsecme-delete-info
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/E04k2IqoTn10ORiZCTpBIgPx8jo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Owner: <mailto:ipsec-owner@ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Subscribe: <mailto:ipsec-join@ietf.org>
List-Unsubscribe: <mailto:ipsec-leave@ietf.org>

> > It just comes up to my mind that the “string” type is widely used in
> > YANG modules. But I didn’t see any with a language indictor. I wonder
> > how YANG modules handle this issue.
> >
> >          I don’t know. Perhaps those strings are not transferred on
> > the wire and are not presented to end user.
> 
> I do know. Language is not specified, the strings are sent over the wire, they are
> presented to the user, and it's working just fine. Thank you for the obvious example
> of why we don't need to argue/rat-hole over this anymore. :)

No problem, but then I have a question to Paul: can you as AD clarify whether the following page

https://wiki.ietf.org/group/art/TypicalARTAreaIssues

reflects the IESG position on reviewing the IETF documents or not?

ARTART reviewers were advised by ART AD (Francesca at that time) to check IETF documents
for common ART area issues, that were listed on this page. One of them is:

	If your spec has protocol elements that contain human-readable text, you need to specify language tags for those fields, or justify why language tagging is not needed. 

As ARTART reviewer I wonder whether I should still pay attention to this advice or not
(perhaps I wrongly marked some drafts as "Not Ready" for lacking language information :-))

Regards,
Valery.

> Thanks,
> Chris.
> 
> 
> >
> >
> >
> >          BCP18 (RFC 2277) states in Section 4.2:
> >
> >
> >
> >    Protocols that transfer text MUST provide for carrying information
> >
> >    about the language of that text.
> >
> >
> >
> >    Protocols SHOULD also provide for carrying information about the
> >
> >    language of names, where appropriate.
> >
> >
> >
> > and in Section 4.4:
> >
> >
> >
> >    Protocols where users have text presented to them in response to
> > user
> >
> >    actions MUST provide for support of multiple languages.
> >
> >
> >
> >          Regards,
> >
> >          Valery.
> >
> >
> >
> > Regards & Thanks!
> >
> > Wei PAN (潘伟)
> >
> >
> >
> > _______________________________________________
> > IPsec mailing list -- ipsec@ietf.org
> > To unsubscribe send an email to ipsec-leave@ietf.org