IETF Logo Mail Archive

Re: [netmod] XML and prefix

Ladislav Lhotka <ladislav.lhotka@nic.cz> Fri, 14 January 2022 10:49 UTC

Return-Path: <ladislav.lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C76E3A218A for <netmod@ietfa.amsl.com>; Fri, 14 Jan 2022 02:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.813
X-Spam-Level:
X-Spam-Status: No, score=-7.813 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, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n2p-7fCrel4j for <netmod@ietfa.amsl.com>; Fri, 14 Jan 2022 02:49:30 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E1673A2189 for <netmod@ietf.org>; Fri, 14 Jan 2022 02:49:29 -0800 (PST)
Received: from [IPV6:2001:1488:fffe:6:a88f:7eff:fed2:45f8] (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 67E3D1409A0; Fri, 14 Jan 2022 11:49:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1642157366; bh=0WHgnnqnYZEf38BQtQMGPJtaA2BNmjRVYxUuTOJPSLg=; h=Date:To:From; b=URvp/h0FKEYEbNWajdAYdBST++N9x+w6C/rmz560pZW0f7oeZSTyhiV5PpeFUSOLD e2PZNA9QMXpILbx0qQL0tVtapzAflmdWojQTyhLgPsgszEChdLKdEQ7HUQlqleHsc2 6xkw6S9FLoSUlpTM05Zf5f5bChhHcbnwd8aoNcyo=
Message-ID: <be6a4101-0897-09fb-43a8-604d247c7090@nic.cz>
Date: Fri, 14 Jan 2022 11:49:26 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Martin Björklund <mbj+ietf@4668.se>, ietfc@btconnect.com
Cc: netmod@ietf.org
References: <AM7PR07MB624809CE687E9F3D052253BEA0549@AM7PR07MB6248.eurprd07.prod.outlook.com> <20220114.113919.91026402981468144.id@4668.se>
From: Ladislav Lhotka <ladislav.lhotka@nic.cz>
Organization: CZ.NIC
In-Reply-To: <20220114.113919.91026402981468144.id@4668.se>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.102.4 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/b_tfgBBzC5NewMfVVxtMnNigdpY>
Subject: Re: [netmod] XML and prefix
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 10:49:35 -0000

On 14. 01. 22 11:39, Martin Björklund wrote:
> Hi,
> 
> I don't understand the problem either.  He writes:
> 
>> Sorry, but this has the same problem in figure 11.1 that we've just been
>> discussing with Ian.
> 
> Can you send a pointer to that discussion?  Perhaps there's more
> context there.

Right. I also suspect that the last sentence should have been

"I don't think it's OK for the draft to say those things."

Lada

> 
> 
> /martin
> 
> 
> tom petch <ietfc@btconnect.com> wrote:
>> I see that IANA have taken to asking  XML Registry experts about the registration of YANG namespaces at Last Call, or perhaps they have always done this but have only recently put the e-mail on a public list.  Anyhow, the experts have taken it upon themselves to comment on the XML examples and I do not understand this comment.  This comes from
>> [IANA #1217705] Expert Review for draft-ietf-i2nsf-nsf-monitoring-data-model-12 (xml-registry)
>> by Tim Bray 17 dec 2021 03:03
>>
>> ===============================
>> Sorry, but this has the same problem in figure 11.1 that we've just been
>> discussing with Ian.
>>
>> For it to work, (a) the prefix in the alarm-category element MUST be the
>> same as the namespace prefix for
>> urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-monitoring, which means that XML
>> software MUST be chosen that makes the namespace prefix information
>> available.  I don't think it's OK for the draft not to say those thigns.
>>
>> <alarm-category
>>             xmlns:nsfmi="urn:ietf:params:xml:ns:yang:\
>>                        ietf-i2nsf-nsf-monitoring">
>>             nsfmi:memory-alarm
>>           </alarm-category>
>> =================================================
>> a) I am unclear what the problem is - I thought that XML allowed great freedom with prefix even if the IETF would rather not
>> b) this suggestion seems to be that all I-D with XML examples, which is pretty much every I-D with a YANG module in it,  needs to carry a warning about what XML software to choose, which seems  rather a burden.  Thoughts?
>>
>> Tom Petch
>>
>>
>>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email