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

Christian Hopps <chopps@chopps.org> Wed, 31 July 2024 15:21 UTC

Return-Path: <chopps@chopps.org>
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 7B373C14F71E for <ipsec@ietfa.amsl.com>; Wed, 31 Jul 2024 08:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 0A2OK5aRVXMf for <ipsec@ietfa.amsl.com>; Wed, 31 Jul 2024 08:21:39 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAC3C14F70A for <ipsec@ietf.org>; Wed, 31 Jul 2024 08:21:39 -0700 (PDT)
Received: from ja.int.chopps.org.chopps.org (syn-172-222-091-149.res.spectrum.com [172.222.91.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 4A33F7D052; Wed, 31 Jul 2024 15:21:38 +0000 (UTC)
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>
User-agent: mu4e 1.8.14; emacs 28.3
From: Christian Hopps <chopps@chopps.org>
To: Valery Smyslov <smyslov.ietf@gmail.com>
Date: Wed, 31 Jul 2024 11:16:16 -0400
In-reply-to: <032101dae341$09505550$1bf0fff0$@gmail.com>
Message-ID: <m21q39a8ou.fsf@ja.int.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: SXJA7OVYWHYRXV523RJYI2GSVF7TYTWU
X-Message-ID-Hash: SXJA7OVYWHYRXV523RJYI2GSVF7TYTWU
X-MailFrom: chopps@chopps.org
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/wo0TQBBNfAceVFmiVgDLpjtHCHw>
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>

"Valery Smyslov" <smyslov.ietf@gmail.com> writes:

> Hi William,
>
>
>
> Hi Valery,
>
>
>
>          I would also add that if this field is left, then the issues
> with its language must be addressed.
>
>          In particular, a compliance with BCP18 is needed.
>
>
>
> 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. :)

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